The Journey of a Web Request
Every time you visit a website, a precise sequence of events happens in milliseconds. Understanding this process helps you make smarter hosting decisions because each step is a potential bottleneck — and good hosting optimizes every one.
This guide is based on hands-on testing of 17+ hosting providers over 90-day cycles, with detailed server response monitoring, PHP benchmark testing, and database query performance analysis.
What Happens When You Type a URL
Step 1 — DNS Lookup (5-50ms): Your browser asks DNS servers to translate the domain name (example.com) to an IP address (93.184.216.34). Your ISP usually has cached DNS records, so this is fast. If not, the query travels through root DNS servers, TLD servers, and the domain's authoritative nameserver.
Step 2 — TCP Connection (10-100ms): Your browser establishes a TCP (Transmission Control Protocol) connection with the hosting server at that IP address. This involves a three-way handshake: your browser sends SYN, the server responds SYN-ACK, and your browser confirms ACK. If the site uses HTTPS (which it should), an additional TLS handshake negotiates encryption.
Step 3 — HTTP Request (1-5ms): Your browser sends an HTTP GET request to the server, asking for the specific page. The request includes your browser type, preferred language, cookies, and other headers.
Step 4 — Server Processing (10-500ms): The server receives the request and processes it. For a static HTML site, it simply reads the file from disk. For WordPress or other dynamic sites, the server executes PHP code, queries a MySQL database, assembles the HTML, and prepares the response. This is where hosting quality matters most — a fast server with SSD storage and optimized PHP processes this in 50ms; a slow shared host might take 500ms.
Step 5 — Response & Rendering (50-2000ms): The server sends the HTML back to your browser, which then requests additional resources (CSS, JavaScript, images). Each resource triggers its own request cycle. Your browser parses the HTML, applies styles, executes scripts, and renders the final page.
Total time from URL to rendered page: 200ms-3 seconds, depending primarily on server processing speed (Step 4) and the number of resources to load (Step 5).
Web Servers Explained
What Is a Web Server?
A web server is two things: (1) the physical computer (hardware) that stores website files, and (2) the software running on that computer that handles HTTP requests. When hosting companies talk about "servers," they usually mean the combined hardware and software stack.
Server Hardware
CPU (Processor): Handles computations — PHP processing, database queries, SSL encryption. More cores and faster clock speeds mean faster dynamic page generation. RAM (Memory): Temporary working space for active processes. More RAM means more simultaneous visitors can be served without slowdown. A shared hosting server typically has 64-128GB RAM shared among hundreds of sites. Storage (SSD/NVMe): Where your files and databases physically reside. NVMe SSDs read data 5-10x faster than traditional hard drives. This directly impacts how quickly the server retrieves your files. Network: The server's connection to the internet. Data center connections are typically 1-10 Gbps — thousands of times faster than your home internet.
Web Server Software
The software that listens for incoming requests and serves files. The three most common: Apache: The oldest and most widely used. Powers about 30% of websites. Flexible but can be slower under heavy load. Nginx: Handles concurrent connections more efficiently than Apache. Used by Cloudways, Kinsta, and high-traffic sites. Powers about 35% of websites. LiteSpeed: Proprietary but fast. Built-in caching and HTTP/3 support. Used by Hostinger, ChemiCloud, and other modern shared hosts. Growing rapidly in the hosting industry.
DNS: The Internet's Phone Book
How DNS Works
DNS (Domain Name System) is the system that converts human-readable domain names into machine-readable IP addresses. Without DNS, you would need to type 93.184.216.34 instead of example.com — for every website you visit.
The DNS Resolution Process
1. Browser Cache: Your browser first checks its own cache for a recent DNS record. If you visited the site recently, it already knows the IP address. 2. OS Cache: If not in the browser cache, your operating system checks its DNS cache. 3. ISP Resolver: If neither cache has the record, the request goes to your ISP's DNS resolver (or a public resolver like Cloudflare 1.1.1.1 or Google 8.8.8.8). 4. Root Server: If the ISP resolver does not have a cached answer, it queries a root DNS server, which directs it to the TLD server for .com, .org, etc. 5. TLD Server: The TLD server directs the resolver to the domain's authoritative nameserver (set by the domain owner). 6. Authoritative Nameserver: This server has the definitive answer — the IP address of the hosting server. The answer propagates back through each level, and each server caches it for future queries.
Why DNS Matters for Hosting
When you change hosting providers, you update your nameservers. DNS propagation (the time for all DNS servers worldwide to update their cache) typically takes 15 minutes to 48 hours. During this period, some visitors see your old site and others see the new one. Using Cloudflare as your DNS provider reduces propagation time significantly and adds a CDN layer for free.
Databases and Dynamic Content
Static vs Dynamic Websites
Static websites serve pre-built HTML files. Every visitor sees the exact same page. The server simply reads a file and sends it — fast and simple. Static sites are ideal for portfolios, documentation, and landing pages.
Dynamic websites (like WordPress) generate HTML on every request. The server runs PHP code that queries a MySQL database for content, applies a template, and builds the page in real time. This enables features like user accounts, comments, search, shopping carts, and personalized content — but requires more server resources.
How WordPress Uses a Database
Every WordPress page load involves multiple database queries: fetch the post content, load sidebar widgets, retrieve menu items, check user permissions, load plugin settings, and get theme options. A typical WordPress page generates 20-100 database queries. Each query takes 1-10ms on a well-configured server — but on slow hosting with a congested database server, queries can take 50-200ms each, making page loads painfully slow.
Caching: The Performance Multiplier
Caching stores the results of expensive operations so they do not need to be repeated. Page caching: Stores the fully rendered HTML page. Instead of running PHP and querying the database on every visit, the server returns the cached HTML file. This turns a dynamic WordPress site into a virtually static one for logged-out visitors. Object caching (Redis/Memcached): Stores database query results in RAM. When WordPress asks the same database question again, the answer comes from fast memory instead of slow disk. Reduces database load by 40-70%. CDN caching: Stores static files (images, CSS, JavaScript) on servers worldwide. Visitors download these from the nearest server rather than your origin host — reducing latency and server load.
What Makes Hosting Fast or Slow
The 5 Factors That Determine Hosting Speed
1. Server Hardware: NVMe SSD storage reads data 10x faster than HDD. Modern CPUs (AMD EPYC, Intel Xeon) process PHP 2-3x faster than older hardware. More RAM means more simultaneous processes without swapping to disk. Hosts using current-generation hardware (ChemiCloud, Cloudways, Kinsta) consistently outperform budget hosts running older machines.
2. Server Software Stack: LiteSpeed and Nginx handle concurrent connections more efficiently than Apache alone. PHP 8.2+ runs 20-30% faster than PHP 7.4. MariaDB is slightly faster than MySQL for WordPress queries. The best hosts keep their software stacks current — check which PHP version your host defaults to.
3. Server Location: Physical distance between the server and your visitor adds latency. A server in New York responds to a New York visitor in 10-20ms, but to a London visitor in 80-100ms. Choose a host with servers near your primary audience. CDNs reduce this gap by serving cached content from edge servers worldwide.
4. Resource Contention (Shared Hosting): On shared hosting, your site shares CPU, RAM, and I/O with other sites. If a neighbor site runs a heavy cron job or gets a traffic spike, your site can slow down temporarily. This is the main limitation of shared hosting and the primary reason to upgrade to VPS or cloud.
5. Caching Configuration: A well-cached WordPress site loads in 200-500ms. The same site without caching loads in 1.5-4 seconds. Server-level caching (managed hosts) outperforms plugin-based caching (regular hosts) because it operates at a lower, more efficient level of the software stack.
How We Measure Hosting Speed
TTFB (Time To First Byte): The time from sending a request to receiving the first byte of data. Measures pure server speed. Under 200ms is excellent, 200-400ms is acceptable, over 500ms is poor. Fully Loaded Time: Total time to load all page resources. Depends on both hosting speed and page optimization. Under 2 seconds is the target. Uptime: Percentage of time the server is accessible. 99.99% = 52 minutes downtime/year. 99.9% = 8.7 hours downtime/year.
FAQ
Bottom Line
Frequently Asked Questions
What is TTFB and why does it matter?
TTFB (Time To First Byte) measures how quickly a hosting server begins responding to a request. It is the purest measure of server speed because it isolates server processing from page complexity. Google uses server response time as a ranking factor — sites with TTFB under 200ms have an SEO advantage. In our tests, Cloudways (145ms) and Kinsta (155ms) deliver the best TTFB.
Does server location affect my website speed?
Yes, significantly. Every 1,000 miles between server and visitor adds roughly 10-15ms of latency. If your audience is in the US, choose a US data center. If your audience is global, use a CDN (Cloudflare is free) to serve cached content from the nearest edge server. Most quality hosts offer data centers in multiple regions.
What is the difference between SSD and NVMe hosting?
Both are solid-state storage, but NVMe connects directly to the CPU via PCIe bus, while SATA SSD uses a slower interface. NVMe reads data 3-7x faster than SATA SSD. For hosting, this means faster file retrieval, faster database queries, and quicker page loads. Most modern hosts (ChemiCloud, Hostinger, Cloudways) use NVMe storage.
Why is my WordPress site slow even on good hosting?
Common culprits: too many plugins (each adds PHP processing time), unoptimized images (use WebP format and compression), no caching configured (install a caching plugin or use managed hosting with server-level caching), heavy theme with unused features, external scripts (analytics, ads, chat widgets) blocking page render. Good hosting is necessary but not sufficient — page optimization matters too.
What is a CDN and do I need one?
A CDN (Content Delivery Network) stores copies of your static files on servers worldwide. When a visitor loads your site, images, CSS, and JavaScript download from the nearest CDN server rather than your origin host. Cloudflare offers a free CDN that is easy to set up. You need one if your audience is geographically distributed or you serve large media files.
What does unmetered bandwidth mean?
Unmetered bandwidth means the host does not cap your monthly data transfer. However, it does not mean unlimited — if your usage is excessive (far beyond normal website traffic), the host may throttle your connection or ask you to upgrade. For most websites with under 100,000 monthly visitors, unmetered bandwidth on any quality host is more than enough.
The Bottom Line
Fastest Shared Hosting
Fastest Overall
Understanding how hosting works helps you choose wisely. For the fastest budget hosting, Hostinger ($2.99/mo) runs LiteSpeed on NVMe with modern PHP. For the fastest performance overall, Cloudways ($14/mo) delivers 145ms TTFB with a fully optimized cloud stack. For the best reliability, ChemiCloud ($2.49/mo) achieves 99.99% uptime at the lowest price point.
More guides: What Is Web Hosting? Beginner's Guide • Types of Web Hosting Explained • Uptime Explained: Why 99.9% vs 99.99% Matters