Most sites that feel slow are not slow everywhere. They are slow in one or two specific places, and those places are almost always the same ones. This is the order we work through them, and roughly what each one is worth.
A visitor decides whether your site is fast in about a second and a half, and they decide it on the first screen — not on the page weight in your build report. That gap between what a tool measures and what a person feels is where most performance work goes wrong. You can shave four hundred kilobytes off a page and change nothing anyone notices, or move one image tag and change everything.
Three things carry almost all of the perceived delay: how long the page stays blank, how long the biggest thing on the first screen takes to paint, and whether the layout jumps around while it settles. Everything else is secondary until those three are handled.
Performance work is not about making everything faster. It is about making the first screen honest.
A blockquote in the editor renders as this pull quote — no extra markup needed
This is the single largest win on nearly every site we are handed, and it is usually the cheapest. A 2400-pixel photograph delivered to a 390-pixel phone is not a small waste; it is most of the page. Modern formats and a correct srcset together typically remove somewhere between half and four fifths of the bytes on a content page.
Open the network panel, sort by size, and look at the top five rows. If four of them are images, you have your afternoon planned. If none of them are, move on to the next section rather than optimising something that was never the problem.
Analytics, a chat widget, two tag managers, a heat-map tool nobody has opened since the redesign, and a font loader. Each was added for a reason and each reason expired. Third-party scripts are the only part of a page you pay for continuously without owning.
If your pages are the same for every visitor, they should not be rebuilt for every visitor. Edge caching moves the response closer to the person asking for it and removes the server from the critical path entirely for repeat views.
| Fix | Typical effort | Typical payoff |
|---|---|---|
| Image sizing | Half a day | Large |
| Third-party audit | An hour | Large |
| Edge caching | A day | Medium |
| Font loading | An hour | Small but visible |
Fonts are quiet. They rarely show up as the biggest file, but they block text from painting and they cause the jump that makes a page feel unfinished. Subset them, preload the one face that appears in the first screen, and give the rest an honest fallback.
A desktop with a fibre connection will tell you the site is fine. It is not lying; it is answering a different question. Test on a mid-range Android over a throttled connection and the list of what matters reorders itself immediately.
Take the largest image on your busiest page and fix that one image properly — correct format, correct dimensions, reserved space. Measure before and after on a phone. That single change is usually worth more than the rest of the list combined, and it tells you whether the rest of the list is worth doing at all.
Tell us what you are building and we will come back with a plan, a timeline and a number.
Get a Free Quote
