joinmastodon.org speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:58 UTC. Grade B (88/100), with the screenshots, the timings and the fixes that matter.

https://joinmastodon.org/

20 October 2026 at 14:58 UTC · Free test · report pt_242b24b8d1ec

Re-test this page Test your own site

Grade

88/100

Performance90/100

Structure85/100

14 audit(s) passed, 2 need work

First byte (TTFB)200 msmeasured from this server

Fully loaded2.37 sfirst byte + slowest asset

Requests26document + assets

Page weight1.70 MBcompressed transfer

HTML document12.7 KBbr

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 82 ms 41%
TCP connect 25 ms 13%
Server wait 93 ms 47%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 92% of 4,999 pages tested here200 ms against a median of 449 ms

Page weightheavier than 77% of 4,999 pages tested here1.70 MB against a median of 650.3 KB

Fully loadedslower than 70% of 4,999 pages tested here2.37 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The server answered in 200 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 1.70 MB over 26 request(s). Images files are 99% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 728 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.012), so nothing jumps under the reader's cursor.
The main thread was blocked for 232 ms, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Desktop screenshot of joinmastodon.org — **Desktop** 1366 × 768 · 249.0 KB · page is 6000 px tall

Mobile screenshot of joinmastodon.org — **Mobile** 390 × 844 · 126.0 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint728 msgood is under 2.5 s

Cumulative layout shift0.012under 0.1 is stable

Total blocking time232 mslong tasks during load

First contentful paint520 msfirst content on screen

Browser page weight1.25 MB54 request(s), scripts included

Largest contentful paint728 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.012

Goodgood under 0.1, poor over 0.25

Total blocking time232 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

1.68 MB 99%

Transfer size, compressed as sent. 26 request(s) in total, 1.70 MB across all of them.

Top issues

Image delivery and format

high impact

1 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 1.70 MB across 26 request(s), with the document itself at 12.7 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.