← ClaudeAtlas

page-speedlisted

Check a page's speed and Core Web Vitals (LCP, INP, CLS) from Google's PageSpeed Insights or a local Lighthouse report, separating real-user field data from lab data, read the Chrome UX Report's history of real-user Core Web Vitals for a whole site or a page over up to 40 weeks, and turn the opportunities into concrete fixes in the site's code, images, fonts and server. Use when someone asks about page speed, site speed, Core Web Vitals, PageSpeed Insights, Lighthouse, CrUX or the Chrome UX Report, LCP, INP or CLS, whether a speed fix worked, slow pages, or whether speed affects SEO or AI crawlers.
visibian/seo-geo-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill visibian/seo-geo-skills
# Page speed and Core Web Vitals Measure how fast a page is for real visitors, find what slows it, and fix it where the page is built. ## What to tell the user first - Core Web Vitals are three measures of real visits at the 75th percentile: Largest Contentful Paint (good within 2.5 seconds), Interaction to Next Paint (200 milliseconds or less) and Cumulative Layout Shift (0.1 or less) (web.dev, "Web Vitals", updated 31 October 2024). - Field data (from real Chrome users, when Google has enough of it) decides whether a page passes. Lab data, from one Lighthouse run, is for finding causes; it moves between runs. - Google has no single page experience signal; its ranking systems "look at a variety of signals that align with overall page experience", and it "always seeks to show the most relevant content, even if the page experience is sub-par" (Google Search Central, "Understanding page experience in Google Search results", updated 22 September 2026). Speed alone does not lift a page. ## Steps 1. Measure the key pages, from this skill's folder: `python3 scripts/page_speed.py https://example.com/pricing` (mobile; add `--strategy desktop` for desktop). If it answers 429, the shared quota is used up: ask the user to set a free PageSpeed Insights API key of their own in `PAGESPEED_API_KEY`, or to run Lighthouse on their machine and give you the report (`--file report.json`; the command is in the script's help). Never ask the user to paste a key into the chat. 2. Read fie