Speed is not a technical nicety. On a phone, on mobile data, a slow site loses visitors before they see anything — and they leave without knowing what they missed.
People leave. Not dramatically — they just tap back and try the next result. You never see them in any report as a lost customer, because they never became a visitor in any meaningful sense.
Search engines also measure real loading experience as part of ranking, so a slow site is fighting on two fronts: fewer people arriving, and fewer of those staying.
Ignore the overall score out of 100 — it's a summary, not a diagnosis. These are the numbers that describe what a visitor experiences:
| What it measures | In plain terms |
|---|---|
| Largest Contentful Paint | How long until the main thing on screen appears. The one that most closely matches "does this feel slow." |
| Cumulative Layout Shift | Whether the page jumps around while loading. The reason you tap the wrong thing. |
| Interaction to Next Paint | How quickly the page responds when you tap something. |
| Time to First Byte | How long the server took to start responding. Mostly a hosting and backend issue. |
Test on a phone profile with a throttled connection, not on your office desktop. Your desktop test is not what your customers experience.
Almost always the biggest win. A photo straight from a phone can be four megabytes and get displayed at 800 pixels wide. Resize to the size actually used, convert to a modern format, compress, and lazy-load anything below the fold. This alone often transforms a page.
Width and height in the markup so the browser reserves the space. Without it, the layout shifts as images arrive — that's the jumping.
Sites accumulate: an analytics script, a chat widget, a font library for two icons, a slider plugin for a slider that was removed. Each one costs a download and execution time.
Load only the weights you use. Six weights of two families is a lot of data for a page that visually uses three.
Text compression on, sensible cache headers so returning visitors don't re-download everything. Server-side concerns — see hosting and site management.
If the server takes a second before sending anything, nothing else you do gets the page under that. Usually a hosting issue or unoptimized database queries — see database-driven websites.
Some sites are slow structurally. Built on a page builder producing enormous markup, carrying a dozen plugins that each load their own assets. You can shave some off, but the floor is high.
At that point spending repeatedly on optimization costs more than rebuilding it properly. That's worth saying honestly rather than billing for incremental gains against a structural problem.
Speed decays. New images get uploaded at full size, a tracking script gets added, a plugin gets installed. Six months later you're back where you started.
Worth checking periodically — total page weight, the core measurements, and whether anything new has been added. That's part of ongoing website maintenance, and the impact on visibility is covered in SEO and performance.
Describe what your business is dealing with and you will get an honest read on whether this is worth building — and what it would take.
