www.wireshark.org speed test — 20 Oct 2026

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

https://www.wireshark.org/

20 October 2026 at 13:33 UTC · Free test · report pt_b738db0fb22a
Grade
C
74/100
Performance76/100
Structure71/100

10 audit(s) passed, 6 need work

First byte (TTFB)445 msmeasured from this server
Fully loaded1.52 sfirst byte + slowest asset
Requests17document + assets
Page weight3.00 MBcompressed transfer
HTML document42.3 KBbr
ProtocolHTTP/3cloudflare
Third-party385.5 KBother hosts

Where the first byte went

  • DNS lookup 56 ms 13%
  • TCP connect 25 ms 6%
  • Server wait 364 ms 82%

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 50% of 4,999 pages tested here445 ms against a median of 449 ms
Page weightheavier than 88% of 4,999 pages tested here3.00 MB against a median of 650.3 KB
Fully loadedfaster than 69% of 4,999 pages tested here1.52 s against a median of 1.84 s
Requestssends fewer requests than 82% of 4,999 pages tested here17 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 445 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 3.00 MB over 17 request(s). Images files are 92% 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 1.06 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.006), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 5 ms in total, which is not enough to feel.

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.

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.06 sgood is under 2.5 s
Cumulative layout shift0.006under 0.1 is stable
Total blocking time5 mslong tasks during load
First contentful paint580 msfirst content on screen
Browser page weight3.03 MB19 request(s), scripts included
Largest contentful paint1.06 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.006
Goodgood under 0.1, poor over 0.25
Total blocking time5 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 11 requests
2.76 MB 92%
Javascript 2 requests
187.5 KB 6%
Css 3 requests
23.6 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 445 ms. Of that, 364 ms was the server thinking and 81 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.

Image delivery and format

high impact

2 image(s) over 200 KB and 3 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.

Render-blocking resources

high impact

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

high impact

The page transfers 3.00 MB across 17 request(s), with the document itself at 42.3 KB.

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

Third-party weight

medium impact

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

IMAGESwww.wireshark.org/assets/banners/wcatrainingbanner.png
1.08 s
IMAGESwww.wireshark.org/_astro/endace.BHKk8StM_Z26cTv1.webp
917 ms
IMAGESwww.wireshark.org/_astro/recall_ai.BBQukeJA_2hf7X.webp
913 ms
IMAGESwww.wireshark.org/_astro/fmadio.BThAw1rz_Z1fceFL.webp
908 ms
CSSuse.typekit.net/nvp0lhj.css
892 ms
IMAGESwww.wireshark.org/_astro/WCAFrontpage.CpLJgg4K_fh7bF.png
887 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
739 ms
JAVASCRIPTstatic.cloudflareinsights.com/beacon.min.js
720 ms
CSScdn.jsdelivr.net/npm/wf-components/public/styles.css
712 ms
IMAGESwww.wireshark.org/_astro/wca.C_vSXqTJ_Z2pt6cI.webp
679 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://www.wireshark.org/assets/banners/wcatrainingbanner.pngimages2001.08 s199.9 KB
https://www.wireshark.org/_astro/endace.BHKk8StM_Z26cTv1.webpimages200917 ms10.1 KB
https://www.wireshark.org/_astro/recall_ai.BBQukeJA_2hf7X.webpimages200913 ms2.3 KB
https://www.wireshark.org/_astro/fmadio.BThAw1rz_Z1fceFL.webpimages200908 ms10.3 KB
https://use.typekit.net/nvp0lhj.css 3rd partycss200892 ms1.1 KB
https://www.wireshark.org/_astro/WCAFrontpage.CpLJgg4K_fh7bF.pngimages200887 ms2.16 MB
https://www.googletagmanager.com/gtag/js?id=G-YLHRKD6LH6 3rd partyjavascript200739 ms177.4 KB
https://static.cloudflareinsights.com/beacon.min.js 3rd partyjavascript200720 ms10.0 KB
https://cdn.jsdelivr.net/npm/wf-components/public/styles.css 3rd partycss200712 ms7.3 KB
https://www.wireshark.org/_astro/wca.C_vSXqTJ_Z2pt6cI.webpimages200679 ms78.9 KB
https://i.ytimg.com/vi/p0aAt3iB398/maxresdefault.jpg 3rd partyimages200672 ms145.5 KB
https://www.wireshark.org/_astro/profitap.6E4vc7ps_1tN69a.webpimages200660 ms8.3 KB
https://i.ytimg.com/vi_webp/XQvb7bzshcE/maxresdefault.webp 3rd partyimages200656 ms44.1 KB
https://www.wireshark.org/img/hero-background.webpimages200655 ms110.7 KB
https://www.wireshark.org/_astro/bibliography.tsm2vgcx.csscss200655 ms15.2 KB
https://www.wireshark.org/favicon.icoimages200655 ms3.1 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.