RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the Core Web Vitals gate works

This tool grades a page against Google's Core Web Vitals. Each signal is scored 0–2; the verdict is the weakest one — then a gate that can only make it worse.

The 3 signals

01LCP — loading (good ≤ 2.5s)top trigger
02INP — responsiveness (good ≤ 200ms)
03CLS — visual stability (good ≤ 0.1)
PASSING
all three vitals good
NEEDS WORK
weakest vital needs work
BLEEDING
any vital in the red
Weakest-vital · worsen-only

A page is only as fast as its worst Core Web Vital. One metric outside 'good' caps the whole-page verdict no matter how strong the other two are, regardless of the score.

NEEDS WORK

Why: INP and CLS both pass — but LCP lands at 3.2s, in the NEEDS-WORK band. A page is only as fast as its worst vital, so the whole-page verdict is NEEDS WORK. The revenue-at-risk it estimates is illustrative, from your own inputs. weakest signal 1/2 · INP and CLS both pass.

Fix firstLCP (loading) — preload the hero image, inline critical CSS, improve TTFB; never lazy-load the LCP image.

A clean sheet didn’t save it. The verdict is the weakest signal — and a top trigger is dispositive on its own — so it names the one thing to fix first. Thresholds are Google's published values; you paste field data you measured. No industry multiplier, no guaranteed outcome.