What actually makes a website fastWhat actually makes a website fast

Performance work has a reputation for being deep and technical. Some of it is. But in ten years of being handed slow websites to fix, the cause has almost always been one of a very short list, and none of the items on that list require rewriting anything.

1. Images

This is the first thing to check and it is right more often than everything else combined. A hero photograph exported at 4000 pixels wide and served as a 3MB JPEG to a phone is still, in 2026, the most common reason a site feels slow. Every image should be served at roughly the size it is displayed at, in a modern format, with width and height declared so the layout does not jump while it loads.

2. Fonts

Webfonts block text from painting. Two families in four weights each, loaded from a third-party domain, is eight round trips before a visitor can read a headline. Self-host the two weights you actually use, subset them to the characters you need, and give them a fallback that is close enough in metrics that the swap does not shove the page around.

3. Third-party scripts

Analytics, a chat widget, a cookie banner, a heatmap tool, two pixels and a review badge. Each was added for a good reason by someone who was not thinking about the other six. Third-party scripts are the one category where the cost is invisible in development — they are fast on your machine, on your connection, with your cache warm — and brutal on a phone on mobile data. Audit them yearly and delete the ones nobody has looked at.

4. Doing work the visitor did not ask for

Loading the whole product catalogue to render a menu. Shipping an animation library to move one arrow. Rendering the page on the client when it could have been generated at build time and served as a file. This is where framework choice genuinely matters — not because one framework is fast and another slow, but because some make it easy to do far too much by accident.

5. The server

Cheap shared hosting with no caching, a database query per component and a PHP process cold-starting on every request will defeat any amount of front-end care. If the first byte takes a second, nothing that happens afterwards can rescue the page.

Fast is not a feature you add at the end. It is the absence of a dozen small decisions to do something unnecessary.

How to actually check

Test on a real phone, on mobile data, away from your office WiFi, with the cache cleared. Lab tools are useful for finding causes, but they are simulations. The number that matters is what a customer experiences standing in a street holding a four-year-old phone — and that is usually two or three times worse than the score in the report.