Engineering Glossary · Domains
Your Domain Name Is the First Round Trip of Every Page Load
Your waterfall does not start with HTML — it starts with a name nobody in the visitor's network has cached yet.
The short answer
A domain name is the hostname a browser must resolve to an IP address before it can open a connection, which means every cold visit spends real time on a DNS lookup before your server is even contacted.
That lookup is the first segment in a network waterfall and it is measurable on its own: Chrome DevTools reports it as DNS Lookup, curl reports it as time_namelookup, and the Navigation Timing API exposes it as domainLookupEnd minus domainLookupStart. Everything else on this page follows from being able to read that number.
By the HostingFast team · Reviewed 12 August 2026
100+
Terms defined properly
2 min
Read time, end to end
Plain
English, no hand-waving
24/7
Engineers on shift
The name itself is a lease from a registry, taken out through a registrar and renewed on a clock. That is the commercial half. The engineering half is that the same string is a cache key in every resolver between your visitor and your zone, and the behaviour of those caches decides how quickly a change you make becomes a change the world sees.
A hostname also carries connection state with it. TLS sessions, HTTP/2 and HTTP/3 connections, HSTS policy, cookies and preload hints are all scoped to the host, so splitting assets across extra hostnames is not free — each new name is another resolve, another handshake and another connection to warm up.
What the browser does before it touches your server
The order is fixed: resolve the hostname, open a TCP connection, negotiate TLS, send the request, wait for the first byte. Only the last of those is under your server's control, which is why a page can feel slow on a box that answers in 90 ms.
Cold lookups are the ones that matter. A returning visitor usually has the answer cached in the browser, in the operating system stub resolver and at their ISP's recursive resolver, so the cost lands almost entirely on first-time traffic — the traffic you are usually paying to acquire.
Measuring the name's share of the load
The cheapest measurement is one command: curl -o /dev/null -s -w "dns=%{time_namelookup} connect=%{time_connect} tls=%{time_appconnect} ttfb=%{time_starttransfer}" against your own URL. Run it twice — the first run includes the resolve, the second usually does not, and the difference is the number you are chasing.
For a per-visitor view rather than a per-engineer one, read performance.getEntriesByType("navigation") in the browser and subtract domainLookupStart from domainLookupEnd. If that figure is a meaningful slice of your TTFB, the fix belongs in DNS, not in PHP.
Apex, www, and the redirect nobody budgeted for
Serving on both example.com and www.example.com without picking a canonical host means half your traffic pays for an extra request, an extra TLS handshake and, when the redirect target is a different host, an extra DNS lookup. One 301 to one canonical host, issued by the server rather than by the application, removes the whole chain.
Check it with curl -sIL and count the hops. Two or more 301s before a 200 is a redirect chain, and each one is a full round trip on a mobile connection — the connection type where it hurts most.
What gets wired up when a name points here
Point a name at this platform and the zone, the certificate and the mail routing are provisioned together, so there is no window where HTTPS is not yet valid. Free SSL is on every plan and renews itself ahead of expiry, which removes the classic expired-certificate outage from the list of things anyone has to remember.
Order annually and the first year of the domain registration costs nothing. If the site already exists somewhere else, our engineers move it — files, databases and mailboxes — free of charge and usually inside 24 hours, with the old site still serving traffic until the new one is ready.
A glossary written by people who read logs
Every entry here exists because the same question arrived in a ticket often enough to be worth answering once, properly, with the command you would actually run to check it.
NVMe storage and server-level LiteSpeed caching are on every tier, from the smallest plan upwards. Speed is the default configuration here rather than a paid add-on.
- 100+ entries, each with the measurement attached
- Commands you can paste, not abstractions
- Cross-linked so one lookup leads to the next
- Written by the engineers who answer the tickets
Why HostingFast
Standard on every plan
The number, not the vibe
Every claim here comes with the tool that produces the figure and the range worth aiming for.
Domain Name, in the waterfall
Where the hostname sits in a real page load, and how much of your TTFB it is quietly responsible for.
Failure modes named
Redirect chains, uncached first hits and split hostnames — the specific ways this concept costs you time.
Commands included
curl format strings, Navigation Timing fields and DevTools panels, so the check takes a minute rather than an afternoon.
No cargo cult
Where a change helps a benchmark and does nothing for a visitor, this page says so plainly.
Wired to its neighbours
DNS, A Record and TTL pick up exactly where this entry stops.
Quick Start
From order to online
- 1
Time the lookup on a cold cache
Run curl with time_namelookup against your own hostname from a machine that has never queried it. That figure is your baseline and everything else is measured against it.
- 2
Count your redirect hops
curl -sIL your bare domain and your www host. Anything beyond a single 301 into a 200 is latency you are adding on purpose.
- 3
Read the field data
Pull domainLookupEnd minus domainLookupStart from Navigation Timing in real browsers, so you are measuring your audience rather than your own office connection.
- 4
Change one thing, then remeasure
Fix the canonical host, or the resolver, or the TTL — one at a time — and rerun the same command. A change you cannot demonstrate is a change you should not keep.
Built In
Loaded onto every plan
- Free SSL on every plan, renewed automatically before expiry
- NVMe SSD storage on every tier, not only the top one
- LiteSpeed caching compiled into the server, not bolted on by plugin
- Full DNS zone editing from the control panel
- Site migration handled by our engineers at no charge
- First year of your domain free on annual orders
- Renewals billed at the rate you originally signed up at
- Human support on shift every hour of every day
Frequently Asked
What people ask us most often
Does the domain name itself affect page speed?
The string does not — a fourteen-character hostname and a four-character one resolve in the same time. What costs you is the path: how far the visitor's resolver has to walk to reach an authoritative answer, whether that answer is already cached, and how many separate hostnames a single page has to resolve before it can finish rendering.
Should the canonical host be the apex or www?
Either works; committing to one is what matters. The apex cannot hold a CNAME, so if you ever want to alias the site at a CDN or a platform hostname, www gives you a lever the bare domain does not. Pick one, redirect the other with a single 301 at the server, and verify with curl -sIL that there is exactly one hop.
How do I measure the DNS portion of a page load?
Three ways, in ascending order of realism: curl with time_namelookup from your own machine, the Timing tab of a request in Chrome DevTools, and Navigation Timing read from real visitors. Only the last reflects the resolvers your audience actually uses, which is usually the only sample that matters.
Do I have to move my domain here to host with you?
No. Leave the registration where it is and either delegate the nameservers to us or point a single A record at your account — the site works identically either way. If you would rather consolidate, transfers are routine, and the first year of a domain ordered with an annual plan costs nothing.
Keep reading
DNS (Domain Name System)
The resolution chain the hostname walks, and where the milliseconds go.
Domain Registrar
Who administers the name, and which knobs they hold that show up in your runbook.
How to Choose a Domain Name
Choosing a name you will not want to redirect away from in eighteen months.
Web Hosting
cPanel hosting on NVMe with LiteSpeed, free SSL and a migration included.
Dedicated Servers
Bare metal with a panel included and the specification stated up front.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Cut the first round trip.
NVMe, LiteSpeed and free SSL on every plan, engineers who answer at any hour, and a renewal price that matches the day you signed up.
View Web Hosting plans