Technical proof
Speed, measured from 6 continents
We do not ask anyone to take our performance on trust. Here is the whole battery: 78 measurements taken by physical probes in 14 cities across 12 countries, the raw file to download, the method to run it again, and what these figures do not prove.
The fleet, in four figures
The fleet, in four figures
Battery of 31 July 2026, taken with the public Globalping probes. The raw file sits at the foot of this page.
On the real web, 44% of sites meet Google’s good threshold for response time on mobile. In our battery: 76 measurements out of 78.
Web distribution: HTTP Archive Web Almanac 2025, from Chrome UX Report data of July 2025. Our figures: battery of 31 July 2026, raw file at the foot of this page.
Why it is fast
Why it is fast
Pages already written
Our sites are files, not programs. There is no database to query and no template to assemble when a visitor arrives: the page requested already exists, in full, before anyone asks for it. The server only has to hand it over.
Served from the city next door
Every page is copied across our host’s worldwide network and served from the point of presence nearest the visitor. A student in Mumbai does not download Paris: she downloads Mumbai. That is exactly what the 14 cities on this page measure.
Nothing loaded from anyone else
No font, no script, no image and no audience measurement comes from another domain. A page that depends on nobody cannot be slowed down by anybody, and checking it takes thirty seconds in any browser’s network inspector.
Light by construction
Text first, photographs given their dimensions, fonts carried with the page, and the page stays readable even if the script never runs. Speed here is no feat of engineering: it is what remains once nothing useless has been added.
What this figure measures, and what it does not
Every measurement on this page is a response time: the delay between the browser asking for the page and the first byte of the answer arriving. It is the foundation, not the house.
- What it includes
- Resolving the domain name, opening the connection, negotiating encryption, then waiting for the answer. Across our battery the median connection opens in 2 ms and the median encryption takes 11 ms.
- What it leaves out
- Downloading the rest of the page, drawing it, laying it out. A short response time does not guarantee a page that feels fast, which is why we publish Google’s scores as well: those measure what appears on screen.
- Why Google’s threshold sits at 800 ms
- Because beyond it the first paint no longer fits inside the budget Google treats as good. The threshold is read at the 75th percentile of real visits: it is not enough for half the measurements to pass, three quarters must.
- Why we aim for 200 ms
- Because that is the bar commonly quoted for excellent infrastructure, and it suits us better: 57 of our 78 measurements clear it. It is no longer an official Google threshold, and we would rather write that down than lay claim to it.
Response time, continent by continent
Each row gathers the measurements taken on that continent, across all of our sites, fastest first. The median is the value that splits the measurements into two equal halves.
| Continent | Cities probed | Measurements | Median | Fastest | Slowest |
|---|---|---|---|---|---|
| Europe | 3 | 18 | 39 ms | 17 ms | 486 ms |
| North America | 3 | 18 | 49 ms | 21 ms | 102 ms |
| Oceania | 1 | 6 | 116 ms | 21 ms | 285 ms |
| South America | 1 | 6 | 139 ms | 28 ms | 151 ms |
| Asia | 4 | 24 | 233 ms | 21 ms | 8,145 ms |
| Africa | 2 | 6 | 252 ms | 30 ms | 268 ms |
The continent is derived from the country of the probe. Not one figure in this table is written by hand: they are all recalculated from the raw file every time the site is published.
Site by site, across the fleet
The 6 sites the association publishes, measured in the same pass. The median shown here is the one for answers already cached: the ordinary visitor’s experience.
| Address | Measurements | Cached | Cached median | Fastest | Slowest |
|---|---|---|---|---|---|
odersa.org | 13 | 11/13 | 24 ms | 17 ms | 497 ms |
letabli.odersa.org | 13 | 6/13 | 40 ms | 27 ms | 449 ms |
depleindroit.odersa.org | 13 | 11/13 | 48 ms | 25 ms | 790 ms |
avantlessecours.odersa.org | 13 | 11/13 | 50 ms | 22 ms | 2,723 ms |
clicparclic.odersa.org | 13 | 12/13 | 56 ms | 21 ms | 8,145 ms |
avantdycroire.odersa.org | 13 | 10/13 | 116 ms | 25 ms | 791 ms |
The spread between our sites comes from how often they are visited, not from their code: a page rarely requested in a region is not cached there yet. Between 24 and 116 ms of median, all of them stay far below Google’s threshold.
The full record, city by city
The 14 cities of the battery, each with its measurements across our 6 sites. This is the least flattering of the three tables, which is exactly why it is here: nothing has been removed.
| City | Continent | Measurements | Cached | Median | Fastest | Slowest |
|---|---|---|---|---|---|---|
| London | Europe | 6 | 6/6 | 25 ms | 23 ms | 64 ms |
| New York | North America | 6 | 6/6 | 32 ms | 24 ms | 50 ms |
| Falkenstein | Europe | 6 | 6/6 | 40 ms | 29 ms | 486 ms |
| Warsaw | Europe | 6 | 6/6 | 46 ms | 17 ms | 117 ms |
| Toronto | North America | 6 | 6/6 | 57 ms | 34 ms | 97 ms |
| Tokyo | Asia | 6 | 5/6 | 64 ms | 21 ms | 267 ms |
| Los Angeles | North America | 6 | 6/6 | 81 ms | 21 ms | 102 ms |
| Singapore | Asia | 6 | 4/6 | 113 ms | 28 ms | 215 ms |
| Sydney | Oceania | 6 | 5/6 | 116 ms | 21 ms | 285 ms |
| Sao Paulo | South America | 6 | 5/6 | 139 ms | 28 ms | 151 ms |
| Johannesburg | Africa | 5 | 4/5 | 248 ms | 30 ms | 258 ms |
| Cape Town | Africa | 1 | 1/1 | 268 ms | 268 ms | 268 ms |
| Mumbai | Asia | 6 | 0/6 | 269 ms | 215 ms | 335 ms |
| Dubai | Asia | 6 | 1/6 | 791 ms | 449 ms | 8,145 ms |
A city where few measurements were cached shows a higher median: that is the first visitor in the region waiting, once, while the page settles in nearby.
Our measurements against public benchmarks
The gap column compares our median of 94 ms with the benchmark on that row. None of these benchmarks are ours: each carries its source, and the address opens in one click.
| Public benchmark | Benchmark value | Gap with our median | Source |
|---|---|---|---|
| Google’s good threshold for response time | 800 ms | × 9 | web.dev (Google) |
| Google’s poor threshold, beyond which a site is flagged | 1,800 ms | × 19 | web.dev (Google) |
| Bar commonly quoted for excellent infrastructure | 200 ms | × 2 | Auditite, 2026 benchmarks |
| Median of the fastest sector in that record: finance | 400 ms | × 4 | Auditite, 2026 benchmarks |
| Median of the healthcare sector | 600 ms | × 6 | Auditite, 2026 benchmarks |
| Median of the media sector | 750 ms | × 8 | Auditite, 2026 benchmarks |
Stated reservation: the source of these sector medians publishes neither its method nor its sample, and it lists sectors beyond these three. We quote it as an order of magnitude, never as proof. The 200 ms bar is no longer an official Google threshold either: it comes from documentation withdrawn in 2019. Our own figures, by contrast, recalculate in front of you from the raw file.
Google’s public scores
PageSpeed Insights is Google’s public tool: anyone can run it on our pages and on other people’s, then compare. Recorded on desktop on 31 July 2026.
| What is measured | Desktop result |
|---|---|
| Performance | 100 / 100 |
| Accessibility | 100 / 100 |
| Best practices | 100 / 100 |
| Search | 100 / 100 |
| Largest element painted | 0.4 s |
| Layout stability | 0.001 |
We are not copying a mobile score here. A score has a date, and ours has just been corrected for a stability fault specific to phone rendering: the honest way to know it is to run the tool, not to read us.
Run the measurements yourself
Everything on this page can be reproduced without us. Both tools are public and free, and neither asks for an account.
- Open the Globalping probe service, pick the HTTP test, enter odersa.org as the address and the whole world as the origin: physical probes spread across the planet will query the site and show their own timings, just like ours.
- Open PageSpeed Insights, paste the address of one of our pages, and read the four scores and the paint measurements. Do the same on another site to give yourself a point of comparison.
- Open any page of ours, press F12, go to the Network tab and reload: every request carries our own domain, and none leaves for anywhere else.
- Download the raw file at the foot of this page and recalculate our medians: you should find the figures in our tables, row for row.
A repeated measurement will not return exactly ours: the probes available change from hour to hour and each one’s network varies. That is what an honest measurement looks like. The orders of magnitude, however, hold.
Our reservations, written before anyone raises them
A measurement without its limits is an advertisement. Here are the limits of ours.
- These figures are a snapshot from 31 July 2026, not a permanent guarantee. Unlike the figures about our content, which recount themselves at every publication, a network measurement means running the probes again.
- 17 of our 78 measurements found the regional cache empty: that is the first visitor in a region waiting, with a median of 270 ms instead of 47 ms. Once. We checked it live on Sydney, where the second request came back in line with the rest.
- Share of the battery coming from probes whose own connection was slow: 1 out of 78. It is readable in the raw file, where their connection alone takes more than one hundred milliseconds, before we have answered anything. We keep them in the tables rather than setting them aside.
- A probe is not a visitor. It measures a network and a server, not a second-hand phone on a congested network. Google’s scores cover that part, and Google measures them, not us.
- Speed is not teaching. A fast site that teaches badly is still a bad site. This page proves one thing and one thing only: that our infrastructure is not in the way.
- We publish no visitor counts, because we collect nothing that would let us count them. What you read here measures our servers, never our readers.
The raw record, as open data
The file our tables summarise, exactly as it came out of the probes: one row per measurement, with the site queried, the city, the cache state and the detailed timings. Under the CC BY 4.0 licence, like everything else we publish.
Read next
Read next
Impact & figures
The figures about our content are recounted at every publication from the projects’ own public data.
See the figures →Our approach
Free of charge, openly licensed, zero data collection: every commitment with the way to check it.
Read the commitments →Accessibility
What is in place, what is still to come, and how to test a page yourself.
Read the statement →