Why your website is slow, and what actually fixes it

When a site is slow, the first instinct is usually to upgrade the hosting. It rarely helps, because hosting is seldom the bottleneck. The problem is almost always what the page is asking the browser to do.

Reason one: the images

This is the single most common cause, and the easiest to fix. A photo straight from a phone camera can be four megabytes and five thousand pixels wide, displayed in a slot six hundred pixels across. The browser downloads all of it.

• Serve images at the size they are actually displayed.
• Use modern formats such as WebP or AVIF.
• Lazy-load anything below the fold.
• Set explicit dimensions so the layout does not jump while loading.

Reason two: too much third-party script

Analytics, chat widgets, heat maps, three tracking pixels, a font loader and a cookie banner. Each was added for a reason, none were ever removed, and collectively they can add several seconds before the page becomes usable.

Audit what is actually loading. In most cases at least a third of it is for a tool nobody has opened in a year.

Reason three: rendering everything in the browser

If a site is built so the browser must download a large bundle of JavaScript before it can draw any content, visitors stare at a blank screen while that happens — and search engines are not patient either. Server-rendering the initial HTML removes that wait entirely.

What to measure

• Largest Contentful Paint — when the main content becomes visible.
• Interaction to Next Paint — how quickly the page responds to a tap.
• Cumulative Layout Shift — whether things move around while loading.

Test on a mid-range phone over mobile data, not on a desktop with fibre. That is the experience most of your visitors are actually having, and it is the one search rankings are based on.