Page Speed
Test one URL with Google PageSpeed Insights and read its real-user Core Web Vitals and Lighthouse scores.
Page Speed (the page is titled Page Speed Insights) sends a URL to the Google PageSpeed Insights API and shows the result. It only reads your page; nothing on your site changes. It works without WordPress.
Test a page
- Open Page Speed in the sidebar.
- Enter the Page URL. Use a full public address, like
https://example.com/page. - Choose a Device: Mobile or Desktop. Google runs Mobile tests on a slower, throttled connection and Desktop tests on a faster one.
- Select Analyze.
A test can take up to 2 minutes. Google runs it, not SEObolt, so a heavy page can take a while.
To test both devices at once, select Compare Mobile vs Desktop instead.
What you see
| Section | What it shows |
|---|---|
| Scores | Performance, Accessibility, Best Practices and SEO, out of 100. Scores of 90+ show green, 50 to 89 yellow, and below 50 red. |
| Core Web Vitals (real users) | Chrome UX Report data: the 75th percentile over the last 28 days for Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS), with a Passed or Failed assessment. This is what Google uses for page experience. |
| Lab diagnostics (Lighthouse) | One simulated page load: LCP, Total Blocking Time (TBT), CLS, First Contentful Paint (FCP), Time to Interactive (TTI) and Speed Index (SI). Useful for debugging. |
| Opportunities | Up to 10 Lighthouse suggestions, with the estimated saving where Google gives one. |
| Mobile vs Desktop Comparison | After a comparison: the Performance score, LCP, FCP and CLS for each device. |
If the URL doesn't get enough Chrome traffic, the real-user card uses the whole site instead. If the site doesn't either, it says "No real-user data". Use the lab diagnostics as a guide then.
"Google couldn't score Performance on this run"
This isn't a score of 0. Lighthouse couldn't measure all the performance metrics, often because the main content appears late or behind a slider, video or cookie banner. Run it again, or try Desktop.
History
When the URL matches a page in your synced Search Console data for the active site, the result is saved with that page, replacing the one saved before. Historical Data then shows the saved scores and Core Web Vitals for that URL, with a Last checked time. Results aren't saved for URLs that don't match a synced page.
Tests only run when you select Analyze or Compare Mobile vs Desktop. Nothing is scheduled.
Your own PageSpeed API key
Without a key of your own, tests use a quota shared between SEObolt users. If it runs out, you see Google PageSpeed API key needed.
- Create a free API key for the PageSpeed Insights API in Google Cloud.
- In SEObolt, open Settings β API Keys.
- Paste it into the Google PageSpeed API Key card and save.
If Google rejects the key, check that the PageSpeed Insights API is enabled for it and that the key has no website, IP address or API restrictions.
Messages
| Message | What to do |
|---|---|
| Enter a full public web address, like https://example.com/page | Check the address is a full web address (with a dot in the domain) for a page the public can open. If you leave out https://, SEObolt adds it. |
| PageSpeed API rate limit reached | Add your own key, as above. |
| PageSpeed analysis took too long | The page is heavy or Google is busy. Try again in a moment. |
| Google PageSpeed Insights had an error on its side | Try again in a minute. |
Last updated 2026-10-28