Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

stanleyearth.com

Our Impact: Planet - Environmental Sustainability | Stanley Black & Decker

Page Load Speed

77.5 sec in total

First Response

8 sec

Resources Loaded

68.3 sec

Page Rendered

1.1 sec

About Website

Welcome to stanleyearth.com homepage info - get ready to check Stanley Earth best content right away, or after learning these important things about stanleyearth.com

Learn about our initiative to go from being carbon neutral to being climate positive by the year 2030 to meet UN Sustainable Development Goals. Learn more.

Visit stanleyearth.com

Key Findings

We analyzed Stanleyearth.com page load time and found that the first response time was 8 sec and then it took 69.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 41 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

stanleyearth.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.289

41/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

planet

8031 ms

d0a068fbbc9f9af642a80633350be77417e0012b2aa65

30 ms

css_QobfCJngxRkQ4dzxj5fI6th_tr0OVHknEsjLIa992J8.css

10126 ms

css_uDteo6YqLe7rPvCgRxMvR0wCog-6jADUveNbpA6imPs.css

10144 ms

jquery_3.7.1_jquery.min.js

8061 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stanleyearth.com, 4% (3 requests) were made to Use.typekit.net and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Stanleyblackanddecker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.9 kB (63%)

Content Size

745.7 kB

After Optimization

273.8 kB

In fact, the total size of Stanleyearth.com main page is 745.7 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. 35% of websites need less resources to load. Javascripts take 654.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 74.7 kB

  • Original 91.3 kB
  • After minification 91.2 kB
  • After compression 16.6 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 74.7 kB or 82% of the original size.

JavaScript Optimization

-61%

Potential reduce by 397.2 kB

  • Original 654.4 kB
  • After minification 654.4 kB
  • After compression 257.2 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 397.2 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (73%)

Requests Now

22

After Optimization

6

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

Accessibility Review

stanleyearth.com accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s are not contained by their required parent element

Best Practices

stanleyearth.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stanleyearth.com SEO score

86

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

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

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 Stanleyearth.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 Stanleyearth.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: