What Happens When Someone Types Your Address
Start a stopwatch when the customer's finger leaves the return key. Stop it when your logo shows up. On a good day you get something close to half a second, and inside that half second are about six separate jobs, done in order, by six different pieces of equipment. What happens when someone types your address is not one event. It is a relay, and a relay moves at the speed of its slowest leg.
The half second is a budget, not a moment
Five hundred milliseconds sounds like nothing until you divide it six ways. The name has to be looked up. A connection has to be opened. The encryption has to be negotiated. Your server has to decide what the page says. The bytes have to travel. The browser has to draw them. Six legs, in order, and every one of them can be measured on its own.
On a site that is set up properly, the first three legs finish in a fraction of the budget and the browser does most of the rest of the work. On a site that feels slow, the time is almost never spread evenly. One leg eats two seconds and the other five are rounding errors. The useful thing about a sequence is that it is not a fog. It is a list, and lists can be checked.
That matters because the product is different for every leg. There is DNS, hosting, certificates, caching and image work, and each one of those lands on exactly one step.
You cannot buy a faster website. You can only buy a faster step, and there are six to choose from.
The first leg never touches your server
Before anything of yours is involved, the browser has to turn your name into a number. That question goes to a name server, and the answer comes back from whoever holds your records, which is frequently not the company that holds your files. Two vendors, one address bar. DNS management for business domains is the leg that decides whether the question gets answered in twenty milliseconds or two hundred, and whether it gets answered correctly at all.
Records carry a time to live, which is just a number of seconds. Three thousand six hundred is one hour. Eighty six thousand four hundred is a day. When you move where your site lives, every machine that already asked keeps the old answer until that clock runs out. That is the whole explanation for the call where the owner sees the new site and a customer across town still sees the old one. Nothing is broken. Two computers hold two different answers and one of them has not expired yet.
No hosting plan on earth improves this leg. If the record for the bare domain is missing and only www resolves, half of your printed material points at nothing, and the server it was meant to reach sits idle and blameless. Slow or wrong here looks exactly like a slow website to the person typing. It is not one.
The handshake nobody counts
Once the number is known, a connection has to be opened and then the encryption has to be agreed. Both are conversations, back and forth, and every round trip costs whatever the distance costs. That is physics, not configuration. A server on another continent adds real time before a single byte of your homepage has moved, and it adds that time to every visitor, every visit, permanently.
The certificate leg does not fail slowly. It fails completely. An expired certificate does not make your site take four seconds. It puts a red warning page in front of it, and most people leave. Certificates run on short cycles now and renew on their own when they are set up right, so this leg is either invisible or catastrophic.
An expired certificate is not a slow website. It is a locked door with a warning sign on it.
What Happens When Someone Types Your Address at Two on a Tuesday
Now the request reaches your machine and your machine has to think. On a brochure site it assembles a page from a template. On a busier one it queries a database, runs a plugin, maybe calls out to somebody else for a feed. This is the leg people mean when they say the site is slow, and it is very often the leg that is fine.
A forty page site with a contact form does not need much. If it uses two hundred megabytes of memory and the plan gives it a gigabyte, moving to a plan that gives it four does not make the page arrive sooner. It gives you headroom you were not touching. Plans get sold against this because plans are what a hosting company has to sell, and a price is easier to compare than a measurement.
There are real reasons to move up and they should be said plainly. web hosting for small business is worth more money when you are genuinely running out of something, when a neighbor on a crowded shared machine is taking processor time you need at noon, or when you want better uptime. Ninety nine point nine percent of a year is about eight hours and forty five minutes of downtime. Ninety nine point nine nine percent is about fifty three minutes. That gap is worth paying for. It is just not the same purchase as a page that loads quicker.
What actually moves this leg is boring. An old PHP version. No page caching, so an identical page is rebuilt from scratch for every visitor. A plugin that calls another company's server on every load, which makes your speed their speed. A database table that has grown for six years with no index.
The bytes you send are your own decision
The fifth leg is transfer, and this is arithmetic you can do at the counter. A four megabyte hero photo is thirty two megabits. On a phone pulling twelve megabits per second that is close to three seconds for one picture, before the rest of the page moves at all. The same photograph, saved at the size it is actually displayed, might weigh two hundred kilobytes and look identical.
No hosting decision changes that. You can move to the quickest server in North America and the photo still weighs four megabytes. This is the leg where the fix is usually free and nobody wants to hear it, because it means the problem is the site and not the vendor.
Third party scripts belong here too. A chat bubble, a font service, a tracking pixel, a review badge. Each one is a fresh name lookup, a fresh connection and a fresh handshake to a machine you do not control and cannot tune. You find out how fast it is at the same moment your customer does.
Every widget on the page starts the relay over again on equipment you do not own.
Telling the legs apart costs nothing
You can narrow this down before you spend a dollar by watching the shape of the delay. A long blank pause with nothing on screen points at the first four legs. A page that appears quickly and then fills in slowly, images popping in, the layout jumping, points at transfer and drawing. Slow for one customer and fine for you, same page, same minute, is a lookup problem nearly every time.
The browser's own network panel is free and it shows the breakdown request by request, with waiting time separated from download time. A command line request with timing switched on tells the same story in one line. This is not specialist work. It is reading a receipt.
The reason to bother is that a wrong purchase costs twice. You pay the higher monthly rate, you still have the slow site, and now you believe you have already tried the fix. That is how a business ends up three plans above where it started, still waiting on a four megabyte photograph and a widget hosted in another country.
The half second is not a mystery and it is not one thing. It is six pieces of equipment doing six jobs in a fixed order, and any one of them can be the reason somebody gives up and goes back to the map listing. The measurement is cheap and it usually names the leg out loud. After that the decision is ordinary. Fix the step that is slow, and leave the other five alone.
More from the blog
- What Unlimited Hosting Really Means
- The First Hour When Your Site Goes Down
- Why Your Business Email Goes to Spam
All posts are on the blog. For the step by step versions, see the domain and hosting guides.