Website Speed Optimization Checklist: How to Get Under Two Seconds Load Time
WEBSITE DEVELOPMENT · 10 MIN READ

Website Speed Optimization Checklist: How to Get Under Two Seconds Load Time

Nine times out of ten it is the images. Here is the order I work through, from the fixes that take ten minutes to the ones that need a developer.

By Tariq Sallam·September 2026

Most slow websites are slow for two or three reasons, and they are the same two or three reasons every time. Images uploaded at camera resolution, too many scripts, and no caching.

This is the order I work through when a site needs to be faster, arranged by return per hour rather than by technical interest. The first four items fix most sites. The last few are for when you have already done the first four and still need more.

Quick Info

Target
Largest Contentful Paint under 2.5 seconds on mobile
Where to measure
PageSpeed Insights and Search Console, on real mobile data
Most common cause
Unoptimised images
Second most common
Too many plugins and third-party scripts
Typical achievable gain
Two to four seconds on an unoptimised small business site
What not to do
Install a second optimisation plugin to fix the first

Measure before you touch anything

Optimising without measuring is how people spend a weekend minifying CSS on a site whose problem was a 4MB hero image.

01Run PageSpeed Insights on your three most important pages, mobile first. Ignore the score and read the metrics.
02Open the Core Web Vitals report in Search Console. That is real user data across your whole site, which is more reliable than any single test.
03Note your Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
04Identify which element is your LCP. It is almost always an image or a heading blocked by a font.

Write the numbers down. Without a baseline you cannot tell whether anything you do afterwards helped.

Fix the images. This is usually the whole job

On the majority of small business sites I audit, images account for eighty per cent or more of the page weight, and the fix requires no technical skill.

01Resize before uploading. An image displayed at 800px wide does not need to be 4,000px wide.
02Convert to WebP or AVIF. Typically 30% to 60% smaller than JPEG at the same visible quality.
03Compress. Aim for under 200KB for content images and under 400KB for a full-width hero.
04Add width and height attributes to every image so the browser reserves the space. This alone fixes most layout shift.
05Lazy-load everything below the fold and never lazy-load the hero image, which is the mistake that makes LCP worse.

If you only do one thing on this list, resize your images before uploading them. It is the fix with the highest return and the lowest skill requirement.

Turn on caching properly

Caching means the server sends a pre-built page instead of assembling it per visitor. On WordPress that is a caching plugin; on hosted platforms it is already done for you.

Enable page caching, browser caching and, if your host offers it, object caching.
Use one caching plugin. Two fighting each other is slower than none.
Serve static assets through a CDN. Most hosts include one now and it costs nothing to switch on.
Clear the cache after changes, then retest. Half of the mysterious no-improvement results are a stale cache.

Audit what is loading

Open your browser's network tab and sort by size. You will usually find something you had forgotten: a chat widget, an old tracking pixel, a font family with nine weights, a slider plugin on a page with no slider.

01Remove plugins you are not using. Deactivated is not removed.
02Consolidate overlapping plugins. Three that each do SEO, caching or forms is two too many.
03Delete tracking scripts for tools you have stopped using. They keep loading forever.
04Load chat, booking and social embeds only on the pages that need them.
05Defer non-critical JavaScript so it does not block rendering.

Third-party scripts are the ones you cannot optimise, only remove. A chat widget can cost a second on its own, and it is worth asking whether it earns that.

Fix the fonts

Fonts are a quiet cause of slow first paint, because text cannot render until the font arrives.

Two families maximum, and only the weights you actually use. Each weight is a separate download.
Self-host rather than calling a font service. It removes a DNS lookup and a connection.
Use font-display: swap so text renders immediately in a fallback.
Preload the one font file used above the fold.

Check the hosting

If your server takes 800ms to respond, nothing you do on the page will produce a fast site. Time to First Byte over about 600ms on mobile means the problem is upstream of your optimisation work.

Cheap shared hosting oversells capacity, which shows up as inconsistent response times rather than consistently slow ones. Moving from the bottom tier to a decent managed host is frequently the single biggest improvement available, and it is the one people try last because it costs money.

The three metrics, and what each one means

Largest Contentful Paint

How long until the biggest visible thing appears. Under 2.5 seconds. Fixed by image optimisation, caching, hosting and font loading.

Interaction to Next Paint

How quickly the page responds when someone taps. Under 200 milliseconds. Fixed by reducing JavaScript, particularly third-party scripts.

Cumulative Layout Shift

How much the page jumps as it loads. Under 0.1. Fixed by setting image dimensions and reserving space for ads, banners and embeds.

Retest, then leave it alone

Retest the same three pages, compare against your written baseline, and check Search Console again in four weeks once real user data has accumulated.

Then stop. Chasing a perfect score is a hobby. A site that loads in 1.8 seconds and one that loads in 1.2 seconds convert about the same, and the hours are better spent on the content.

Speed is a threshold, not a competition. Get under the threshold and go and do something that earns money.

Frequently Asked Questions

What is a good page load time in 2026?

Largest Contentful Paint under 2.5 seconds on mobile is the threshold that matters. Total load time is a less useful number because it includes things the user never waits for.

Does site speed affect rankings?

It is a real but modest factor, and it matters more as a tie-breaker between comparable pages. Its effect on conversion is larger than its effect on ranking.

Which single fix helps most?

Resizing and compressing images. On most small business sites it accounts for the majority of the available improvement.

Do I need a CDN?

It helps if your visitors are geographically spread or your host is far from them. Most hosts now include one, so switch it on and measure.

Why did my PageSpeed score not improve after installing an optimisation plugin?

Usually a stale cache, or because the plugin cannot fix your actual problem. Plugins do not resize the images you uploaded at 4,000 pixels wide.

Is it worth paying for faster hosting?

If your Time to First Byte is over about 600ms, yes, and it is often the largest single gain available. Below that, spend the money elsewhere.

Before You Go

Work down the list in order and stop when you are under the threshold. Most sites get there at step two.

If your site is slow because of how it was built rather than what it contains, that is a platform conversation instead: the platform comparison covers it, and the Core Web Vitals guide goes deeper on the metrics.

Measure. Fix the images. Measure again.

WRITTEN BY TARIQ SALLAM
Marketing Consultant. Entrepreneur. Content Creator.

I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.

More About Tariq →

Keep reading