Core Web Vitals in 2026: Why Your Website Feels Slow
A site can look modern and still lose half its mobile visitors before it renders. The five usual causes and the fixes in the order that pays back fastest.
A website can look modern, load fast enough on office Wi-Fi, and still be quietly losing customers. Usually the owner never finds out — the visitor just leaves.
Start with the numbers
- LCP (Largest Contentful Paint) — main content visible. Good: under 2.5s.
- INP (Interaction to Next Paint) — response to a tap. Good: under 200ms.
- CLS (Cumulative Layout Shift) — layout jumping. Good: under 0.1.
Test on mobile, on throttled 4G. Desktop scores flatter sites.
The five usual culprits
- Oversized images. Resize to display size, serve WebP, compress to 80–85% quality, lazy-load below the fold.
- Too many scripts. Every chat widget, pixel and slider library is code the browser must run.
- Cheap hosting. Ask for TTFB — under 600ms is acceptable, under 200ms is good.
- Render-blocking CSS and fonts. Self-host fonts and load only the weights you use.
- Plugin bloat. On WordPress, trimming the plugin list is often the single most effective fix.
What faster is actually worth
- Pages over 3 seconds lose roughly half of mobile visitors before they render.
- Moving LCP from 4s to 2s typically lifts conversion rates by 10–30%.
- Faster pages get crawled more often, so new content is indexed sooner.
Sensible order of work
Measure, compress every image, enable caching and a CDN, trim scripts and plugins, fix layout shift, then re-measure monthly.