Core Web Vitals on a Marketing Site: Five Fixes in the Order I Try Them
When a client says "the site feels slow", the useful question is which part. Core Web Vitals give you three answers: how fast the main content appears (LCP), how quickly the page reacts to a tap or click (INP), and how m
When a client says "the site feels slow", the useful question is which part. Core Web Vitals give you three answers: how fast the main content appears (LCP), how quickly the page reacts to a tap or click (INP), and how much the layout jumps around while loading (CLS). Each has a different usual cause.
Here are the five fixes I try on marketing sites, in the order I try them. The order matters because the first two fix most problems for the least effort.
1. Measure before you touch anything
Run PageSpeed Insights on the pages that matter, usually the homepage, one service page and one article. Look at the field data first if it exists, because that is what real visitors experienced. Lab data is a useful second opinion, but it is one simulated visit.
Write down the three metrics for each page. Without a baseline you cannot tell whether a change helped.
2. Fix the largest image
On most marketing pages, the largest element above the fold is an image: a hero photo, a banner, a product shot. It is also the most common reason LCP is poor.
Check four things. Is the file far bigger than the space it fills? Is it in a modern format such as WebP or AVIF? Does it have width and height attributes? And is it being lazy-loaded when it should load right away? A hero image should never be lazy-loaded. It should be preloaded or given high fetch priority so the browser starts on it early.
3. Remove what blocks the first paint
Next, look at what the browser must finish before it can show anything. Large CSS files, web fonts and scripts in the head are the usual suspects.
For fonts, host them yourself where you can, limit the number of weights, and use font-display so text shows right away. For scripts, ask of each one whether it is needed on this page. Chat widgets, heat-map tools and old tracking tags pile up on WordPress sites over the years. Defer what you must keep and delete what nobody uses.
4. Reserve space so the page stops jumping
CLS is mostly a discipline problem. A layout shifts when something loads without space being held for it: images without dimensions, ad or embed slots, cookie banners that push content down, fonts that swap and change line lengths.
The fix is dull and reliable. Give images and embeds explicit dimensions or an aspect ratio. Make banners overlay the page or reserve their height. Test on a phone, since shifts show up there first.
5. Look at interaction last
INP measures how fast the page responds when someone taps a menu, opens an accordion or submits a form. Poor results usually come from heavy JavaScript running on the main thread. On a marketing site that often means a page builder, a large slider or several third-party scripts competing for time.
The approach is the same as before: remove, defer, then simplify. A static framework such as Astro helps here because it ships little JavaScript by default, but you can improve a WordPress site a lot just by cutting plugins that load on every page.
Things I avoid
I do not chase a perfect score. A 100 in a lab test is not a business goal, and the last few points can cost more than they return.
I do not trust a single run. Scores vary between tests, so I compare several runs and the field data.
I do not install another plugin to fix a plugin problem. A "speed" plugin that adds its own scripts and settings is sometimes the right call, but more often it hides the real cause.
What to do when fixes are not enough
If the images are sized, the scripts are trimmed and the page is still slow, the cause is probably deeper: slow hosting, no caching, an overloaded database or a theme that was never built for performance. That is where hosting and platform choices come in, and it is usually cheaper to know that early.
If you want a first read on where your pages stand, the free PageScore check takes about a minute. Our managed hosting covers the server side of performance, and if the front end needs real work, here is how we approach web development.
If you would like someone to look at a specific page and tell you plainly what is worth fixing, get in touch through codercorn.com.
Abdul Haseeb Sadiq - Founder
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.