The fastest HTML hosting, timed to a live page

ship.page is the fastest HTML host we timed, ahead of Cloudflare Pages and Netlify: with no account and $0 to pay, it served our 1.5 MB page in a median 3.14 s on November 15, 2026, against 9.52 s for Cloudflare Pages and 10.11 s for Netlify's anonymous deploy. It also led with the 24-file, 7.7 MB site at 5.15 s, where Netlify (9.42 s) edged out Cloudflare Pages (9.76 s). We rank this page by the 1.5 MB times. Speed sits next to the htmlbench Index, not inside it: ship.page scores 79/100, Netlify Drop 73/100 and Cloudflare Pages 48/100. Each time is the median of 3 runs, and the clock stopped at the first response that matched our file byte for byte.

Tested November 15, 2026Updated Nov 15, 2026

Host	htmlbench Index	1.5 MB page: URL back	1.5 MB page: live	Fastest to slowest	7.7 MB site: live	Account needed
ship.pageTop	79/100	2.20 s	3.14 s	2.67 s to 3.40 s	5.15 s	No
Cloudflare Pages	48/100	9.11 s	9.52 s	9.47 s to 10.02 s	9.76 s	Yes
Netlify Drop	73/100	9.78 s	10.11 s	7.18 s to 44.43 s	9.42 s	No

Medians of 3 runs per host and payload on November 15, 2026, through two proxy IPs in Frankfurt. Netlify was timed with its anonymous CLI deploy and Cloudflare Pages with Wrangler, project creation excluded. Surge, GitHub Pages and Tiiny Host were scored but not timed.

ship.page at 79/100: 3.14 seconds from upload to the right page

ship.page HTML hosting upload page, captured November 15, 2026

ship.page was the fastest host we timed on both payloads. For the 1.5 MB HTML page, the median of 3 runs was 2.20 s to get a URL back and 3.14 s until that URL served the right page. The individual runs went live between 2.67 s and 3.40 s.

The ZIP took longer. Our 7.7 MB site, with 24 files sent together as one ZIP, was live in a median of 5.15 s across 3 runs.

There isn't much setup. In the browser, you can drop an HTML file, a ZIP or a folder without an account, and the API takes a single request: POST the file to https://ship.page/deploy with curl, no API key needed.

How long does the link last? Without an account, it's 7 days. Claim the upload into a free account and it lasts 30 days, counted from the upload date (not the day you claim it). There's no expiry on Pro, which costs $4 a month.

Cloudflare Pages at 48/100: about nine and a half seconds on every page run

Cloudflare Pages HTML hosting page, captured November 15, 2026

Cloudflare Pages was slower, but on the 1.5 MB page it was the steadiest host in our test. Using Wrangler, the 1.5 MB page went live in a median of 9.52 s, with individual runs between 9.47 s and 10.02 s. The 24-file site took a median of 9.76 s.

That's not the whole wait. Before either upload, we had to create the Cloudflare project, which took another 2.5 to 5.4 s, with a median of 2.9 s, and we left that step out of the upload-to-live timing.

Cloudflare Pages costs $0, but you won't get a link until you've created a Cloudflare account and given your project a name.

Netlify Drop at 73/100: quick on a good run, with one 44-second wait

Netlify Drop HTML hosting upload page, captured November 15, 2026

Netlify came third on the page test, with a median of 10.11 s, but second on the 24-file site at 9.42 s. We timed its anonymous command-line deploy, not the Drop page in a browser (both let you publish without an account).

The page results were spread out: the fastest was 7.18 s, while one run took 44.4 s. That's the wait the median doesn't show. We don't have a cause to put against it.

In the browser, Netlify Drop accepts a folder, a ZIP or a single HTML file. Anonymous deploys get deleted within 1 hour unless you claim them with a free account.

There's a daily limit, too. Netlify refused our 4th anonymous deploy of the day from the test server with the message "You've reached the daily limit for anonymous deploys".

The direct numbers from our Frankfurt server

Before the published runs, we tested directly from a server in Frankfurt. ship.page had the 1.5 MB page live in 1.91 s and the 24-file site in 3.68 s. Cloudflare Pages took 8.53 s and 9.22 s, respectively. These are medians.

Netlify isn't in that set. It refused the 4th anonymous deploy of the day from that server, so we ran the published set through the same proxy exits in Frankfurt for all three hosts, rather than mixing direct and proxy results.

Hosts we couldn't put on the stopwatch

Surge scored 47/100. Surge works only from the command line: install its tool, which requires Node.js 18 or newer, then sign up in the terminal using an email and password. There's an email check too. A new account's surge.sh domains serve for 90 minutes, then stop serving until you verify your email.

GitHub Pages scored 44/100. You'll need a GitHub account and a repository before you can switch on Pages in that repository's settings. After you push, GitHub Pages builds the site from that repository. That puts account setup and a repository ahead of the first link, rather than giving us a file upload we could time on the same terms.

Tiiny Host scored 36/100. You can upload a file or a ZIP in the browser, but you have to create an account before you can upload either, and its free plan allows 1 live project with a limit of 3 MB per project.

So why scores but no times? We scored Surge, GitHub Pages and Tiiny Host without timing them; each requires an account, a terminal login or a repository before you get the first link. We didn't have a comparable upload-to-live moment to put on the stopwatch.

Frequently asked questions on upload speed

Does speed change the htmlbench Index?

No. We report speed next to the score, but it isn't part of it.

Why does the URL show up before the page is live?

The host returns a URL first; we only count the page as live when it serves our exact file. For ship.page, that was 2.20 s to the URL and 3.14 s to live.

Why did the published runs go through proxies?

Netlify refused our 4th anonymous deploy of the day from the server, so all three hosts went through the same proxy exits in Frankfurt for a fair comparison.

Was Cloudflare's project setup counted in its time?

No. Creating the project took 2.5 to 5.4 s, with a median of 2.9 s across 18 projects, and we left that out. The clock started at the deploy command.

Which host was fastest with the 24-file site?

ship.page at 5.15 s, followed by Netlify at 9.42 s and Cloudflare Pages at 9.76 s.

Sources checked November 2026