PlugsightDocs

Core Web Vitals check for key pages

Check your most important pages with Google PageSpeed Insights, see which pass Core Web Vitals on mobile, and get the fixes that save the most time.

Check whether your key pages pass Google's Core Web Vitals, and what would make them faster.

What you'll get

  • For each page: performance, SEO, accessibility and best-practice scores out of 100.
  • Real-user Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift) for the page and for the whole site, from Chrome users, as Google Search uses them.
  • Lab timings from one test run.
  • The changes that would save the most time, with how much each would save.
  • A summary table across all the pages you checked.

What you need

  • Nothing to connect. PageSpeed Insights works on every plan and every MCP server. See PageSpeed Insights.
  • The pages must be public. Pages behind a login can't be checked.
  • Optional: Google Search Console or Google Analytics 4 (Pro or Agency), if you want your AI to pick the pages with the most traffic.

Ask this

Using Plugsight, run a PageSpeed check on mobile for these pages: https://example.com/, https://example.com/pricing, https://example.com/blog/. For each, tell me whether it passes Core Web Vitals, its performance score, and the top three fixes. Finish with a table across all pages.

Variations

  • Pick the pages for me: "Find my five landing pages with the most Google clicks last month in Search Console, then check each with PageSpeed on mobile."
  • Desktop: "…on desktop." Mobile is checked unless you ask; it's what Google ranks on.
  • Only SEO and accessibility: "Check only the SEO and accessibility scores of https://example.com/blog/latest."
  • Compare: "Compare the mobile and desktop scores of our home page."

What your AI does behind the scenes

  1. If you asked it to pick pages, pulls your top pages by clicks (get_marketing_data on Search Console) or sessions (on GA4).
  2. Checks each page with PageSpeed Insights (pagespeed_check), one page at a time. Each check takes 10 to 40 seconds, so several pages take a few minutes.
  3. Puts the results side by side.

A quiet page or new site may not have enough Chrome visits for real-user data; your AI is told, and the lab scores still work. Lab results come from one test run and can vary a little between checks.

Does it change anything?

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