Tools & Wizards About Us
wd40.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wd40.com

WD-40 Lubricants, Degreasers & Rust Removal Products | WD-40

Page Load Speed

1.9 sec in total

First Response

155 ms

Resources Loaded

1.7 sec

Page Rendered

82 ms

wd40.com screenshot

About Website

Welcome to wd40.com homepage info - get ready to check WD 40 best content for United States right away, or after learning these important things about wd40.com

For over 50 years, people have relied on WD-40 to protect metal from rust and corrosion. Explore our lubricants, penetrating oils, cleaners and rust removal products. WD-40 is perfect for big and smal...

Visit wd40.com

Key Findings

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

Performance Metrics

wd40.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value9,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.356

31/100

15%

TTI (Time to Interactive)

Value31.0 s

0/100

10%

Network Requests Diagram

wd40.com

155 ms

www.wd40.com

69 ms

uc.js

71 ms

bootstrap.min.css

60 ms

webpack-runtime-d7f8d46d8115671b1521.js

14 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 31% of them (18 requests) were addressed to the original Wd40.com, 12% (7 requests) were made to Datocms-assets.com and 5% (3 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Datocms-assets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 936.8 kB (22%)

Content Size

4.3 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wd40.com main page is 4.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 647.5 kB

  • Original 797.5 kB
  • After minification 797.5 kB
  • After compression 150.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 647.5 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 58.6 kB

  • Original 2.8 MB
  • After minification 2.7 MB

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. WD 40 images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 230.7 kB

  • Original 686.5 kB
  • After minification 686.4 kB
  • After compression 455.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 230.7 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (55%)

Requests Now

47

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wd40.com

wd40.com

155 ms

www.wd40.com

www.wd40.com

69 ms

uc.js

uc.js

71 ms

bootstrap.min.css

bootstrap.min.css

60 ms

webpack-runtime-d7f8d46d8115671b1521.js

webpack-runtime-d7f8d46d8115671b1521.js

14 ms

commons-02e60d988a08e53abbb3.js

commons-02e60d988a08e53abbb3.js

46 ms

styles-74569603787453ea62d3.js

styles-74569603787453ea62d3.js

37 ms

component---src-templates-index-js-31af86766509e247b928.js

component---src-templates-index-js-31af86766509e247b928.js

48 ms

app-1888636743989b5ad33e.js

app-1888636743989b5ad33e.js

44 ms

ps-widget.js

ps-widget.js

59 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

52 ms

popper.min.js

popper.min.js

239 ms

bootstrap.min.js

bootstrap.min.js

61 ms

wd40.js

wd40.js

39 ms

matomo.js

matomo.js

239 ms

gtm.js

gtm.js

326 ms

logo.svg

logo.svg

162 ms

1681425949-5-pods_master_retouch_png-cutout-1.png

1681425949-5-pods_master_retouch_png-cutout-1.png

465 ms

newSearch.png

newSearch.png

127 ms

homeMobileThumbnail.jpeg

homeMobileThumbnail.jpeg

130 ms

1681425920-screen-shot-2023-04-11-at-12-17-16-pm.png

1681425920-screen-shot-2023-04-11-at-12-17-16-pm.png

564 ms

1692979072-1678732688-gettheinsidescoopdesktop.png

1692979072-1678732688-gettheinsidescoopdesktop.png

663 ms

1692979079-1678732703-gettheinsidescooptablet.png

1692979079-1678732703-gettheinsidescooptablet.png

548 ms

1691523110-group-386.png

1691523110-group-386.png

1252 ms

1691523128-group-387.png

1691523128-group-387.png

547 ms

barlow-all-400-normal-ac4ae75b2bfcdb3fb681f07bd3e89159.woff

barlow-all-400-normal-ac4ae75b2bfcdb3fb681f07bd3e89159.woff

120 ms

app-data.json

app-data.json

54 ms

page-data.json

page-data.json

113 ms

config.js

config.js

719 ms

barlow-condensed-all-500-normal-82cb4e1619a0f238c9892b218af5e285.woff

barlow-condensed-all-500-normal-82cb4e1619a0f238c9892b218af5e285.woff

127 ms

barlow-condensed-all-400-normal-ae2c5b91f5adc4138844d53258ce29a8.woff

barlow-condensed-all-400-normal-ae2c5b91f5adc4138844d53258ce29a8.woff

340 ms

barlow-semi-condensed-all-600-normal-6cc8dc81ba69db31af3f5a13ba901b46.woff

barlow-semi-condensed-all-600-normal-6cc8dc81ba69db31af3f5a13ba901b46.woff

41 ms

fontawesome-webfont-fee66e712a8a08eef5805a46892932ad.woff

fontawesome-webfont-fee66e712a8a08eef5805a46892932ad.woff

47 ms

matomo.php

matomo.php

518 ms

configs.php

configs.php

484 ms

1681425949-5-pods_master_retouch_png-cutout-1.png

1681425949-5-pods_master_retouch_png-cutout-1.png

610 ms

destination

destination

110 ms

iframe_api

iframe_api

152 ms

pixel.js

pixel.js

151 ms

tfa.js

tfa.js

174 ms

amzn.js

amzn.js

155 ms

fbevents.js

fbevents.js

147 ms

ps-utid.js

ps-utid.js

64 ms

tfa.js

tfa.js

243 ms

149 ms

www-widgetapi.js

www-widgetapi.js

24 ms

rp.gif

rp.gif

133 ms

t2_jrneitp9_telemetry

t2_jrneitp9_telemetry

117 ms

bounce

bounce

112 ms

665630150299420

665630150299420

81 ms

json

json

58 ms

vv.20240509-4-RELEASE.js

vv.20240509-4-RELEASE.js

11 ms

30 ms

appnexus

appnexus

33 ms

572891166806252

572891166806252

66 ms

pixel

pixel

29 ms

google

google

4 ms

rubicon

rubicon

3 ms

rum

rum

18 ms

Accessibility Review

wd40.com accessibility score

93

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

Best Practices

wd40.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wd40.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wd40.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wd40.com 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

wd40.com

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