PlugsightDocs

PageSpeed Insights

Your AI can check the speed, Core Web Vitals and SEO scores of any public web page, with no connection and on every plan.

Every MCP server includes a page speed check powered by Google PageSpeed Insights. You don't need to connect anything: your AI can check any public web page.

What your AI can do

For one page, on mobile or desktop, your AI gets:

  • Scores out of 100 for performance, SEO, accessibility and best practices.
  • Real-user Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift), for the page and for the whole site, from Chrome users over the last 28 days. These are the same figures Google Search uses.
  • Lab timings from one test run, such as first contentful paint, total blocking time and server response time.
  • The biggest fixes: up to eight changes that would save the most time, with how much each would save.

Example questions

  • "Check the speed of https://example.com/pricing on mobile."
  • "Do our product pages pass Core Web Vitals?"
  • "What are the three changes that would make our home page load fastest?"
  • "Compare our home page's mobile and desktop performance scores."
  • "Check the SEO and accessibility scores of our blog's latest article."

What you need

Nothing. It works on every plan and every MCP server, whatever you have connected. The page must be public: PageSpeed Insights can't open pages behind a login.

Limits

  • Each check takes 10 to 40 seconds.
  • Mobile is checked unless you ask for desktop. Mobile is what Google ranks on.
  • Real-user data needs enough Chrome visits. For a quiet page or a new site, your AI is told "Not enough Chrome visits to this exact page for real-user data" (or "to this site"). Lab scores still work.
  • Lab data is one test run, so it can vary a little between checks.
  • If you leave out https://, Plugsight adds it.

What it can and can't change

Nothing. A page speed check only loads the page, the way a visitor would.

Troubleshooting

PageSpeed Insights didn't accept that request. … (PageSpeed Insights said: …)

What it means: Google couldn't check the page, for example because the address is wrong, the page is private, or the site didn't load for Google's test. The text after "said:" is Google's own reason.

How to fix it: Open the address in a private browser window to check it loads without signing in, then ask again.

PageSpeed Insights is limiting requests right now. Wait a minute, then try again.

What it means: Google has received too many checks in a short time.

How to fix it: Wait a minute, then ask again.

PageSpeed Insights is having problems right now. Try again in a few minutes.

What it means: Google's service had an error.

How to fix it: Try again in a few minutes.