WhatsApp Web Is Measured at 11.8 Seconds to Load, One of the Slowest Popular Sites on the Web

WhatsApp Web is one of the most-used web applications on the planet, and in Google's public field data it is measured at 11.8 seconds to render its main content on a phone, nearly five times the threshold for a good experience. It is not alone. Google Cloud Console, Cloudflare's dashboard, Facebook's Ads Manager, Google's own Looker Studio and WeTransfer all sit near the top of a list nobody wants to lead: the most-visited sites on the internet that are also among its slowest.

This matters because these are not obscure pages. They are tools people open every day to run businesses, move money and talk to family, and speed shapes every one of those sessions. Google's research links slow pages to sharply higher abandonment, slow responses to lost interactions, and Core Web Vitals to search ranking since 2021. When a household-name tool takes ten seconds to appear and more than a second to answer a tap, the cost lands on real users, in real time, at scale.

None of these figures come from a synthetic test. They are drawn from the Chrome User Experience Report, Google's public record of what real Chrome users experienced on real devices and networks, the same field data Google's ranking systems draw on. Ranked by how slowly they load, the top of the list reads like a tour of the software people rely on most.

We queried the Chrome User Experience Report for origins in roughly the top 5,000 by CrUX popularity rank, a proxy for real visitor traffic, that fall short of Core Web Vitals, and ordered them by mobile 75th-percentile Largest Contentful Paint, slowest first. Restricting to popular sites keeps the list to tools people actually use, which is what separates this study from a market-value ranking.

A good LCP is 2.5 seconds or under at the 75th percentile, a good Interaction to Next Paint is 200 milliseconds or under, and a good Cumulative Layout Shift is 0.1 or under. Each value below is a real field measurement in Google's public dataset, a figure any site can improve, and one most sites clear comfortably. The sites here are the exceptions, measured at four to five times the good bar for loading.

WhatsApp Web is measured at 11.8 seconds to paint its main content at the 75th percentile on mobile, and its Interaction to Next Paint is measured at 1,450 milliseconds, more than seven times the 200 ms threshold. Google Cloud Console comes in at 11.5 seconds, Cloudflare's dashboard at 10.9, Facebook's Ads Manager at 12.1 with a 1,600 ms INP, Google's Looker Studio at 10.3, and WeTransfer at 9.6. Major e-commerce is represented too: South Africa's takealot.com is measured at a 13.2-second LCP. A notable share of the slowest popular sites are online casinos and betting platforms.

There is a common thread, and it is not that these companies failed. Almost none of these are web pages. They are web applications, dashboards, consoles and chat clients that render their entire interface in the browser with large JavaScript bundles. They serve enormous global audiences on every device and network, from the newest phones to older handsets on slow connections, so their field data reflects the full range of real-world conditions rather than a best case. Many are complex authenticated experiences, loading personalized data, permissions and live state before anything useful can appear. That architecture asks the phone to download, parse and execute a large amount of code up front, and then keeps the main thread busy so taps respond more slowly.

This is the same pattern our popularity-tier study found across the whole web: the most popular sites tend to be the most JavaScript-heavy, which serves them well in aggregate but leaves the genuinely complex apps among them slower on real devices. The gambling sites are a category of their own, typically packed with third-party game embeds, live-odds widgets, tracking and ad-tech all loading at once. The responsiveness picture follows the loading one, with the heaviest apps keeping the main thread busy long after the page appears.

The full list makes the shape clear. Every entry is a household name or a heavily used tool, and every one is a web application rather than a document, clustered at nine to thirteen seconds to load with a long run of betting and casino sites behind them.

Mobile, 75th percentile, May 2026 CrUX. Plus a long run of betting and casino sites (betpawa, sportingbet, casinoplus, congobet) clustered at 9.5 to 12.5 s.

For anyone using these tools, the lesson is that scale does not buy speed: WhatsApp Web is measured at 11.8 seconds to paint and 1,450 ms to answer a tap, and on a slower phone or connection those figures run higher still. For the teams building them, the list is a clear picture of the cost of shipping an entire application to the browser. Almost every entry is a client-rendered web app, from Facebook Ads Manager at 12.1 seconds to takealot.com at 13.2, and the convenience of that architecture becomes a wait near ten seconds for the people signed in every day.

Every one of these figures is improvable, and the levers are well understood. Server-render the initial view, then code-split and defer the JavaScript the first paint does not need. The payoff scales with the audience, which is why WhatsApp Web and Google Cloud Console at 11.5 seconds have the most to gain: the seconds they save are multiplied across millions of daily sessions. The slowest popular sites today, clustered at nine to thirteen seconds, are the largest performance wins waiting to happen.