Speed · Core Web Vitals

Core Web Vitals + Speed audit — measured like Google

Core Web Vitals (LCP, INP, CLS) measured per page on your site, not generic. Concrete recommendations with estimated impact: what to change in CSS, JS, images to get under 2.5s LCP, under 200ms INP, under 0.1 CLS.

  • Data from PageSpeed Insights API
  • Per-page not just homepage
  • Recommendations with estimated impact
See plans See how we measure

The 3 indicators · Google 2026 standards

What the Speed module checks

All 3 metrics are measured per page, compared with official Google thresholds and rolled into the global SEO score.

  • LCP

    Largest Contentful Paint

    Time until the largest element on the page appears (large text or hero image).

    • Good under 2.5 s
    • Needs improvement 2.5 – 4 s
    • Poor over 4 s
  • INP

    Interaction to Next Paint

    Time from first click or tap to the next visible update. Replaced FID in 2024.

    • Good under 200 ms
    • Needs improvement 200 – 500 ms
    • Poor over 500 ms
  • CLS

    Cumulative Layout Shift

    How much the layout “shifts" while loading (text that slides, buttons that move).

    • Good under 0.1
    • Needs improvement 0.1 – 0.25
    • Poor over 0.25

Concrete recommendations

What to change exactly

AI Co-pilot turns the Speed report into concrete recommendations, with difficulty, estimated impact and a link to docs.

  • LCP > 2.5 s

    hero image og-banner.jpg (450 KB) is the LCP element. Replace with responsive WebP (estimated 80 KB), priority hint, lazy-mount below fold.

  • INP > 200 ms

    event handler on .search-button takes 340 ms due to a costly React re-render. Memoize the component with useMemo on the items array.

  • CLS > 0.1

    images without explicit width/height on Cards #3 and #5 generate a 0.18 shift. Add width="..." height="..." attributes or CSS aspect-ratio.

Each recommendation includes: difficulty (low / medium / high) · estimated impact (delta in seconds) · link to documentation on Google or MDN.

Frequently asked

Everything you want to know about Speed

We combine 2 sources: PageSpeed Insights API (lab data, Chrome simulator) and Chrome User Experience Report (CrUX, real data from your site's Chrome users, if there's enough traffic). On Pro, the full audit correlates Speed data with concrete HTML/CSS issues.
Because Google ranks per-page, not per-site. The homepage can be fast, but slow product pages are where you lose conversions. The Speed audit traverses sitemap.xml and measures all pages that matter (top 100 by traffic).
Weekly on sites in development (many deploys), monthly on stable sites. Each major deploy on critical pages should be followed by a Speed recheck to catch regressions.

See exactly where you lose speed on your site

Free plan. Speed audit on the top 100 pages by traffic. Concrete recommendations with estimated impact.

See plans See app modules