Performance
—
Display and response speed, under the test conditions.
Speed test for a page
Paste an address. Google tests the page on a phone and on a computer, at the same time. The score is a lab test.
Allow 15 to 40 seconds. The address is sent to Google (PageSpeed Insights). The result is kept for 90 days behind its own link. Nothing is tied to your name.
Results are kept for 90 days.
Result
Mobile
Scores
Accessibility
—
Automated checks only. A WCAG audit also needs manual tests.
Technical SEO
—
Tags, indexing and technical basics seen by the tool. Not your rank in Google.
Best practices
—
HTTPS, console errors, libraries at risk.
Real visits
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Delay before the page responds to a click. Mostly a real-user metric. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
Simulated test
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Time scripts keep the page busy and unable to respond. Lab only. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the first content is displayed. Good: 1.8 s or less.
What Google flags
Computer
Scores
Performance
—
Display and response speed, under the test conditions.
Accessibility
—
Automated checks only. A WCAG audit also needs manual tests.
Technical SEO
—
Tags, indexing and technical basics seen by the tool. Not your rank in Google.
Best practices
—
HTTPS, console errors, libraries at risk.
Real visits
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Delay before the page responds to a click. Mostly a real-user metric. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
Simulated test
—
Time until the largest visible element, often an image or a heading, is displayed. Good: 2.5 s or less.
—
Time scripts keep the page busy and unable to respond. Lab only. Good: 200 ms or less.
—
Layout shifts while the page loads. Good: 0.1 or less.
—
Time until the first content is displayed. Good: 1.8 s or less.
What Google flags
What we would look at
Fill out the form to get a quote
“*” indicates required fields
A score is not your visitors
PageSpeed loads the page in a lab: a simulated device and connection, at a given moment. Run the test again, and the score moves. The Core Web Vitals in Search Console, on the other hand, sum up 28 days of Chrome visits.
Both are useful. The lab shows what is heavy in the code. Real visits tell you whether your customers feel it. A site with little traffic often has no real-world data: that is not a failure, just a lack of measurement.
Questions about the test
The lab shares its machines and its connection. A slow third-party script, an ad or an image that changes is enough to make the number vary. Look at the metrics, not just the score.
No. It does not change your site and promises no position. It shows technical conditions that Google takes into account.
It is sent to Google for the measurement. The result is kept for 90 days under its own link, so you can share it, then it is deleted. The address is not tied to a name or an email, unless you request a quote with the form.
No. The tool only sees some of the WCAG criteria. Keyboard and screen reader testing is still done manually.
It depends on the starting point. A site that starts far behind often gains a lot in a few hours. An already optimized site needs fine-tuning, which takes longer. The quote starts from your test.
