slashdot.org speed test — 20 Oct 2026

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

https://slashdot.org/

20 October 2026 at 13:18 UTC · Free test · report pt_f59a1f2a9fc6
Grade
A
93/100
Performance100/100
Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)215 msmeasured from this server
Fully loaded1.18 sfirst byte + slowest asset
Requests26document + assets
Page weight387.3 KBcompressed transfer
HTML document35.8 KBzstd
ProtocolHTTP/3cloudflare
Third-party350.7 KBother hosts

Where the first byte went

  • DNS lookup 57 ms 27%
  • TCP connect 31 ms 14%
  • Server wait 127 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 90% of 4,999 pages tested here215 ms against a median of 449 ms
Page weightlighter than 66% of 4,999 pages tested here387.3 KB against a median of 650.5 KB
Fully loadedfaster than 88% of 4,999 pages tested here1.18 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 215 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 387.3 KB over 26 request(s). Javascript files are 40% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 91% 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 540 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.074), so nothing jumps under the reader's cursor.

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.

Screenshot

What the page looks like

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

Mobile screenshot of slashdot.org
Mobile 390 × 844 · 130.8 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 paint540 msgood is under 2.5 s
Cumulative layout shift0.074under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint540 msfirst content on screen
Browser page weight710.6 KB66 request(s), scripts included
Largest contentful paint540 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.074
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 6 requests
155.9 KB 40%
Images 16 requests
140.5 KB 36%
Css 3 requests
55.1 KB 14%

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

Top issues

Render-blocking resources

high impact

8 render-blocking resource(s) in the document head (3 script(s), 5 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.

TLS certificate validity

high impact

The certificate for slashdot.org has 21 day(s) left.

Fix: Renew automatically (certbot with a working renewal timer) and alert on the certificate, not on the renew command, so a silent failure is caught weeks before a browser warning.

Cache static assets

medium impact

1 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 350.7 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.

Waterfall

Slowest requests

IMAGESa.fsdn.com/sd/topics/privacy_64.png
961 ms
IMAGESa.fsdn.com/sd/topics/business_64.png
923 ms
IMAGESslashdot.org/images/njs.gif
919 ms
IMAGESa.fsdn.com/sd/topics/applelaptop_64.png
918 ms
IMAGESa.fsdn.com/sd/NewsletterSubscription.png
915 ms
IMAGESa.fsdn.com/sd/topics/wine_64.png
914 ms
IMAGESa.fsdn.com/sd/topics/government_64.png
910 ms
IMAGESa.fsdn.com/sd/topics/wireless_64.png
910 ms
IMAGESa.fsdn.com/sd/topics/movies_64.png
908 ms
IMAGESa.fsdn.com/sd/topics/security_64.png
901 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://a.fsdn.com/sd/topics/privacy_64.png 3rd partyimages200961 ms4.8 KB
https://a.fsdn.com/sd/topics/business_64.png 3rd partyimages200923 ms5.5 KB
https://slashdot.org/images/njs.gif?579images200919 ms49 B
https://a.fsdn.com/sd/topics/applelaptop_64.png 3rd partyimages200918 ms2.2 KB
https://a.fsdn.com/sd/NewsletterSubscription.png?v=2 3rd partyimages200915 ms88.5 KB
https://a.fsdn.com/sd/topics/wine_64.png 3rd partyimages200914 ms3.4 KB
https://a.fsdn.com/sd/topics/government_64.png 3rd partyimages200910 ms3.6 KB
https://a.fsdn.com/sd/topics/wireless_64.png 3rd partyimages200910 ms3.2 KB
https://a.fsdn.com/sd/topics/movies_64.png 3rd partyimages200908 ms2.7 KB
https://a.fsdn.com/sd/topics/security_64.png 3rd partyimages200901 ms4.3 KB
https://a.fsdn.com/sd/topics/power_64.png 3rd partyimages200900 ms4.1 KB
https://a.fsdn.com/sd/classic.css?0ab6e7235c60a5c8 3rd partycss200899 ms31.9 KB
https://a.fsdn.com/con/js/sandiego/floating-unit.js?2026-09-15 3rd partyjavascript200893 ms10.8 KB
https://a.fsdn.com/sd/topics/mars_64.png 3rd partyimages200893 ms6.8 KB
https://slashdot.org/favicon.icoimages200890 ms775 B
https://a.fsdn.com/sd/topics/ai_64.png 3rd partyimages200889 ms6.8 KB
https://a.fsdn.com/con/css/sftheme/sandiego/cmp.css?2026-09-15 3rd partycss200884 ms1.0 KB
https://a.fsdn.com/sd/js/scripts/asg_embed.js?0ab6e7235c60a5c8 3rd partyjavascript200883 ms28 B
https://a.fsdn.com/con/js/sandiego/maxnav.js?2026-09-15 3rd partyjavascript200877 ms363 B
https://a.fsdn.com/sd/css/app.css?0ab6e7235c60a5c8 3rd partycss200872 ms22.1 KB
https://a.fsdn.com/sd/ccpa-optout.png 3rd partyimages200870 ms1.0 KB
https://a.fsdn.com/sd/all-minified.js?0ab6e7235c60a5c8 3rd partyjavascript200869 ms124.3 KB
https://a.fsdn.com/sd/topics/mozilla_64.png 3rd partyimages200866 ms2.8 KB
https://a.fsdn.com/sd/js/scripts/admanager.js?0ab6e7235c60a5c8 3rd partyjavascript200863 ms32 B
https://a.fsdn.com/con/js/sftheme/cmp-slashdot.js?2026-09-15 3rd partyjavascript200862 ms20.5 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.