Core Web Vitals sound like an engineering problem, which is why most blogging advice ignores them. But three of the biggest levers — image weight, ad placement, and theme bloat — sit squarely in editorial territory. Here's what each metric measures and the moves that actually change it.
The three metrics#
LCP (Largest Contentful Paint) — how long until the biggest visible element (usually your hero image or headline) appears. Good: under 2.5 seconds.
Readers judge this instantly; a slow LCP feels like a slow site no matter how fast everything after it is.
INP (Interaction to Next Paint) — how long between a reader tapping something (menu, link, accordion) and seeing a response. Good: under 200 milliseconds. Heavy JavaScript is almost always the culprit.
CLS (Cumulative Layout Shift) — how much content jumps around while loading. Good: under 0.1. The classic offender: an ad slot that loads late and shoves the paragraph you were reading down half a screen.
The fixes that actually matter#
1. Size images before uploading#
A phone photo is 4–8 MB. Your article column renders at maybe 800 pixels wide. Upload the original and every reader downloads all of it.
Resize covers to roughly 1200 pixels wide and export as WebP where possible — the file drops to 100–300 KB with no visible difference. If you're on a platform with next/image-style optimization this happens automatically; otherwise do it manually. This single habit usually fixes LCP by itself.
2. Reserve space for ads#
Ad layouts shift content when the space isn't booked in advance. Give every ad slot a fixed minimum height before any ad loads — that's what built-in slots with reserved containers do, and why our AdSense setup treats zero layout shift as a requirement rather than a nice-to-have. If your CLS score suffers, audit ad units first; they're responsible more often than images.
3. Keep the theme boring#
Every slider, animation library, and font variant costs milliseconds of main-thread time that INP pays for. A fast blog needs: system or well-subset fonts (two families max), one CSS file, minimal third-party widgets. Each embed — video player, comment iframe, social card — adds load; keep them below the fold where they don't block first paint.
4. Measure real visitors, not your laptop#
Lab tools (PageSpeed Insights) are fine for spotting obvious problems, but the scores that count come from Chrome users in the wild — visible in Search Console's Core Web Vitals report once traffic exists. Your MacBook on fiber is not your audience.
Why bother#
Page experience is a tiebreaker, not a rocket: great content ranks despite mediocre vitals, and perfect vitals won't save thin posts. But when two similar pages compete — and the checklist has made on-page SEO table stakes — passing vitals tips close calls. It also compounds with monetization: faster pages show ads sooner, get seen more, and earn higher RPM.
Ten minutes of image discipline per post buys all of it.
