2.3 sec in total
100 ms
2 sec
246 ms
Welcome to windex.com homepage info - get ready to check Windex best content for United States right away, or after learning these important things about windex.com
Get a streak-free shine all throughout your home, inside and out, with Windex® Glass Cleaner. Find an easy cleaning solution for practically every surface from Windex
Visit windex.comWe analyzed Windex.com page load time and found that the first response time was 100 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.
windex.com performance score
name
value
score
weighting
Value14.2 s
0/100
10%
Value19.3 s
0/100
25%
Value14.2 s
1/100
10%
Value0 ms
100/100
30%
Value0.004
100/100
15%
Value14.4 s
9/100
10%
100 ms
175 ms
24 ms
260 ms
70 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 48% of them (66 requests) were addressed to the original Windex.com, 18% (24 requests) were made to Az807109.vo.msecnd.net and 8% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (510 ms) relates to the external source Az807109.vo.msecnd.net.
Page size can be reduced by 530.6 kB (35%)
1.5 MB
993.7 kB
In fact, the total size of Windex.com main page is 1.5 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. 65% of websites need less resources to load. Images take 894.8 kB which makes up the majority of the site volume.
Potential reduce by 46.8 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 6.6 kB, which is 11% 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 46.8 kB or 76% of the original size.
Potential reduce by 78.0 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. Windex images are well optimized though.
Potential reduce by 307.5 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 307.5 kB or 68% of the original size.
Potential reduce by 98.3 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. Windex.com needs all CSS files to be minified and compressed as it can save up to 98.3 kB or 82% of the original size.
Number of requests can be reduced by 46 (50%)
92
46
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Windex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
windex.com
100 ms
www.windex.com
175 ms
default.aspx
24 ms
default.aspx
260 ms
satelliteLib-b56cdb5169f3fd30cc5b17aea2d63862893f7254.js
70 ms
footer.min.css
134 ms
master.css
45 ms
Local.css
46 ms
Footer.css
465 ms
jquery-1.11.0.min.js
7 ms
global.js
46 ms
s_code.js
47 ms
omniture_methods.js
48 ms
all.js
161 ms
underscore.js
51 ms
jquery.plugins.js
62 ms
plusone.js
74 ms
WebResource.axd
43 ms
blank.js
43 ms
master.css
41 ms
local.css
34 ms
global.js
48 ms
s_code.js
89 ms
omniture_methods.js
47 ms
underscore.js
60 ms
jquery.plugins.js
133 ms
webresource.axd
43 ms
adscout.php
448 ms
site-gradient-bg.gif
55 ms
drano.png
268 ms
glade.png
303 ms
kiwi.png
351 ms
off.png
402 ms
raid.png
398 ms
scj_signature.png
349 ms
rah.png
443 ms
ziploc.png
510 ms
logo_scj_md.png
510 ms
scj_logo.png
50 ms
windex-logo.png
56 ms
icon_facebook.png
55 ms
icon-YouTube.png
54 ms
tumblr_logo_white_blue_20.png
54 ms
TU_1_1_Marquee_CO.jpg
59 ms
learn-more-btnblue.jpg
59 ms
mbfgw_windex.com[1].jpg
257 ms
cta_bar[3].jpg
114 ms
HOMPAGEMARQUEE_Glass_Cleaner.png
118 ms
Origina_Action.gif
96 ms
cb=gapi.loaded_0
37 ms
95 ms
site-gradient-bg.gif
74 ms
scj_logo.png
72 ms
icon-youtube.png
95 ms
windex-logo.png
97 ms
tumblr_logo_white_blue_20.png
93 ms
icon_facebook.png
93 ms
tu_1_1_marquee_co.jpg
218 ms
learn-more-btnblue.jpg
197 ms
xd_arbiter.php
227 ms
xd_arbiter.php
369 ms
origina_action.gif
154 ms
hompagemarquee_glass_cleaner.png
331 ms
gradient.png
37 ms
header_bg.jpg
141 ms
tab-left-8.png
146 ms
rcb-blue-bottom.gif
148 ms
rcb-blue-top.gif
148 ms
moneybackG-tout.jpg
149 ms
arrow-right-29404d.gif
152 ms
windex-facebook.gif
154 ms
new_scents-tout.jpg
154 ms
GlassNMore-tout.jpg
154 ms
tag.js
107 ms
h1.js
109 ms
player_api
105 ms
cb=gapi.loaded_1
59 ms
cb=gapi.loaded_2
70 ms
fastbutton
146 ms
subscribe_embed
135 ms
Homepage_Marquee_dot_hover.jpg
53 ms
Homepage_Marquee_dot.jpg
50 ms
header_bg.jpg
136 ms
drano.png
78 ms
tab-left-8.png
72 ms
rcb-blue-bottom.gif
76 ms
rcb-blue-top.gif
75 ms
moneybackg-tout.jpg
125 ms
arrow-right-29404d.gif
115 ms
windex-facebook.gif
122 ms
new_scents-tout.jpg
125 ms
glassnmore-tout.jpg
158 ms
icon1.png
15 ms
3091.js
20 ms
novecento-ultrabold-webfont.woff
152 ms
glade.png
100 ms
www-widgetapi.js
104 ms
ric-info.png
32 ms
ric-close.png
34 ms
like.php
90 ms
homepage_marquee_dot.jpg
119 ms
homepage_marquee_dot_hover.jpg
124 ms
postmessageRelay
142 ms
kiwi.png
81 ms
scj_signature.png
158 ms
pledge.png
153 ms
www-subscribe-embed-vflWJjAep.css
70 ms
www-subscribe-embed.js
114 ms
cb=gapi.loaded_0
76 ms
cb=gapi.loaded_1
76 ms
qeKvIRsJabD.js
395 ms
raid.png
170 ms
LVx-xkvaJ0b.png
424 ms
off.png
160 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
113 ms
www-hitchhiker-vfluKv9vH.png
75 ms
rah.png
161 ms
3193398744-postmessagerelay.js
96 ms
rpc:shindig_random.js
94 ms
cb=gapi.loaded_0
34 ms
windex.png
109 ms
shout.png
108 ms
scrubbing_bubbles.png
109 ms
ziploc.png
90 ms
logo_scj_md.png
116 ms
cb=gapi.loaded_0
5 ms
cb=gapi.loaded_3
15 ms
s7342772817239
110 ms
border_3.gif
16 ms
subscribe_embed
64 ms
spacer.gif
12 ms
border_3.gif
10 ms
bubbleSprite_3.png
11 ms
bubbleDropR_3.png
11 ms
bubbleDropB_3.png
12 ms
www-subscribe-embed-card-vflqARhQ4.css
11 ms
www-subscribe-embed-card.js
13 ms
windex.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
windex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
windex.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Windex.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 Windex.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.
windex.com
Open Graph data is detected on the main page of Windex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: