Tools & Wizards About Us
wireshark.org screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

wireshark.org

Wireshark · Go Deep

Page Load Speed

2.3 sec in total

First Response

169 ms

Resources Loaded

1.7 sec

Page Rendered

490 ms

wireshark.org screenshot

About Website

Visit wireshark.org now to see the best up-to-date Wireshark content for United States and also check out these interesting facts you probably never knew about wireshark.org

Visit wireshark.org

Key Findings

We analyzed Wireshark.org page load time and found that the first response time was 169 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wireshark.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value6,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

wireshark.org

169 ms

www.wireshark.org

503 ms

opnet_browsermetrix.c.js

66 ms

switcher.min.css

379 ms

css

79 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 59% of them (30 requests) were addressed to the original Wireshark.org, 22% (11 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (503 ms) belongs to the original domain Wireshark.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (63%)

Content Size

1.9 MB

After Optimization

713.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wireshark.org main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. CSS take 959.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 76.4 kB

  • Original 108.5 kB
  • After minification 108.5 kB
  • After compression 32.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 76.4 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 116 B

  • Original 264.8 kB
  • After minification 264.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Wireshark images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 306.4 kB

  • Original 587.7 kB
  • After minification 582.1 kB
  • After compression 281.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 306.4 kB or 52% of the original size.

CSS Optimization

-86%

Potential reduce by 824.6 kB

  • Original 959.5 kB
  • After minification 957.9 kB
  • After compression 134.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Wireshark.org needs all CSS files to be minified and compressed as it can save up to 824.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (58%)

Requests Now

36

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wireshark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wireshark.org

wireshark.org

169 ms

www.wireshark.org

www.wireshark.org

503 ms

opnet_browsermetrix.c.js

opnet_browsermetrix.c.js

66 ms

switcher.min.css

switcher.min.css

379 ms

css

css

79 ms

bootstrap.min.css.pagespeed.ce.-D0KGMMjlG.css

bootstrap.min.css.pagespeed.ce.-D0KGMMjlG.css

37 ms

theme.min.css.pagespeed.ce.A8duM8JVi5.css

theme.min.css.pagespeed.ce.A8duM8JVi5.css

48 ms

color-defaults.min.css.pagespeed.ce.aZ4ZaDxZFL.css

color-defaults.min.css.pagespeed.ce.aZ4ZaDxZFL.css

74 ms

swatch-white.min.css.pagespeed.ce.Rzbe0PB0SG.css

swatch-white.min.css.pagespeed.ce.Rzbe0PB0SG.css

59 ms

custom.css.pagespeed.ce.rss-4-ouUw.css

custom.css.pagespeed.ce.rss-4-ouUw.css

55 ms

swatch-blue.min.css.pagespeed.ce.uKDZCTHDLS.css

swatch-blue.min.css.pagespeed.ce.uKDZCTHDLS.css

60 ms

swatch-gray.min.css.pagespeed.ce.yCW6e4nhdg.css

swatch-gray.min.css.pagespeed.ce.yCW6e4nhdg.css

74 ms

swatch-black.min.css.pagespeed.ce.HrDJ5EYg_A.css

swatch-black.min.css.pagespeed.ce.HrDJ5EYg_A.css

62 ms

swatch-white-black.min.css.pagespeed.ce.8-xKJVHt7U.css

swatch-white-black.min.css.pagespeed.ce.8-xKJVHt7U.css

66 ms

swatch-white-green.min.css.pagespeed.ce.tXsHrUWR7M.css

swatch-white-green.min.css.pagespeed.ce.tXsHrUWR7M.css

77 ms

swatch-white-red.min.css.pagespeed.ce.bb78CD_H4M.css

swatch-white-red.min.css.pagespeed.ce.bb78CD_H4M.css

78 ms

jquery.min.js

jquery.min.js

81 ms

mirrors.js

mirrors.js

357 ms

fill_dl.js.pagespeed.ce.JG5F7doie5.js

fill_dl.js.pagespeed.ce.JG5F7doie5.js

24 ms

packages.min.js

packages.min.js

23 ms

theme.min.js.pagespeed.ce.XsPRzAEo1l.js

theme.min.js.pagespeed.ce.XsPRzAEo1l.js

16 ms

home-intro.jpg

home-intro.jpg

59 ms

grid-70.png

grid-70.png

58 ms

grid-10.png

grid-10.png

62 ms

xanalyzer.png.pagespeed.ic.jwNumwrOZ4.jpg

xanalyzer.png.pagespeed.ic.jwNumwrOZ4.jpg

59 ms

airpcap.png.pagespeed.ce.s7OWKZUSEH.png

airpcap.png.pagespeed.ce.s7OWKZUSEH.png

59 ms

grid-20.png

grid-20.png

60 ms

xvideo_hansang_hands_on.jpg.pagespeed.ic.mlb4SWH8eB.jpg

xvideo_hansang_hands_on.jpg.pagespeed.ic.mlb4SWH8eB.jpg

60 ms

xsflogo.png.pagespeed.ic.bA_F9P-nfS.png

xsflogo.png.pagespeed.ic.bA_F9P-nfS.png

61 ms

troubleshooting.png.pagespeed.ce.dgBkgGj19G.png

troubleshooting.png.pagespeed.ce.dgBkgGj19G.png

60 ms

background1.jpg

background1.jpg

27 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

215 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

238 ms

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

258 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

273 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

273 ms

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

273 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

21 ms

fpTVHK8qsXbIeTHTrnQH6EfrksRSinjQUrHtm_nW72g.ttf

fpTVHK8qsXbIeTHTrnQH6EfrksRSinjQUrHtm_nW72g.ttf

273 ms

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

273 ms

fpTVHK8qsXbIeTHTrnQH6Iue0YgdIF4L_q7PS4yTQOQ.ttf

fpTVHK8qsXbIeTHTrnQH6Iue0YgdIF4L_q7PS4yTQOQ.ttf

273 ms

rLfYuO6pdVA

rLfYuO6pdVA

66 ms

ga.js

ga.js

42 ms

beacon.gif

beacon.gif

344 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

54 ms

www-embed-player.js

www-embed-player.js

67 ms

__utm.gif

__utm.gif

48 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

51 ms

ad_status.js

ad_status.js

51 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

36 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

37 ms

Accessibility Review

wireshark.org accessibility score

66

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wireshark.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wireshark.org SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wireshark.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wireshark.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

wireshark.org

Open Graph description is not detected on the main page of Wireshark. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: