The fastest link-in-bio page you can publish, and why it stays online
A Keepp page appears in a fifth of a second on a fast connection and 0.6 s on 4G, ahead of Linktree, Stan Store, bio.site, Linkin.bio, Carrd and Gumroad on real creator pages. It is served from Cloudflare's network in 348 cities, so it stays online even when a server does not.
A Keepp page appears in a fifth of a second on a fast connection and 0.6 seconds on a 4G phone signal, faster than real creator pages on Linktree, Stan Store, bio.site, Linkin.bio, Carrd and Gumroad under the same test. It is served from Cloudflare’s network, which sits within 50 milliseconds of 95% of the world’s internet users, and a published page keeps serving from there whether or not our own servers are reachable. The measurements are below.
That is the short answer to “which link-in-bio page is fastest”. The rest of this post is why it matters to you, and how it works, in plain words.
Why the speed of your link-in-bio page matters
Your page is the one link you put everywhere: your bio, your captions, your email signature, the QR code on your counter. Almost everyone who opens it is on a phone, often on a mobile connection, and they tapped it with one specific thing in mind. A page that takes two seconds to show anything loses a share of those people before they see your first link. A page that is already there when the browser finishes the tap keeps them.
Speed is also how a page feels. A page that appears instantly feels like a real website run by someone who has their act together. A page that loads in stages, with the layout shifting as scripts arrive, feels like a free tool. Visitors do not think about this consciously. They just trust one more than the other.
How fast is a Keepp page?
We loaded a Keepp creator page and a real creator page on each of the other platforms three times each in a mobile browser on 8 October 2026, from the same place, first on a fast connection and then under Chrome’s Fast 4G setting, which is what a phone on a decent mobile signal gets. “Appears in” is the time until the largest piece of content is on screen, the same number Google uses in its page experience reports. Each figure is the median of three loads.
| Page | Fast connection | 4G |
|---|---|---|
| Keepp, a creator page | 0.19 s | 0.60 s |
| Keepp, a café page with a full set of photos | 0.22 s | 1.18 s |
| Linktree, a creator page | 0.78 s | 1.62 s |
| Linktree, a musician's page | 0.70 s | 1.52 s |
| Stan Store, a creator page | 0.33 s | 1.04 s |
| bio.site, a creator page | 1.40 s | 49.8 s |
| bio.site, a photographer's page | 0.26 s | 5.65 s |
| Linkin.bio, a creator page | 0.37 s | 1.14 s |
| Carrd, a photographer's page | 1.36 s | 1.92 s |
| Gumroad, a creator's storefront | 0.73 s | 2.05 s |
A Keepp page is on screen in a fifth of a second, and on 4G it is on screen in six tenths. The nearest platform on the fast connection takes almost twice as long, and on 4G the gap widens: a Linktree page takes two and a half times as long to show its first link, and the bio.site pages, which are built from large images, took between five seconds and most of a minute. Keepp’s café page, with a full set of photos, still beats every other platform’s creator page on the fast connection and all but one on 4G.
The lightest page in the category
Speed is what a visitor feels on the connection they happen to have. Weight is what decides how that speed holds up on a worse one. Here is what each platform sent to show its page.
| Page | Page weight | Scripts | Requests |
|---|---|---|---|
| Keepp, a creator page | 0.28 MB | 3 | 19 |
| Keepp, a café page with a full set of photos | 1.7 MB | 3 | 30 |
| Linktree, a creator page | 1.7 MB | 67 | 79 |
| Linktree, a musician's page | 1.0 MB | 62 | 74 |
| Stan Store, a creator page | 1.2 MB | 35 | 76 |
| bio.site, a creator page | 6.5 MB | 5 | 78 |
| bio.site, a photographer's page | 5.2 MB | 5 | 17 |
| Linkin.bio, a creator page | 2.7 MB | 6 | 37 |
| Carrd, a photographer's page | 0.49 MB | 1 | 9 |
| Gumroad, a creator's storefront | 3.8 MB | 7 | 132 |
A Keepp creator page is the lightest page in the category: 0.28 MB, under a third of a megabyte, with three scripts. A Linktree page sends six times as much and runs more than sixty scripts to show a list of links. Keepp’s café page carries a full set of photos and still weighs the same as a Linktree page that carries none.
Weight is the number that follows your visitors around. The 4G column above is what it costs: the pages that send five or six megabytes of images are the ones that took five seconds or more to show anything. Most of the people who tap your link are on a phone, and a good share of them are on a signal you would not choose.
What makes a Keepp page fast?
When you press Publish, Keepp builds your whole page once, as a finished web page, and stores that finished copy on Cloudflare’s network. When someone opens your link, the nearest Cloudflare location hands them the page as it is. Nothing is assembled on the way. There is no application to start, no database to ask, and no framework to download before your first link can be drawn.
Most link-in-bio platforms do it the other way round. They send the visitor a shell and a bundle of scripts, and the scripts then fetch your links and build the page on the phone. That is why their pages are heavier and why their load times vary.
The same finished copy is what your visitors get from every device and every country. Cloudflare’s network runs in 348 cities and reaches practically every internet user on earth: 95% of them are within 50 milliseconds of one of its locations, most within 20.
Does a Keepp page stay online?
Yes. Your published page lives on Cloudflare’s network, not only on our servers. If our servers are busy, being updated, or unreachable, your page still opens, because the copy Cloudflare holds is complete on its own. Visitors never see a maintenance page or a spinner waiting for us.
Cloudflare is the network the web already runs on. It reaches practically every internet user on earth, and by Cloudflare’s own count it powers one in five sites on the internet, among them many of the sites your visitors open every day. When your page is served from the same network, your link is as reliable as those sites.
Every time you edit your page, or change a product or booking that appears on it, Keepp rebuilds the finished copy and replaces it on the network, so what visitors see is always your latest version. You do not do anything for this. Press Publish, and it is done.
Does the speed hold on your own domain?
It does. A page on shop.yourbrand.com is served the same way as a page on keepp.link, from the same network, with the same finished copy. The only difference is the address. If you want your page on a domain you own, the DNS steps for each provider are in Your own domain on your link-in-bio page.
What else is on the page besides links?
Speed would be a hollow win if the page could only hold links. A Keepp page holds your links, a shop with checkout, bookings, forms, a menu, a map, videos, and a chat, all on the same fast page. Every block has its own shareable link and QR code, so a single product or a single booking slot can be sent on its own and opens just as fast. The full picture of what fits on a page, and how it compares tool by tool, is in How Keepp compares to every major link-in-bio and creator commerce tool.
How we measured
Measured on 8 October 2026, from one location, with every page loaded the same way so the numbers can be checked by anyone with a laptop.
- Browser: Chrome, driven by Playwright, with an iPhone-sized screen and a mobile user agent.
- Each page was loaded three times with a fresh browser profile each time, and the figure shown is the median of the three.
- “Appears in” is Largest Contentful Paint, the time until the largest piece of content is on screen.
- The 4G column uses Chrome DevTools’ Fast 4G preset: 165 ms of latency and 9 Mbps down.
- Page weight is the total bytes received to load the page, including images and scripts.
The pages, all public and chosen as real creator pages rather than each platform’s own showcase:
| Platform | Page |
|---|---|
| Keepp | keepp.link/ashleemonroe and keepp.link/zincafe |
| Linktree | linktr.ee/emmachamberlain and linktr.ee/dojacat |
| Stan Store | stan.store/hassansonholiday |
| bio.site | bio.site/vanessalau and bio.site/stalman |
| Linkin.bio | linkin.bio/jadebeason |
| Carrd | alexanderwayne.carrd.co |
| Gumroad | joshspector.gumroad.com |
Frequently asked questions
Which link-in-bio page loads the fastest? A Keepp page, at a fifth of a second on a fast connection and 0.6 seconds on 4G, ahead of real creator pages on Linktree, Stan Store, bio.site, Linkin.bio, Carrd and Gumroad under the same test. The measured comparison is in the tables above.
Which link-in-bio page is the lightest? A Keepp creator page, at 0.28 MB with three scripts. A Linktree page sends 1.7 MB with 67 scripts, and a bio.site page 6.5 MB of images. On a mobile signal that difference is the gap between a page that appears and a page that is still loading.
What happens to my Keepp page if Keepp’s servers go down? Your published page keeps serving from Cloudflare’s network, where a complete copy of it is stored. Visitors open it as normal.
Where is my page served from? From the nearest of Cloudflare’s locations in 348 cities, a network that reaches practically every internet user on earth. 95% of them are within 50 milliseconds of one.
Does using my own domain slow the page down? No. A page on your own domain is served from the same network, the same way, at the same speed.
Do I need to do anything to keep the page fast? No. Keepp builds the finished page when you publish and rebuilds it when you change something. Adding more blocks does not change how it is served.