What a slow site actually costs a Kansas City business
Somebody searching for a service while driving across the metro gives your page a few seconds at most. If it has not shown them something useful by then they are back in the results clicking the next one, and you paid nothing to lose them, which is exactly why it goes unnoticed.
There is no alert for this. The calls that did not happen do not appear anywhere. That is why speed stays unfixed on sites where everything else has been looked at twice.
Images are almost always the biggest single problem
The common pattern is a photo straight off a phone or a camera, four thousand pixels wide, displayed in a slot six hundred pixels wide. The browser downloads the whole thing and then shrinks it. Multiply that by a gallery and the page weighs more than it needs to by an order of magnitude.
Resizing to the slot, using modern formats and loading what is off screen only when it is needed usually cuts page weight more than every other fix combined, and it changes nothing about how the site looks.
Scripts that block the page from appearing
Fonts, chat widgets, review carousels, three tracking tags where one would do. Each one is small on its own. Together they stop the browser drawing anything until they have finished arriving, which is why a page can feel slow even on a fast connection.
The fix is ordering and honesty: what has to load before the page appears, what can wait, and what nobody is using and can go entirely. The third category is usually bigger than expected.
Hosting and the first byte
Some of the delay happens before the browser has anything to work with at all. Cheap shared hosting, an uncached database, a plugin running a query on every page load. If the server takes a second to answer, nothing you do in the browser gets that second back.
We measure that separately so the diagnosis does not blame the design for a server problem, or the other way around.
Measuring it the way customers experience it
A score out of a hundred from a testing tool is not the goal. The number that matters is how long somebody on a phone on cell data waits before they see something useful, and that is what we measure and report.
Before and after, on the same test, so the change is provable rather than asserted. If a fix did not move the number we say so.
Sites get slower on their own
Speed is not a one time project. New plugins, new tracking, a gallery somebody uploaded at full resolution, and six months later the page weighs what it did before. This is why it sits alongside ongoing work rather than being a box to tick.
The build decisions that prevent most of it are covered in the Kansas City web design work, and the monthly check catches the rest.
The five things we check first
Image weight, because it is almost always the largest single number. How long the server takes to send the first byte, because nothing in the browser can recover that. What loads before the page can draw. How much of what loads is used. And whether anything is being downloaded twice.
That list finds the bulk of the problem on most sites inside an hour, which is why we start there rather than with a long audit. The report you get says which of the five is costing you what, in seconds, not in a score.
If none of the five explains it, the cause is usually the hosting or a single plugin doing something expensive on every request, and we go looking for that next.
Speed questions we get asked
A useful target is something meaningful on screen within about two and a half seconds on a phone on cell data. Perfect scores in testing tools are not the goal and chasing the last few points usually costs more than it returns.
Usually not at all. Most of the gain comes from image sizing and script loading, which are invisible to a visitor. If a fix would change the design we will tell you before doing it and let you decide.
On a site that has never been looked at, cutting load time by half is common and sometimes more. On a site that has already been optimized once, the gains are smaller and we will say so before you spend anything.
It is a ranking factor but a modest one. The bigger effect is on the people who leave before the page loads, which costs you calls regardless of where you rank. We treat it as a conversion fix that happens to help rankings.
Yes, and that is most of this work. We need access to the site and the hosting, and we will tell you up front if something is slow for a reason we cannot fix without rebuilding it.
Want to know what your site weighs?
We will map where you rank across Kansas City and show you the gaps.