disqus.com speed test — 20 Oct 2026

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

https://disqus.com/

20 October 2026 at 12:31 UTC · Free test · report pt_726126d832d6

Re-test this page Test your own site

Grade

98/100

Performance97/100

Structure100/100

16 audit(s) passed, 0 need work

First byte (TTFB)300 msmeasured from this server

Fully loaded1.24 sfirst byte + slowest asset

Requests18document + assets

Page weight136.0 KBcompressed transfer

HTML document1.7 KBgzip

ProtocolHTTP/2nginx

Third-party134.4 KBother hosts

Where the first byte went

DNS lookup 48 ms 16%
TCP connect 75 ms 25%
Server wait 178 ms 59%

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

Page weightlighter than 84% of 4,999 pages tested here136.0 KB against a median of 650.5 KB

Fully loadedfaster than 86% of 4,999 pages tested here1.24 s against a median of 1.84 s

Requestssends fewer requests than 81% of 4,999 pages tested here18 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 300 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 136.0 KB over 18 request(s). Javascript files are 89% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.08 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.013), so nothing jumps under the reader's cursor.
The main thread was blocked for 730 ms, so taps and scrolling wait while scripts run.

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.

Mobile screenshot of disqus.com — **Mobile** 390 × 844 · 62.3 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 paint1.08 sgood is under 2.5 s

Cumulative layout shift0.013under 0.1 is stable

Total blocking time730 mslong tasks during load

First contentful paint728 msfirst content on screen

Browser page weight3.41 MB95 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint1.08 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.013

Goodgood under 0.1, poor over 0.25

Total blocking time730 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests

120.9 KB 89%

Images 14 requests

8.7 KB 6%

Html 1 request

4.8 KB 3%

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

No failing audits: the page passes everything this test can check.