www.classdojo.com speed test — 20 Oct 2026

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

https://www.classdojo.com/

20 October 2026 at 14:27 UTC · Free test · report pt_92a19f8f4486

Re-test this page Test your own site

Grade

90/100

Performance99/100

Structure76/100

10 audit(s) passed, 6 need work

First byte (TTFB)230 msmeasured from this server

Fully loaded1.41 sfirst byte + slowest asset

Requests26document + assets

Page weight930.4 KBcompressed transfer

HTML document122.5 KBgzip

ProtocolHTTP/3AmazonS3

Third-party807.9 KBother hosts

Where the first byte went

DNS lookup 68 ms 30%
TCP connect 29 ms 13%
Server wait 134 ms 58%

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 88% of 4,999 pages tested here230 ms against a median of 449 ms

Page weightheavier than 60% of 4,999 pages tested here930.4 KB against a median of 650.3 KB

Fully loadedfaster than 76% of 4,999 pages tested here1.41 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 first byte arrived in 230 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 930.4 KB over 26 request(s). Images files are 87% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
87% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 25 requests

807.9 KB 87%

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

Top issues

Render-blocking resources

high impact

4 render-blocking resource(s) in the document head (4 script(s), 0 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

medium impact

The page transfers 930.4 KB across 26 request(s), with the document itself at 122.5 KB.

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

Cache static assets

medium impact

5 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Third-party weight

medium impact

1 third-party host(s) serve 807.9 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

HTML document size

medium impact

The document transfers 122.5 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.