Website Speed Optimization Checklist (2026)

To make a website fast, work in this order: optimise and properly size images (the biggest cause of slow pages), enable caching and a CDN, cut and defer unnecessary JavaScript, minify CSS and JavaScript, reserve space for elements to stop layout shift, and run it all on good hosting. Aim for Core Web Vitals targets of LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. In the UAE, where most traffic is mobile and often on the move, speed is not a vanity metric, it directly affects rankings and conversions. This checklist is ordered by impact so the first fixes give the biggest gains.

You can test any page free with Google's PageSpeed Insights, which reports your Core Web Vitals and tells you exactly what to fix. Here is how to act on it.

Core Web Vitals: the targets to hit

Google measures three real-world metrics that feed into rankings:
• LCP (Largest Contentful Paint) — how fast the main content loads. Target: under 2.5 seconds.
• INP (Interaction to Next Paint) — how quickly the page responds to a tap or click. Target: under 200 ms.
• CLS (Cumulative Layout Shift) — how much the layout jumps while loading. Target: under 0.1.

These map directly to user frustration: slow loading, laggy buttons, and content that jumps as you try to tap it. Fix the causes and the scores follow. For the why, see why website speed matters for UAE business.

The checklist, ordered by impact

1. Images (usually the biggest win)

Images are the most common cause of slow pages.
• Compress every image before uploading; never serve a 3 MB photo.
• Use modern formats — WebP or AVIF, which are far smaller than JPEG or PNG.
• Size images correctly — do not load a 2000px image into a 400px slot.
• Lazy-load below-the-fold images and video so they load only when needed.
• Set width and height on images so the layout does not shift (helps CLS).

2. Caching

Caching serves ready-made pages instead of rebuilding them per visit.
• Enable page caching (especially important for dynamic sites like WordPress).
• Use browser caching so returning visitors reload less.

3. A CDN

A content delivery network serves your site from servers closer to the visitor, cutting latency. For UAE visitors, a CDN (such as Cloudflare) noticeably improves load time and adds a firewall layer at the same time.

4. Cut and defer JavaScript

Heavy JavaScript is the main cause of poor INP and slow loads.
• Remove scripts you do not use — unused plugins, old tracking, abandoned widgets.
• Defer or async non-critical scripts so they do not block rendering.
• Limit third-party scripts (chat widgets, trackers); each one adds weight.

This is where lean, custom builds pull ahead of heavy template-and-plugin sites. See vanilla JS vs React and custom PHP vs template websites in the UAE.

5. Minify code

Minify CSS and JavaScript to strip whitespace and comments, and combine files where sensible to cut requests.

6. Prevent layout shift (CLS)

7. Good hosting

All the optimisation above is undermined by slow, overcrowded shared hosting. Choose a host that performs well for UAE visitors. Hosting is the foundation everything else sits on.

Quick self-audit

If you tick most of these, you are ahead of the majority of UAE business sites. For the standard we hold ourselves to, see achieving 100 PageSpeed and the SEO and performance service.

How much each fix actually moves the needle

Not every item earns the same effort. If your time is limited, this is roughly where the gains sit on a typical UAE business site, so you can start where the return is highest.

The pattern is clear: images and JavaScript give the biggest wins for the least work, which is why they sit at the top of the ordered checklist. Minification is worth doing but rarely the thing standing between you and a passing score.

When the site is slow no matter what you do

Sometimes the foundation is the problem, a bloated theme with dozens of plugins, or a heavy builder platform. In that case, optimisation only goes so far and a lean rebuild is the real fix. See rebuild a slow WordPress website in the UAE and why your website is slow on mobile.

Measure on real-world data, not just lab scores

PageSpeed Insights shows two things: a lab score (a simulated test) and field data (the real experience of actual visitors, where available). They often disagree, and the field data is what Google uses for ranking. A page can score well in the lab but fail in the field because real users are on slower devices and networks than the test assumes. Always check the field-data section, and if it is missing, your site may not have enough traffic yet, in which case test on a real mid-range phone over mobile data to approximate it. Optimising for a perfect lab score while real users struggle is a common trap.

Speed is a habit, not a one-off

A site that is fast at launch slowly gets heavier: new images go up uncompressed, a plugin is added here, a tracking script there, and six months later the page is sluggish again. Keep speed by making it part of your routine, compress every image before upload, review third-party scripts periodically and remove what you no longer use, and re-test Core Web Vitals after any significant change. For ongoing sites, a maintenance plan that includes performance checks keeps speed from quietly degrading.

The UAE latency angle most checklists skip

Every fix above assumes the server answers quickly in the first place. It often does not. A site hosted far from the UAE — a cheap US or European shared plan — adds a round-trip delay to every request before your optimised images even start downloading.

Two moves fix this. Put a CDN in front of the site so static assets are served from an edge close to Dubai, and choose hosting that responds fast to UAE visitors rather than the cheapest plan you can find. Server response time (TTFB) is the floor everything else sits on: you cannot make a page feel instant if the first byte takes a second to arrive. See website hosting in the UAE for how to judge a host on response time rather than price.

This matters most on mobile, where the connection is already slower and less stable. A page that is fine on office wifi can fall apart on 4G in a moving car, which is exactly the context why your website is slow on mobile covers.

Related resources