Bulk Core Web Vitals Test

Why test Core Web Vitals in bulk

Core Web Vitals are Google's three measures of how a page feels to a visitor: Largest Contentful Paint (how fast the main content appears), Interaction to Next Paint (how fast the page reacts to a tap or click) and Cumulative Layout Shift (how much the layout jumps while loading). They feed into Google's page experience signals, and slow pages lose visitors before they see anything.

Problems rarely sit on one page. A heavy theme, a chat widget or an unoptimized hero image usually affects a whole template, so the useful question is which page types are slow — home, category, product, article — and how they compare with a competitor. PageSpeed Insights answers that one URL at a time. This tool runs up to ten pages in parallel and puts the numbers in one table.

Field data and lab data

Field data comes from real Chrome users over the last 28 days and is what Google uses for ranking. The table shows its 75th percentile, which is how Google judges a page: three out of four visits must be good. Lab data comes from one simulated load on a throttled device; it is available for any page, including new or low-traffic ones, and is best for debugging. When a page has no field data, the tool falls back to lab values and labels them.

Good, needs improvement, poor

• LCP: good up to 2.5 s, poor above 4 s.
• INP: good up to 200 ms, poor above 500 ms.
• CLS: good up to 0.1, poor above 0.25.
• TBT (lab stand-in for INP): good up to 200 ms, poor above 600 ms.

What to fix first

Start with the page type that brings the most traffic and has the worst LCP. Typical causes are a large hero image without proper sizing or preloading, render-blocking scripts and styles, and a slow server response. Poor INP usually means too much JavaScript on the main thread: third-party tags, heavy frameworks, long tasks during interaction. Layout shift comes from images and ads without reserved space and from late-loading fonts. Re-run the test after each change to confirm it helped.

FAQ