Get Google’s performance score, your Core Web Vitals and the fixes that would save the most time, from a real Lighthouse test on mobile or desktop.
Runs Google’s PageSpeed Insights on a simulated phone or desktop. Takes about 10 to 60 seconds.
SEOgent tracks Core Web Vitals for your most visited pages and hands the fixes to your coding agent.
Request an inviteOne load on a simulated mid-range phone over a slow mobile connection, or on a desktop over a fast one, scored out of 100.
Render-blocking files, unused JavaScript, oversized images, missing cache headers and the rest of Lighthouse’s insights, sorted by how much time each fix would save.
The score is Google’s. 90 and up is good, 50 to 89 needs work, and under 50 is poor. It weighs the five lab metrics, with Largest Contentful Paint, Total Blocking Time and layout shift counting most.
Real users win ties. When Chrome has enough visits, you also see the page’s real-user Core Web Vitals from the last 28 days. Those are what Google uses in ranking, so fix what they flag first.
Fixes are sorted by time saved. Lighthouse estimates how much each fix would speed up the page. The top of the list is where an afternoon of work pays off most.
It connects to Google Search Console, audits your whole site, ranks the fixes worth doing, and hands them to Claude Code, Codex or Cursor over MCP.
Request an inviteYes. There’s no signup and no email. Enter a URL and the result appears in about 10 to 60 seconds. To keep it fast for everyone, each visitor can run a few tests an hour.
It runs Google’s PageSpeed Insights on your page, which loads it in Lighthouse on a simulated mid-range phone over a slowed-down mobile connection, or in a desktop browser on a fast connection if you pick Desktop. You get Google’s performance score, the lab metrics, real-user Core Web Vitals when Google has them, and the fixes that would save the most time.
Start with mobile. Google ranks pages on their mobile version, and most visitors arrive on a phone. A page that feels quick on your laptop can take several seconds on a mid-range phone, so desktop scores usually run higher. Test desktop too if most of your visitors are on computers.
90 to 100 is good, 50 to 89 needs work, and below 50 is poor. These are Google’s bands. The score is a summary of the lab metrics; the Core Web Vitals are what Google uses in ranking.
Lab tests vary a little with network and server conditions, so a few points either way is normal. Results here are reused for a day, so testing the same URL on the same device again shows the same run.
Lab data comes from this one test. Real-user data comes from the Chrome UX Report: how the page, or the whole site when the page has too few visits, performed for real Chrome users over the last 28 days. Only real-user data includes Interaction to Next Paint.
We log the address, its score and a one-way hash of your IP address for rate limiting. Google’s PageSpeed Insights fetches the page, under Google’s terms.