Why your website is slow, and the fixes in order

A slow website is expensive in a way that never appears on an invoice. Visitors leave before the page appears, Google ranks it below faster competitors, and every form and checkout converts worse. The good news is that slowness has a short list of causes, and the fixes have a clear order of impact.

Measure before touching anything

Open PageSpeed Insights, paste your address, and look at the mobile tab. Two sections matter.

The top, “Discover what your real users are experiencing”, is field data from actual visitors’ phones over the last month. This is what Google uses. The three numbers are Largest Contentful Paint, how long until the main content appears, which should be under two and a half seconds; Interaction to Next Paint, how quickly the page reacts to a tap, under two hundred milliseconds; and Cumulative Layout Shift, how much the page jumps around, under a tenth.

The lower section is a lab test with a list of opportunities. Useful for finding causes; not the score to obsess over.

Our scanner gives a quick outside read too: response time, image formats, compression, whether a CDN is in front. Between the two you can usually see the cause before opening the site’s admin.

The fixes, in order of impact

1. The server’s response time. If the first byte takes over half a second, nothing on the page can be fast. Causes: cheap shared hosting, an old PHP version, no page caching, a database bloated with years of revisions and logs. Fixes: a page cache so most visitors get a stored copy, PHP on a current version (often a large gain on its own), and if the host is the problem, a better host. This is usually the biggest single win and the one people skip because it is not visible.

2. Images. The most common cause on business sites. A phone photo uploaded at four thousand pixels and displayed at four hundred. Fixes: resize to the size actually displayed, serve modern formats like WebP or AVIF, compress, and lazy-load anything below the first screen. Most platforms can do all of this automatically once set up.

3. Third-party scripts. Chat widgets, analytics, tag managers, social embeds, fonts from three different services, tracking pixels. Each one is a request to another company’s server before your page can finish. Fix: remove what is not earning its place, load the rest after the page appears.

4. Too much on the page. Page builders that ship hundreds of kilobytes of CSS and JavaScript for a simple layout. Sliders. Twelve plugins each adding their own scripts to every page. Fix: fewer plugins, a lighter theme, and on a site that has grown heavy, a rebuild is sometimes the honest answer.

5. Fonts. Five weights of two typefaces, loaded from a remote server, blocking the text from appearing. Fix: two or three weights, preloaded, with the text shown in a fallback while they load.

6. No CDN. Visitors far from your server wait for every request to cross the distance. A CDN puts copies near them. Cloudflare’s free tier does this and it also provides the firewall we recommend anyway.

7. Layout shift. The page jumping as images and ads load, which is what the CLS number measures. Fix: give every image and embed its dimensions so the space is reserved.

What to expect

On a typical business site with the first three fixes done, the main content appears in under two seconds on mobile instead of five or six. That is the difference between visitors staying and leaving, and it moves rankings.

Speed also drifts. New plugins, new images, a cache that quietly stopped. Measuring monthly and fixing the drift is part of what a care plan does, because a site that was fast at launch is not automatically fast a year later.