A browser resolves the address to a server, opens a connection, secures it, requests the page, receives it, then discovers and loads everything the page references. Slowness lives in one of those steps, and identifying which turns an unanswerable complaint into a fixable problem.
The six steps
- Find the address. The name is translated into the server's numeric address through the domain name system.
- Open a connection to that server.
- Secure it, exchanging certificates so the connection is encrypted.
- Ask for the page, sending a request for the specific address.
- Receive the response, which is the HTML.
- Build the page, discovering and loading images, stylesheets, scripts, and fonts, then rendering.
Everything a visitor experiences as slowness is one of those taking longer than it should, and they have different causes and different fixes.
Why the order matters
The steps are largely sequential, which is the point most people miss.
Nothing in step six can begin until step five has delivered the HTML, because the browser does not know what the page needs until it reads it. And step five cannot begin until the server has finished whatever work it does.
That is why a slow server delays everything rather than only its own portion, and why optimising images does nothing if the delay is in step one.
Where each step goes wrong
Steps one to three, the setup
Usually fast and largely out of your control. Where it is slow, the causes are a distant server, a slow name resolution provider, or a certificate configuration requiring extra work.
Repeat visitors skip most of this, which is why a site feels faster the second time and why testing should be done in a fresh session.
Step five, the server response
The most consequential and the most commonly slow. This is the server doing work: running code, querying a database, and assembling the page.
Measured as time to first byte. A large figure here delays every subsequent step, and the fixes are caching, a newer language version, or more resources.
Step six, building the page
Where most of the visible weight sits on a small business site. Oversized images, scripts that block rendering, and fonts that delay text.
The specific problem is that some of these block. A script in the page head stops everything until it loads, which is why script placement matters more than script size.
The discovery problem
Worth understanding because it explains a category of slowness that looks mysterious.
The browser learns what to load by reading the HTML. If a stylesheet then references a font, the font cannot start loading until the stylesheet has arrived and been read. That is a chain, and each link adds a round trip.
Deep chains are why a page with modest total weight can still feel slow. The fix is shortening them: fewer dependencies, critical resources referenced directly in the HTML, and anything non-essential deferred.
Diagnosing yours
Browser developer tools show all of this on a waterfall chart, where each request is a bar showing when it started and how long it took.
Three things to look for. A long first bar, which is server response. A large gap before other requests begin, which is a discovery chain. And a single very long bar, which is usually one oversized file.
That reading takes two minutes and it converts the site is slow into a specific finding, which is the difference between guessing at fixes and applying one.
What the numbers mean
| Measurement | What it covers |
|---|---|
| Time to first byte | Steps one to five. Mostly server and network. |
| First contentful paint | When anything first appears on screen |
| Largest contentful paint | When the main content is visible, usually the hero image or heading |
| Fully loaded | Everything finished, including things nobody sees |
The middle two matter most, since they describe what the visitor experiences. Fully loaded is the number people quote and the least meaningful, because it includes items loading after the page is usable.
Why this is worth knowing
Not to perform the fixes yourself, but to ask the right question.
A business told the site is slow can only accept whatever is proposed. A business that knows the server response is fine and the delay is in image loading can say so, and can tell whether a proposed fix addresses the actual problem.
It also prevents the common waste of buying more hosting to solve a problem that is entirely in the images, or compressing images to solve a problem that is entirely in the server, which is the diagnostic order set out in hosting and its effect on speed.
Frequently asked questions
What happens when a browser loads a page?
It resolves the address to a server, opens a connection, secures it, requests the page, receives the HTML, then discovers and loads everything the page references before rendering.
Why does a slow server affect everything?
The steps are largely sequential. The browser cannot know what else the page needs until the HTML arrives, so a delay in the server response pushes every subsequent step back.
What is time to first byte?
How long steps one to five take, meaning the address lookup, connection, security handshake, request, and the server producing a response. It sits in front of everything else.
What is a discovery chain?
Where one file references another, so the second cannot start loading until the first arrives and is read. Deep chains make a page with modest weight still feel slow.
Which speed measurement matters most?
When content first appears and when the main content becomes visible. Fully loaded is the number most often quoted and the least meaningful, since it includes items nobody sees.
Why should a business owner know this?
To ask the right question. Knowing whether the delay is in the server or the images prevents buying more hosting to fix an image problem, or the reverse.
West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.
Been told your site is slow with no explanation of why?
We read the waterfall and tell you which of the six steps is actually costing you the time.
Start a Conversation