Episode 06 game · Vayu · Air
Vayu’s Mirage
Lighthouse says 100. Real users wait 4.2 seconds. Work out which number counts, feel the layout shift, measure the real causes, then spend a three-ticket sprint on the fixes that matter.
1 · The Mirage
Kai’s report and Google’s report don’t agree. Same page, same day.
Which number does Google use to judge the page?
2 · Feel the shift
This is Kai’s checkout on a mid-range phone. Press Start, then tap “Buy now” as fast as you can.
3 · Measure first
Field data at the 75th percentile: LCP 4.2s, INP 380ms, CLS 0.28. All three fail. What do you do next?
- LCP 4.2s · the hero image<img loading="lazy"> on a 1.8 MB JPEG, discovered late
- INP 380ms · “Add to cart”the click waits behind a 310ms task from chat-widget.js
- CLS 0.28 · the ad slot.ad-slot has no reserved height and pushes the checkout buttons
4 · The sprint
You have three tickets. Pick the three fixes that turn field LCP, INP and CLS green, then ship.
New seal earned
Mirage cleared
Acharya’s Rule #6Measure first, optimise second.
Google judges real visits at the 75th percentile. Lighthouse is for debugging.
LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1.
Find the cause with attribution before you optimise anything.