Short answer: To check Core Web Vitals of a website, combine Google Search Console’s Core Web Vitals report (field data at scale) with PageSpeed Insights and Lighthouse (page-level diagnostics). Start in Search Console to see passing/failing URLs by template and device, then use PageSpeed/Lighthouse to pinpoint LCP, INP, and CLS causes and fix them.
Google evaluates pass/fail at the 75th percentile: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1. Search Console updates daily on a 28‑day rolling window.
Use field data to choose what to fix, then lab data to diagnose why.
• Pull the Core Web Vitals report in Google Search Console. Switch to Mobile first. Note failing URL groups and the specific metric causing failure (LCP, INP, CLS).
• Map failing URL groups to templates. Export affected URLs. Prioritize by clicks/impressions from the Performance report so fixes move rankings.
• For each representative URL per template, run PageSpeed Insights. Capture both Field (CrUX) and Lab data. Save JSON responses or screenshots for audit trails.
• Open Chrome DevTools Lighthouse. Run Mobile, throttled. Use Performance panel to trace LCP element; use Layout Shift Regions for CLS; use Performance Insights for INP interactions.
• If you need sitewide field coverage, query the CrUX API or BigQuery dataset by origin and path to see percentile curves by device for your top templates.
• Validate dev fixes on staging with Lighthouse and WebPageTest. Only ship when LCP element, layout shifts, and interaction delays are concretely addressed.
A typical constraint: a 3-person growth team with $2k/month content budget shipping 20 posts cannot tune every page. Pick the top 3 templates by traffic, fix the heaviest elements (hero image, third-party scripts, animations), and re-check in GSC the following week. We’ve seen teams cut LCP by 900ms on blog templates by compressing hero images, lazy-loading below-the-fold media, and deferring non-critical JS in one sprint.
For deeper context, see Why Is My Website Not Indexed By Google.
Choose the tool by job: Search Console for scale, Lighthouse for diagnosis, CrUX for population truth.
caption
Mergeflo ships visibility, end-to-end, across Google and AI engines, so CWV improvements translate into rankings and citations.
Mergeflo is an autonomous SEO + AEO content engine: research to published, AI-citable pages in your CMS, with schema, internal links, and ongoing refresh. Clean, consistent templates and media discipline in this pipeline reduce LCP/CLS risk across new pages, while Mergeflo measures and fixes visibility so the gains show up in Google and AI Overviews.
Use Google Search Console’s Core Web Vitals report as your weekly source of truth, segmented by Mobile and Desktop. For the top failing URL groups, run 1-2 representative URLs through PageSpeed Insights and Lighthouse to diagnose. Track the same templates week over week; avoid chasing noise.
Passing requires LCP ≤ 2.5s, INP ≤ 200ms, and CLS ≤ 0.1 at the 75th percentile of field data. CWV is a lightweight ranking signal; relevance still dominates. In competitive queries, tie-break improvements after fixing LCP/INP can move you a few positions when content and links are already strong.
Use Search Console exports and, if you need more granularity, the CrUX API filtered by path prefixes (e.g., /blog/). Group by template. This keeps work focused on system fixes (image handling, script loading) that lift hundreds of pages at once.
Use Lighthouse and WebPageTest on staging to confirm the LCP element changed, layout shifts are eliminated, and interaction delay is low. After deployment, spot-check PageSpeed Insights for field deltas on high-traffic pages, then wait for the next GSC refresh to confirm population-level improvement.
Attack the heaviest, most common causes per template to move rankings fast.
• LCP: Compress and resize hero images, serve AVIF/WebP, set correct width/height, and use priority hints; self-host critical fonts.
• INP: Remove render-blocking JS, defer non-critical scripts, eliminate unnecessary third-party widgets, and fix expensive event handlers.
• CLS: Set fixed dimensions for media/ads, avoid late-loading fonts that shift text, and keep dynamic UI changes below the fold.
When a founder asks how to check Core Web Vitals of a website, the right sequence is pick templates via Search Console, diagnose a representative URL with Lighthouse, fix systematic issues, and confirm in field data. Do the boring, high-impact fixes. Then publish confidently, knowing Google and AI engines can cite and rank your pages.
