Load speed and Core Web Vitals: speed up your site
A site that goes from 4 to 2 seconds of load time often sees 10 to 20% more organic traffic in the following weeks.
- Three metrics really matter to Google: LCP, INP, and CLS
- Unoptimized images are the number-one cause of slowness on a showcase site
- Deferring non-essential JavaScript (defer/async) frees up rendering of the main content
- Weekly monitoring in Search Console catches regressions before they cost you traffic
Why speed has become crucial
Google has explicitly penalized slow sites since 2018, and that penalty tightened with Core Web Vitals in 2021. A site that takes 4 seconds to load sees its bounce rate rise by 40% compared to a site that loads in one second. A slow site sends a doubly negative signal: to search engines, and to visitors who question the company's seriousness.
Core Web Vitals: what Google really measures
LCP
Time to display the main content. Target: under 2.5 seconds.
INP
Responsiveness to a click. Target: under 200 milliseconds.
CLS
Visual stability during loading. Target: under 0.1.
On a showcase site, a hero image or a block of text often determines the LCP. A click on "Request a quote" that takes a second to respond signals an INP problem. Content that shifts after the fact, often because of images without defined dimensions, degrades the CLS.
Identify what's slowing down speed
Google PageSpeed Insights (desktop and mobile) gives a score from 0 to 100 and lists the specific issues. On showcase sites, unoptimized images are the number-one cause: a raw photo can weigh 5 to 10 MB versus 50 to 300 KB when properly compressed, a factor of 20. Poorly loaded JavaScript and the absence of browser caching follow close behind.
Optimize images: the highest-impact lever
- Resize to the size actually displayed, then compress (TinyPNG, Squoosh) with no visible loss.
- Adopt the WebP format: 25 to 35% more compression than JPEG at equal quality.
- Define dimensions in the code: reserves the space and prevents shift (CLS) on loading.
- Lazy loading for images below the fold, and responsive versions depending on the screen.
Reduce server response time and JavaScript
A well-configured server cache can bring the first-response time down from 3 seconds to 0.4 seconds. Minifying CSS and JavaScript, a CDN (Cloudflare, for example, often improves TTFB by 30 to 50%), and removing unnecessary resources round out the server-side optimization.
On the JavaScript side, defer everything that isn't essential to the initial display (tracking, chat, cookie banner) with the async or defer attributes. Splitting a large file into smaller pieces (code splitting) and assessing whether each library is truly necessary avoids needlessly blocking rendering.
A redesign is the ideal opportunity to build speed in from the design stage: that's what we build into every website design and redesign project, rather than fixing a legacy site after the fact.
Continuous monitoring
The page experience report in Google Search Console shows how many pages have a good, acceptable, or poor experience according to Core Web Vitals: check it every week. Aim for a PageSpeed score of 90 or higher on mobile and desktop; below 50, immediate action is required. An annual audit with a specialized provider is enough for most SMBs and mid-market companies without an in-house developer.
Frequently asked questions
What is the most common cause of slowness?+
Unoptimized images, by far, on the majority of showcase sites and portfolios.
Is a CDN necessary for a small site?+
Not essential, but a free CDN like Cloudflare often improves reliability and response time with no effort.
How do I know if my site has a CLS problem?+
If content moves visibly during loading, that's a sign. PageSpeed Insights gives a precise CLS score.