www.snopes.com speed test — 20 Oct 2026

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

https://www.snopes.com/

20 October 2026 at 14:01 UTC · Free test · report pt_1485ca90e648
Grade
E
54/100
Performance39/100
Structure77/100

10 audit(s) passed, 6 need work

First byte (TTFB)5.24 smeasured from this server
Fully loaded10.39 sfirst byte + slowest asset
Requests26document + assets
Page weight964.9 KBcompressed transfer
HTML document91.6 KBbr
ProtocolHTTP/3cloudflare
Third-party549.3 KBother hosts

Where the first byte went

  • DNS lookup 5.10 s 97%
  • TCP connect 26 ms 0%
  • Server wait 113 ms 2%

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 byteslower than 99% of 4,999 pages tested here5.24 s against a median of 448 ms
Page weightheavier than 61% of 4,999 pages tested here964.9 KB against a median of 650.3 KB
Fully loadedslower than 99% of 4,999 pages tested here10.39 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 took 5.24 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 964.9 KB over 26 request(s). Javascript files are 49% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 57% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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

Javascript 6 requests
475.6 KB 49%
Images 19 requests
397.7 KB 41%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 5236 ms. Of that, 113 ms was the server thinking and 5123 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Total page weight

medium impact

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

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

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

5 third-party host(s) serve 549.3 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.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

IMAGESmediaproxy.snopes.com/width/600/https://media.snopes.com/202…
5.15 s
JAVASCRIPTwww.googletagmanager.com/gtag/js
5.15 s
JAVASCRIPTdist.bigcrunch.com/lighthouse/main.js
5.15 s
JAVASCRIPTdist.bigcrunch.com/cmp/cmp.js
5.15 s
IMAGESmediaproxy.snopes.com/width/900/https://media.snopes.com/202…
5.15 s
JAVASCRIPTwww.snopes.com/design/assets/bundle.js
5.15 s
IMAGESmediaproxy.snopes.com/width/400/https://media.snopes.com/202…
5.15 s
IMAGESmediaproxy.snopes.com/width/400/https://media.snopes.com/202…
5.15 s
IMAGESmediaproxy.snopes.com/width/400/https://media.snopes.com/202…
5.15 s
IMAGESwww.snopes.com/design/images/logo-main.png
5.15 s

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://mediaproxy.snopes.com/width/600/https://media.snopes.com/2026/10/voters_in_line_at_a_polling_place.png 3rd partyimages2005.15 s38.9 KB
https://www.googletagmanager.com/gtag/js?id=G-Q9SR89WW85 3rd partyjavascript2005.15 s186.4 KB
https://dist.bigcrunch.com/lighthouse/main.js 3rd partyjavascript2005.15 s115.1 KB
https://dist.bigcrunch.com/cmp/cmp.js 3rd partyjavascript2005.15 s73.5 KB
https://mediaproxy.snopes.com/width/900/https://media.snopes.com/2026/10/voters_in_line_at_a_polling_place.png 3rd partyimages2005.15 s72.5 KB
https://www.snopes.com/design/assets/bundle.js?rev=44309cc7f579c89707fbfa4521607f175266650ejavascript2005.15 s61.0 KB
https://mediaproxy.snopes.com/width/400/https://media.snopes.com/2026/10/facade_of_a_kroger.jpg 3rd partyimages2005.15 s23.1 KB
https://mediaproxy.snopes.com/width/400/https://media.snopes.com/2026/10/did_rioters_in_paris_and_marseille_target_synagogue_and_jewish_businesses_sparing_muslim_ones.png 3rd partyimages2005.15 s21.3 KB
https://mediaproxy.snopes.com/width/400/https://media.snopes.com/2026/10/if_poll_workers_mark_your_ballot_is_it_disqualified_we_looked_into_the_claim.png 3rd partyimages2005.15 s18.0 KB
https://www.snopes.com/design/images/logo-main.pngimages2005.15 s17.2 KB
https://www.snopes.com/apple-touch-icon.pngimages2005.15 s12.2 KB
https://www.snopes.com/design/images/snopes_default_square.pngimages2005.15 s8.9 KB
https://applets.ebxcdn.com/ebx.js 3rd partyjavascript2005.15 s322 B
https://sb.scorecardresearch.com/p?c1=2&c2=38282683&cv=3.6.0&cj=1 3rd partyimages2005.15 s43 B
https://www.snopes.com/design/images/ifcn_badge.pngimages2005.15 s84.2 KB
https://www.snopes.com/design/js/swiper-bundle.min.jsjavascript2005.15 s39.3 KB
https://www.snopes.com/design/images/logo-main-shadow.pngimages2005.15 s23.7 KB
https://www.snopes.com/design/images/badge_of_honor.pngimages2005.15 s15.4 KB
https://www.snopes.com/apple-touch-icon-precomposed.pngimages2005.15 s12.2 KB
https://www.snopes.com/apple-touch-icon-152x152-precomposed.pngimages2005.15 s11.2 KB
https://www.snopes.com/design/images/NewsGuard_logo_white.pngimages2005.15 s7.4 KB
https://www.snopes.com/apple-touch-icon-152x152.pngimages2005.15 s11.2 KB
https://www.snopes.com/apple-touch-icon-120x120.pngimages2005.15 s8.9 KB
https://www.snopes.com/apple-touch-icon-120x120-precomposed.pngimages2005.15 s8.9 KB
https://www.snopes.com/favicon-32x32.pngimages2005.15 s2.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.