Core Web Vitals checker and competitor speed comparison (CrUX)

Compare your real 28-day Chrome mobile speed (LCP, INP, CLS, TTFB) and CMS script overhead side by side against a competitor and a zero-plugin Next.js architecture - and see how many enquiries slow mobile loads cost you each month.

Quick example:

3,000 visits/mo
€800
Reads real 28-day Chrome UX Report (CrUX) + PageSpeed data and inspects CMS script bloat.

Short answer

Core Web Vitals are Google’s three official user-experience metrics measured at the 75th percentile of real Chrome mobile visits: Largest Contentful Paint (LCP <= 2.50 s), Interaction to Next Paint (INP <= 200 ms) and Cumulative Layout Shift (CLS <= 0.10). Our tool compares your live CrUX field metrics and CMS script weight directly against your competitor and a modern Next.js Server Components stack, translating millisecond delays into estimated monthly mobile revenue leak.

What you get for free

Right away in the browser, no email required

  • Side-by-side 3-column table: Your Website vs Competitor vs Next.js Booster Pack Benchmark
  • Color-coded mobile LCP, INP, CLS and TTFB evaluated against Google’s official 75th-percentile thresholds
  • CMS & plugin X-Ray revealing detected framework, plugin footprints, render-blocking scripts and HTML KB weight
  • Reactive mobile conversion leak calculator with live sliders for monthly traffic and customer value
  • Shareable comparison URL (?a=...&b=...) to send directly to your board or developer

All measurements and financial estimates appear immediately with zero registration.

CrUX 28-Day Field Data vs Lighthouse Lab Scores

Many website owners celebrate a green 92/100 score in a desktop Lighthouse test while Google Search Console flags every URL on their domain as "Poor" on mobile. That discrepancy happens because Lighthouse is a synthetic single-run simulation, whereas Google’s ranking systems read the Chrome User Experience Report (CrUX).

  • Real devices and cellular networks: CrUX aggregates anonymized telemetry over a rolling 28-day window from real Android and desktop Chrome users visiting your pages on 4G/5G and Wi-Fi.
  • The strict 75th-percentile rule: To pass a Core Web Vital, at least 75% of all recorded visits must beat the threshold - not the average, and not your office MacBook Pro.
  • No gaming the metric: Script-delay plugins that trick Lighthouse timers by waiting for mouse movement still fail real CrUX INP as soon as a mobile visitor taps the navigation menu.

INP vs FID: Official 2026 Core Web Vitals Thresholds

When Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) in March 2024, hundreds of thousands of plugin-heavy CMS websites dropped out of the "Good" bucket overnight. Unlike FID, INP measures main-thread responsiveness throughout the entire session:

Google Core Web Vitals and server TTFB thresholds (75th percentile, mobile)

MetricGood (Green)Needs ImprovementPoor (Red)Typical Bottleneck in Legacy CMS
LCP (Largest Contentful Paint)<= 2.50 s2.51 - 4.00 s> 4.00 sSlow PHP TTFB, unoptimized hero images, render-blocking CSS/JS
INP (Interaction to Next Paint)<= 200 ms201 - 500 ms> 500 msHeavy page-builder DOM, jQuery sliders, tag manager & chat widget scripts
CLS (Cumulative Layout Shift)<= 0.100.11 - 0.25> 0.25Images/iframes without width & height, late-loading web fonts and cookie banners
TTFB (Time to First Byte)<= 800 ms801 - 1800 ms> 1800 msUncached MySQL queries, overloaded shared hosting, heavy PHP middleware

Source: Google web.dev Core Web Vitals documentation (verified November 2026).

Why CMS Plugin Bloat Leaks Mobile Leads (and How Next.js Fixes It)

A typical corporate WordPress installation accumulates 15 to 30 plugins over three years: a visual builder, form plugin, multilingual add-on, slider, popup manager and security firewall. Even when page caching hides slow PHP execution, every mobile visitor still downloads and parses each plugin’s CSS and JavaScript.

In Next.js App Router, layout, copy, comparison tables and structured data compile on the server as zero-bundle React Server Components, while images automatically receive AVIF/WebP sizing with zero layout shift. Read our full 9-point breakdown in Next.js vs WordPress for SEO & AI, see how we build high-converting sites in custom web design, pair fast pages with AI search optimization (GEO), and review all tiers on our SEO pricing page.

More free tools

Frequently Asked Questions: Core Web Vitals, INP & Next.js

Lighthouse runs a single synthetic lab simulation on a throttled virtual CPU, whereas Google Search rankings evaluate real-world Chrome User Experience Report (CrUX) field data aggregated over the past 28 days from actual mobile visitors. Our comparison tool prioritizes official 28-day CrUX field metrics and falls back to PageSpeed Insights lab runs only when a domain lacks sufficient Chrome traffic.

Interaction to Next Paint (INP) officially replaced First Input Delay (FID) in March 2024. While FID only measured the very first tap, INP measures the worst interaction latency across the entire page visit - opening mobile menus, expanding FAQs or typing into forms (threshold: 200 ms or less). Heavy CMS themes with 10-20 plugins ship megabytes of main-thread JavaScript that freeze mid-range smartphones for 300-600 ms per tap.

Page caching plugins improve server TTFB by serving pre-saved HTML instead of running PHP + MySQL queries on every visit. However, caching cannot strip bloated DOM trees or eliminate third-party plugin scripts executing inside the visitor’s phone browser. Next.js Server Components render on the edge with zero client-side JavaScript overhead for content sections, keeping INP consistently around 40-60 ms.

The formula references the joint Google and Deloitte study ("Milliseconds Make Millions"), which found across millions of mobile sessions that every 0.1 s improvement in mobile load speed lifted conversion rates by 8.4% in retail and 10.1% in travel and services. We measure the gap between your live LCP/INP and our 1.15 s Next.js benchmark with a conservative cap so you get a grounded commercial estimate.

Instead of paying $4,000-$10,000 upfront for a custom website rebuild before starting SEO, our Booster Pack (€590 net/mo, 3-month minimum agreement) includes a bespoke, custom-coded Next.js SSR website built for €0 upfront alongside ongoing technical SEO, content, link building and AI visibility optimization.

Have a project in mind? Let’s price it!

Fill out our quick form and receive a tailored proposal within 24 hours.

WHAT YOU GET AFTER SENDING

  • Clear quote and priority roadmap within ≤ 24 h on business days
  • Quick review of indexation issues, keywords and AI visibility for your domain
  • Direct reply from the SEO specialist running the work - no sales rep
  • Office: ul. Grzybowska 5A, 00-132 Warszawa
  • Phone: 518 815 055
  • E-mail: kontakt@ai-seo-company.pl
  • Opening hours: Mon-Sat 7 am-11 pm, Sunday closed
  • NIP: 5253090237
  • Response Time: Within 24 h on business days, usually sooner
Prefer to talk? Call us518 815 055

No sales rep - an SEO specialist replies in ≤ 24 h · free quote

Plan and source (optional)

The controller of your data is AI SIGNALS COMPANY Prosta Spółka Akcyjna (brand: AI SEO COMPANY), ul. Grzybowska 12/14 lok. B-3, 00-132 Warsaw, Poland. We process the form data to answer your enquiry and prepare an offer. We send it by e-mail to our team (e-mail provider: Resend) and store it in a Google spreadsheet. After you submit the form, your browser passes Google an enquiry event with your hashed e-mail address, to measure ad performance. You have the right to access, rectify and erase your data, and to object to processing. Details are in our privacy policy.

We reply within 24 h on business days. No sales rep - you hear from the person doing the SEO.

Start your project →