Tools & Wizards About Us
madwater.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

madwater.com

Mad Water - Waterproof Duffels, Bags, & Backpacks

Page Load Speed

776 ms in total

First Response

106 ms

Resources Loaded

514 ms

Page Rendered

156 ms

madwater.com screenshot

About Website

Click here to check amazing Mad Water content. Otherwise, check out these important facts you probably never knew about madwater.com

Mad Water offers waterproof duffel bags, waterproof backpacks, waterproof dry bags, and are makers of the submersible Waterproof USA Duffel.

Visit madwater.com

Key Findings

We analyzed Madwater.com page load time and found that the first response time was 106 ms and then it took 670 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

madwater.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

www.madwater.com

106 ms

css-base.css

27 ms

css-element.css

25 ms

css-contents.css

24 ms

css-edits.css

25 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 27% of them (8 requests) were addressed to the original Madwater.com, 47% (14 requests) were made to Ep.yimg.com and 7% (2 requests) were made to Lib.store.yahoo.net. The less responsive or slowest element that took the longest time to load (117 ms) relates to the external source S.yimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.6 kB (26%)

Content Size

352.5 kB

After Optimization

259.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Madwater.com main page is 352.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 214.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 7.0 kB

  • Original 10.0 kB
  • After minification 10.0 kB
  • After compression 3.0 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 7.0 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 15.2 kB

  • Original 214.3 kB
  • After minification 199.1 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. Mad Water images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 55.8 kB

  • Original 109.5 kB
  • After minification 102.6 kB
  • After compression 53.7 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 55.8 kB or 51% of the original size.

CSS Optimization

-79%

Potential reduce by 14.7 kB

  • Original 18.7 kB
  • After minification 14.2 kB
  • After compression 4.0 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. Madwater.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.madwater.com

www.madwater.com

106 ms

css-base.css

css-base.css

27 ms

css-element.css

css-element.css

25 ms

css-contents.css

css-contents.css

24 ms

css-edits.css

css-edits.css

25 ms

jquery.min.js

jquery.min.js

42 ms

loader_536a99d.js

loader_536a99d.js

117 ms

css-base.css

css-base.css

12 ms

yhst-99929751614010_2230_2964

yhst-99929751614010_2230_2964

19 ms

M62100-fishingsmall.jpg

M62100-fishingsmall.jpg

13 ms

index-5.jpg

index-5.jpg

102 ms

m63100-48.jpg

m63100-48.jpg

39 ms

yhst-99929751614010_2230_2270781

yhst-99929751614010_2230_2270781

29 ms

yhst-99929751614010_2230_2252355

yhst-99929751614010_2230_2252355

28 ms

rgbutton.gif

rgbutton.gif

12 ms

M62100-fishingsmall.jpg

M62100-fishingsmall.jpg

88 ms

rgbutton.gif

rgbutton.gif

33 ms

css-base.css

css-base.css

33 ms

yhst-99929751614010_2230_532062

yhst-99929751614010_2230_532062

15 ms

yhst-99929751614010_2230_586285

yhst-99929751614010_2230_586285

11 ms

yhst-99929751614010_2230_586871

yhst-99929751614010_2230_586871

9 ms

yhst-99929751614010_2230_526400

yhst-99929751614010_2230_526400

11 ms

yhst-99929751614010_2230_527414

yhst-99929751614010_2230_527414

12 ms

yhst-99929751614010_2230_586715

yhst-99929751614010_2230_586715

13 ms

yhst-99929751614010_2230_531624

yhst-99929751614010_2230_531624

17 ms

css-element.css

css-element.css

14 ms

1458507350830___fc_yhst-99929751614010.js

1458507350830___fc_yhst-99929751614010.js

22 ms

combo

combo

10 ms

combo

combo

24 ms

e00f21ac258e5890712b788befcb8c21

e00f21ac258e5890712b788befcb8c21

36 ms

Accessibility Review

madwater.com accessibility score

80

Accessibility Issues

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

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

Form elements do not have associated labels

Best Practices

madwater.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

madwater.com SEO score

98

Search Engine Optimization Advices

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Madwater.com 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 Madwater.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

madwater.com

Open Graph description is not detected on the main page of Mad Water. 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: