See your site load the way mobile users do.

Real Chromium, throttled to Slow 3G and a 4× slower CPU. LCP, INP and CLS graded on Google's thresholds, then traced to the file behind them.

Sign in to start · $1.49 per report

  • Real-user CrUX data
  • Slow & Fast 3G
  • 4× CPU throttle
  • JS/CSS coverage
  • AI fixes in the PDF
yoursite.com · Core Web Vitalsexample run

1440 × 900 · no throttling

LCP
1.6 s
Good
FCP
0.9 s
Good
TTFB
0.3 s
Good
CLS
0.02
Good

Baseline passes. Every lab vital is inside Google's good range.

  1. 01InputYour URLHomepage plus crawled pages
  2. 02MeasureReal ChromiumBaseline, Fast 3G and Slow 3G loads
  3. 03TraceRoot causeCoverage, long tasks, image bytes
  4. 04OutputRanked fixesGraded report with AI-written code

What gets measured

Measured in a real browser. Not estimated.

Every check answers two questions: what is slow, and which file made it slow?

CDP throttling · 4× CPU

Loaded like a mid-range phone on a weak signal.

Every scan reloads your page on Slow 3G and Fast 3G with a 4× slower CPU, then shows how far LCP drifts from the baseline.

Field data first

Real users beat lab guesses.

When Google has CrUX data for your page, that's the number you get. Every vital is labelled with its source.

JS & CSS coverage

Dead code, file by file.

Precise V8 and CSS rule coverage flags files over 40% unused, and names third-party scripts.

Long tasks · TBT

See what freezes the main thread.

Every task over 50 ms is counted toward Total Blocking Time, and the longest is traced to its script.

WebP · AVIF

Image savings, measured.

We download your largest PNGs and JPEGs and re-encode them, so the savings are real bytes, not estimates.

LCP element

Fixes aimed at the right image.

Fold position, lazy-loading, fetchpriority and served-vs-shown size all go into the AI fix.

Weight budgets

Payload broken down by type.

Scripts, images, CSS and fonts are each checked against a budget, so you know which one to cut first.

Grading

Google's thresholds. No house rules.

Score penalties ramp between good and poor, so a 2.6 s reading can't sink your grade the way a 6 s one does.

  • LCP≤ 2.5 s

    Largest Contentful Paint

    Good
    ≤ 2.5 s
    Needs work
    ≤ 4 s
    Poor
    > 4 s
  • INP≤ 200 ms

    Interaction to Next Paint

    Good
    ≤ 200 ms
    Needs work
    ≤ 500 ms
    Poor
    > 500 ms
  • CLS≤ 0.1

    Cumulative Layout Shift

    Good
    ≤ 0.1
    Needs work
    ≤ 0.25
    Poor
    > 0.25
  • FCP≤ 1.8 s

    First Contentful Paint

    Good
    ≤ 1.8 s
    Needs work
    ≤ 3 s
    Poor
    > 3 s
  • TTFB≤ 0.8 s

    Time to First Byte

    Good
    ≤ 0.8 s
    Needs work
    ≤ 1.8 s
    Poor
    > 1.8 s

Finding → fix

Every red number comes with the code to fix it.

AI writes each fix for your actual markup and files. It ships in the PDF, right next to the finding.

example findings

Detected

LCP image is lazy-loaded

hero.jpg · above the fold

LCP
3.4 s
Shown at
1200 × 630
Served at
2400 × 1260

Why it hurts

The browser waits for layout before fetching it, and downloads 4× the pixels it paints.

Hurts LCP

Fix · in your PDF

html
<link rel="preload" as="image" href="/hero-1200.avif"
      fetchpriority="high">

<img src="/hero-1200.avif" width="1200" height="630"
     fetchpriority="high" decoding="async" alt="…">

Fetched first, sized right

Where it lands

Numbers you can hand off.

  • White-label PDF

    Every vital labelled with its source, plus AI fixes.

  • LCP per page

    Sort crawled pages by LCP in the crawl explorer.

  • Scheduled re-scans

    Weekly or monthly runs catch regressions.

  • CSV & JSON

    Export the raw numbers for your own tooling.

FAQ

Speed questions, answered.

What is Interaction to Next Paint (INP) and why did it replace FID?

First Input Delay (FID) only measured the delay before the browser started processing the very first interaction on a page. INP evaluates all user interactions (clicks, taps, keypresses) throughout the entire session lifecycle and reports the worst-case interaction latency. Google officially replaced FID with INP in March 2024.

Why can BugViso's numbers differ from PageSpeed Insights?

When Google has real-user (CrUX) data for your page or site, BugViso reports that 28-day p75 value, the same field data PageSpeed Insights shows. Without it, BugViso falls back to a PageSpeed mobile lab run, then to its own Chromium measurement, and labels every metric with its source. The Slow 3G and Fast 3G runs are deliberate stress tests, so expect them to be slower than PageSpeed's default profile.

How is INP measured without real visitors?

INP needs real taps, clicks and keypresses, so the most reliable value is CrUX field data, which BugViso uses whenever Google has it. In the lab, BugViso measures what drives INP: main-thread tasks longer than 50 ms, Total Blocking Time, and the script each long task is attributed to.

How do I fix failing Cumulative Layout Shift (CLS)?

The primary cause of CLS is dynamically loaded images and embeds without explicit dimensions. Always specify width and height attributes (or CSS aspect-ratio) on all images and video containers so the browser can reserve the necessary layout space before the asset finishes downloading.

Does server response time (TTFB) directly affect LCP?

Yes. TTFB is the starting line for every paint metric: if your server takes 1.5 seconds to send the first byte of HTML, LCP can't be faster than 1.5 seconds. BugViso reports TTFB separately from asset download time, as the median of several loads.

Find out what's slowing you down.

One URL. Results in about five minutes.

Sign in to start · $1.49 per report