Tools & Wizards About Us
wattstopper.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

wattstopper.com

Wattstopper Lighting Control Systems

Page Load Speed

5 sec in total

First Response

127 ms

Resources Loaded

3.7 sec

Page Rendered

1.2 sec

wattstopper.com screenshot

About Website

Click here to check amazing Wattstopper content for United States. Otherwise, check out these important facts you probably never knew about wattstopper.com

Wattstopper lighting control products are designed to meet code, ensure ease of installation, and enable the control of light. Learn more.

Visit wattstopper.com

Key Findings

We analyzed Wattstopper.com page load time and found that the first response time was 127 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wattstopper.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,470 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

wattstopper.com

127 ms

wattstopper.com

37 ms

wattstopper

481 ms

awy7nwh.css

30 ms

css

29 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Wattstopper.com, 39% (31 requests) were made to Legrand.us and 37% (29 requests) were made to Cdn2.webdamdb.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cdn2.webdamdb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 625.4 kB (10%)

Content Size

6.1 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wattstopper.com main page is 6.1 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. 50% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 420.1 kB

  • Original 457.6 kB
  • After minification 290.7 kB
  • After compression 37.5 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. This page needs HTML code to be minified as it can gain 166.9 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 420.1 kB or 92% of the original size.

Image Optimization

-4%

Potential reduce by 199.2 kB

  • Original 5.6 MB
  • After minification 5.4 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. Wattstopper images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 6.1 kB

  • Original 41.4 kB
  • After minification 41.4 kB
  • After compression 35.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 6.1 kB or 15% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 8 (12%)

Requests Now

67

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wattstopper. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wattstopper.com

wattstopper.com

127 ms

wattstopper.com

wattstopper.com

37 ms

wattstopper

wattstopper

481 ms

awy7nwh.css

awy7nwh.css

30 ms

css

css

29 ms

common.css

common.css

20 ms

style.css

style.css

46 ms

ps-utid.js

ps-utid.js

135 ms

p.css

p.css

50 ms

DMF36-N82WJ-UH7CT-58HE2-ARD2Z

DMF36-N82WJ-UH7CT-58HE2-ARD2Z

142 ms

us.svg

us.svg

58 ms

1280_YxpgRbb71Q71cRsw.jpg

1280_YxpgRbb71Q71cRsw.jpg

707 ms

seal.min.js

seal.min.js

246 ms

jquery.min.js

jquery.min.js

193 ms

icons.svg

icons.svg

72 ms

ma.svg

ma.svg

43 ms

sa.svg

sa.svg

43 ms

tn.svg

tn.svg

117 ms

br.svg

br.svg

119 ms

ca.svg

ca.svg

116 ms

cl.svg

cl.svg

118 ms

co.svg

co.svg

158 ms

mx.svg

mx.svg

160 ms

pe.svg

pe.svg

229 ms

cn.svg

cn.svg

232 ms

in.svg

in.svg

230 ms

sg.svg

sg.svg

231 ms

ae.svg

ae.svg

234 ms

be.svg

be.svg

233 ms

fr.svg

fr.svg

243 ms

de.svg

de.svg

237 ms

it.svg

it.svg

240 ms

nl.svg

nl.svg

239 ms

pl.svg

pl.svg

238 ms

pt.svg

pt.svg

241 ms

ru.svg

ru.svg

248 ms

es.svg

es.svg

246 ms

au.svg

au.svg

244 ms

logo-legrand.svg

logo-legrand.svg

243 ms

legrand-footer-logo.svg

legrand-footer-logo.svg

249 ms

1280_syLJWYTaC4b61skF.jpg

1280_syLJWYTaC4b61skF.jpg

780 ms

1280_wg82hFbprnt356bo.jpg

1280_wg82hFbprnt356bo.jpg

944 ms

1280_6vNkWj8oRRi09Mf4.jpg

1280_6vNkWj8oRRi09Mf4.jpg

728 ms

1280_EJIA0sWZoTp12pGo.jpg

1280_EJIA0sWZoTp12pGo.jpg

821 ms

1280_YCLM1nj6HMe83QKq.jpg

1280_YCLM1nj6HMe83QKq.jpg

690 ms

1280_6ygFRBLh5Km38M8Z.jpg

1280_6ygFRBLh5Km38M8Z.jpg

1318 ms

1280_6A1Qj10vHr989Mya.jpg

1280_6A1Qj10vHr989Mya.jpg

1204 ms

1280_UWKAA8t9QSu41MrH.jpg

1280_UWKAA8t9QSu41MrH.jpg

1175 ms

1280_gb3aNtJKCz41AYu7.jpg

1280_gb3aNtJKCz41AYu7.jpg

1236 ms

1280_gj7iqBGR3nZ85tLf.jpg

1280_gj7iqBGR3nZ85tLf.jpg

1367 ms

1280_oMs6TjaUM0N12wJF.jpg

1280_oMs6TjaUM0N12wJF.jpg

1514 ms

1280_c6Vwfg1tCWP53ona.jpg

1280_c6Vwfg1tCWP53ona.jpg

1913 ms

1280_kIQVPaX1Xba81gXD.jpg

1280_kIQVPaX1Xba81gXD.jpg

1694 ms

1280_MXcaP7pn2Oa22gBN.jpg

1280_MXcaP7pn2Oa22gBN.jpg

1868 ms

1280_gcX8dAgoKbU11sTI.jpg

1280_gcX8dAgoKbU11sTI.jpg

1936 ms

1280_U9MXdhi0aDc69krh.jpg

1280_U9MXdhi0aDc69krh.jpg

2051 ms

1280_2MBbzi5rJo31UGYI.jpg

1280_2MBbzi5rJo31UGYI.jpg

2003 ms

1280_oS55tiI2Qa01sVA2.png

1280_oS55tiI2Qa01sVA2.png

2314 ms

1280_6odDO5PeajU23AJ8.jpg

1280_6odDO5PeajU23AJ8.jpg

2370 ms

1280_kNEL28o9o5s19coY.png

1280_kNEL28o9o5s19coY.png

2614 ms

1280_g8TJslOoSSh02w5b.png

1280_g8TJslOoSSh02w5b.png

2308 ms

1280_YxwYENiHVp51oo27.jpg

1280_YxwYENiHVp51oo27.jpg

2430 ms

1280_QX6v1VoeR488Yq2K.jpg

1280_QX6v1VoeR488Yq2K.jpg

2404 ms

1280_kDjQQjBwkZ23EHhS.jpg

1280_kDjQQjBwkZ23EHhS.jpg

2686 ms

1280_A8TLh4qKGpt2.jpg

1280_A8TLh4qKGpt2.jpg

2738 ms

1280_66wqszcQPpC9.jpg

1280_66wqszcQPpC9.jpg

2754 ms

1280_UMeBqAZHvc02.jpg

1280_UMeBqAZHvc02.jpg

2880 ms

1280_MENyxKsy8M78.jpg

1280_MENyxKsy8M78.jpg

2843 ms

d

d

36 ms

d

d

182 ms

d

d

64 ms

d

d

54 ms

d

d

84 ms

d

d

72 ms

d

d

151 ms

d

d

180 ms

d

d

180 ms

config.json

config.json

100 ms

core.js

core.js

40 ms

Accessibility Review

wattstopper.com accessibility score

77

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

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Some elements have a [tabindex] value greater than 0

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

wattstopper.com 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

wattstopper.com SEO score

91

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wattstopper.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 Wattstopper.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

wattstopper.com

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