What is the fastest web hosting right now?
Measured by the response times real Chrome users actually experienced in June 2026, the fastest web hosting fleets are Seravo (596ms) and One.com (599ms), the only two providers whose entire customer base came in under 600 milliseconds for Time To First Byte. Close behind are the static and edge platforms GitHub Pages (639ms) and Vercel (667ms), then Hetzner Online (681ms). These are not lab numbers from a single test site. They are the 75th-percentile response time across every customer site each host runs that gets enough traffic to register with Google.
That last point is the whole story, so it is worth slowing down on.
Why is this different from every other "fastest hosting" list?
Almost every hosting speed ranking you will find works the same way: the reviewer signs up for one plan, installs one demo site, points a testing tool at it a few times, and records the result. That single number then stands in for the host's entire performance. It is cheap to produce, it is easy to flatter (a brand-new empty site on a nearby server is about as fast as that host will ever look), and it tells you very little about what your site will do once it is live with real content and real visitors.
HostList measures the opposite way. Instead of one site we control, we look at all of a host's customer sites at once, using the response times Google already collects from actual Chrome users out in the world. For the 36 fleets with enough traffic to measure in June 2026, that adds up to more than two million individual customer sites. GoDaddy alone accounts for over 575,000 of them. No demo site can represent that. The fleet can.
What exactly are we measuring?
The metric is TTFB, or Time To First Byte: how long the server takes to start sending the page after the browser asks for it. We use TTFB deliberately. Of the common speed metrics, it is the one most attributable to the host's own infrastructure. Later metrics like Largest Contentful Paint and Cumulative Layout Shift are dominated by how the site owner built the page (image sizes, fonts, scripts, layout), so they say more about the developer than the host. TTFB is where the server itself shows up.
The data comes from the Chrome User Experience Report (CrUX), Google's public record of how real Chrome users experienced real websites. Every number here is a 28-day, 75th-percentile reading: three out of four page loads were at least that fast. We only publish a fleet once at least 100 of its customer sites carry enough Chrome traffic to appear in CrUX, so no host is judged on a handful of cherry-picked origins. The raw CrUX data is public, but mapping millions of origins to the host that actually serves them, and rolling that up into one honest fleet number, is the part nobody else does.
The fastest web hosting fleets
Here are the fastest providers by phone TTFB (75th percentile) for June 2026, with the number of customer sites in each fleet:
- Seravo (Finland): 596ms, 1,883 sites. A specialist managed WordPress host, and the fastest fleet in the dataset.
- One.com (Denmark): 599ms, 21,827 sites. The fastest result at real scale, across a fleet more than ten times the size of Seravo's.
- GitHub Pages (US): 639ms, 11,134 sites. Static hosting, so speed is expected, but it earns the placement.
- Vercel (US): 667ms, 109,514 sites. Edge-served front ends across a very large fleet.
- Hetzner Online (Germany): 681ms, 11,829 sites. The fastest traditional server company on the list.
- Hostpoint (Switzerland): 695ms, 5,102 sites.
- Sakura Internet (Japan): 700ms, 53,888 sites.
- ALL-INKL.COM (Germany): 729ms, 36,739 sites.
- Xserver (Japan): 796ms, 88,355 sites.
- GoDaddy (US): 796ms, 575,262 sites. Worth noting: the largest fleet in the data is still under 800ms.
A pattern stands out. The genuinely quick end mixes boutique European and Japanese hosts (Seravo, One.com, Hostpoint, ALL-INKL.COM, Sakura, Xserver) with static and edge platforms (GitHub Pages, Vercel). If you are comparing like with like, GitHub Pages and Vercel are a different category from a traditional shared or WordPress host, and their numbers reflect that. Among conventional hosting companies, One.com and Hetzner are the standouts.
Phone or desktop?
The figures above are phone readings, because most web traffic is mobile and phones are the harder test. Desktop is generally quicker on the same fleets: Vercel drops from 667ms on phone to 426ms on desktop, GitHub Pages from 639ms to 436ms, and even GoDaddy's huge fleet improves to 626ms. The ranking barely moves, though. The hosts that are fast on phone stay fast on desktop, and the slow ones stay slow, with Flywheel still last at 1,713ms. That consistency matters: if a provider only looks good when you test it once on a wired desktop connection, the fleet data will not let it hide.
What about the fastest WordPress and VPS hosting?
For WordPress specifically, the fastest fleet in the data is Seravo at 596ms, a host that runs nothing but managed WordPress. The more useful lesson sits at the other end: one of the best-known premium managed-WordPress brands, Flywheel, posts the slowest fleet in the entire dataset at 1,766ms. Paying a managed-WordPress premium does not guarantee a fast server.
For VPS and server hosting, the spread is just as wide. Hetzner Online, popular for cloud and dedicated servers, runs at 681ms, while the budget VPS provider Contabo sits near the bottom at 1,279ms. "VPS" is not a speed tier on its own. The provider is what decides it.
Which hosts are the slowest?
We publish the slow numbers too, including for hosts that market heavily on speed. By phone TTFB (75th percentile) in June 2026, the slowest fleets were:
- Flywheel: 1,766ms (10,348 sites)
- Bluehost: 1,361ms (33,917 sites)
- HostGator: 1,309ms (40,448 sites)
- DreamHost: 1,309ms (18,583 sites)
- SiteGround: 1,248ms (96,959 sites)
The budget shared-hosting names (Bluehost, HostGator, DreamHost) clustering here is no surprise. SiteGround is the more interesting entry: it is one of the most heavily promoted "fast" hosts in the affiliate world, yet across nearly 97,000 real customer sites its fleet TTFB is roughly double what the leaders manage. That gap is exactly what a single demo-site test hides and a fleet measurement exposes.
The honest limitation
TTFB is server responsiveness, not total page speed. A quick first byte still leaves room for a slow, heavy page if the site itself is bloated, and a host's fleet number is not purely the host's doing: it partly reflects the sites its customers build and the code they run. Smaller fleets are noisier, too. Seravo's 596ms comes from under 2,000 sites, so it is a less settled figure than One.com's across nearly 22,000. Read these as strong directional signals about a host's infrastructure, not as a promise for any one site. Your own build still decides a great deal.
See the live numbers
These rankings refresh as new CrUX data lands. The current fleet TTFB table for every measured host is on our Market Insights page, in the fleet TTFB section. If you want the full method, including how we attribute origins to hosts and why we set these thresholds, it is written up at how we measure hosting performance.
