Why did my audit findings change after PageSpeed ran?
Google's PageSpeed test loads the website in a real phone browser, and what Google saw replaces what the first audit worked out from the raw page code. That can confirm a finding, clear it, or change how a row reads, and the lead's problems and score are then worked out again. It can happen by itself a few minutes after a search completes, because Legiit Leads runs the test automatically on up to 25 leads, not only when you click ⚡ Get Google's Official Score.
What Google's page load changes
- Tracking and chat tags. Analytics, the Meta pixel, the Google Ads tag, live chat and AI chatbots are judged by whether they actually loaded while Google opened the page. A tag that loaded is marked present and verified, so Analytics or Meta pixel reads Installed. A tag that did not load is marked verified absent and reads
Not found (verified). - One exception. If a tag is clearly in the page code but did not fire during Google's load, it stays marked present. Cookie consent banners and delayed loading often hold tags back.
- Forms, booking and email tools can only be added. If an embedded form service, a booking tool or an email marketing service loaded, Contact form, Online booking or Email capture becomes present and verified. If none loaded, nothing changes, because a plain form on a page makes no request Google could see.
- Mobile viewport. Google's own mobile check replaces the first verdict. When it passes, the row reads Yes (Google verified).
- Title tag and Meta description. Google's SEO checks settle these. If Google found none, the row reads Missing. If Google saw one that the raw page code did not have, the row reads Set by JavaScript (Google saw one) or Present (set by JavaScript).
- Image alt text. Google's verdict settles the row, so the (unverified) note goes. If Google found the images do have alt text, the row shows all of them covered.
After these changes, the lead's problems, its Worth a look, not verified box and its opportunity score are all recalculated. A hint can become a problem, and a problem can disappear.
How to tell Google's load was used
- The Pages checked row gains + Google rendered load.
- Hover over a changed row to see the evidence, for example
Analytics loaded during Google's rendered page load (84 network requests). - A Google PageSpeed row with the score appears in the audit.
When Google's load was cut short
A real page load makes dozens of requests. If Google's load was blocked or cut short and made only a handful, only the Mobile viewport verdict is updated (a pass then reads plain Yes). The score is still saved, but every other finding stays as the first audit found it, and Pages checked does not gain + Google rendered load.
Good to know
- Later re-checks keep Google's results. When the checks run again, for example when someone opens the proof page, findings Google verified are kept. The one exception is a tool Google's load marked missing that the new check now finds, for example because the business has installed it since: the new find wins.
- Findings you removed with Something not accurate? stay removed.
- The results page stops refreshing once a search is complete, so reload it to see changes from the automatic check. See Why did my leads' problems and scores change after the search said complete?
Still stuck?
A real person on the Legiit team will help. No bots, no runaround.
Contact Supporthelp@legiit.com