3 sec in total
59 ms
2.7 sec
244 ms
Welcome to clx.com homepage info - get ready to check Clx best content right away, or after learning these important things about clx.com
The Clorox Company champions people to be well and thrive every single day. Get company news, learn what’s in our products and search job opportunities.
Visit clx.comWe analyzed Clx.com page load time and found that the first response time was 59 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
clx.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value12.1 s
0/100
25%
Value5.0 s
63/100
10%
Value1,120 ms
23/100
30%
Value1.141
1/100
15%
Value9.7 s
28/100
10%
59 ms
122 ms
226 ms
94 ms
90 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Clx.com, 57% (70 requests) were made to Thecloroxcompany.com and 14% (17 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Thecloroxcompany.com.
Page size can be reduced by 939.0 kB (30%)
3.1 MB
2.2 MB
In fact, the total size of Clx.com main page is 3.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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 124.9 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 124.9 kB or 76% of the original size.
Potential reduce by 140.3 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. Clx images are well optimized though.
Potential reduce by 603.6 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 603.6 kB or 66% of the original size.
Potential reduce by 70.2 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. Clx.com needs all CSS files to be minified and compressed as it can save up to 70.2 kB or 82% of the original size.
Number of requests can be reduced by 43 (36%)
119
76
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
clx.com
59 ms
www.thecloroxcompany.com
122 ms
www.thecloroxcompany.com
226 ms
common.css
94 ms
screen.css
90 ms
style-home.css
115 ms
jquery.min.js
88 ms
common.js
107 ms
siteCommon.js
167 ms
activeClass.js
140 ms
jquery.tools.min.js
326 ms
jquery.jcarousel.min.js
240 ms
liteaccordion.jquery.js
257 ms
home.js
217 ms
satelliteLib-e1a96af74edf26406b64b1c5cb0abedb7b5a6c6c.js
190 ms
irxml.aspx
84 ms
irxml.functions.js
72 ms
addthis_widget.js
49 ms
style-defaults.css
186 ms
style-pages.css
230 ms
nav.css
258 ms
modern2015.css
262 ms
iMAWebCookie.js
115 ms
analytics.js
21 ms
print.css
39 ms
collect
31 ms
collect
61 ms
bg_main.png
292 ms
16x16.png
139 ms
bg_utilityNav.gif
215 ms
nav-linkedin-icon.png
216 ms
nav-twitter-icon.png
215 ms
nav-glassdoor-icon.png
214 ms
logo.png
267 ms
hero_slide-un-global-compact.jpg
472 ms
hero_slide1.png
420 ms
public-health.jpg
576 ms
hero_slide3.jpg
494 ms
hero_slide4.jpg
501 ms
hero_slide5.jpg
592 ms
hero_slide6.jpg
804 ms
annual_report.jpg
642 ms
blog.png
644 ms
blog-red-cross.png
747 ms
brands_clx.png
709 ms
brands_fsh.png
722 ms
brands_gw.png
795 ms
brands_bb.png
775 ms
brands_gld.png
842 ms
brands_kin.png
853 ms
brands_hvr.png
876 ms
brands_tlx.png
907 ms
brands_sa.png
946 ms
brands_lp.png
953 ms
brands_poett.png
973 ms
brands_soyvay.png
982 ms
brands_ps.png
1005 ms
brands_oyudin.png
1038 ms
brands_kcm.png
1074 ms
brands_sos.png
1082 ms
brands_ec.png
1123 ms
brands_409.png
1112 ms
brands_chux.png
1133 ms
brands_brt.png
1168 ms
widgets.js
156 ms
tag.js
217 ms
300lo.json
73 ms
sh.8e5f85691f9aaa082472a194.html
44 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
3 ms
syndication
129 ms
429326364127162368
166 ms
brands_mistolin.png
999 ms
brands_chc.png
1008 ms
brands_ppd.png
1038 ms
layers.e5ea973510bf60b3db41.js
8 ms
icon_share.gif
1021 ms
ftr-linkedin-pos.png
976 ms
ftr-twitter-pos.png
1001 ms
icon1.png
31 ms
-_bZUG1-.jpg
29 ms
1f41d.png
195 ms
1f484.png
193 ms
1f338.png
192 ms
1f3b6.png
194 ms
1f340.png
190 ms
1f308.png
208 ms
1f423.png
212 ms
1f430.png
226 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
7 ms
ftr-instagram-pos.png
903 ms
RExpE1C4_normal.jpg
13 ms
aGdmCcyc_normal.jpg
54 ms
Yr_JmccN_normal.png
55 ms
010_normal.jpg
65 ms
RmtgY0Yn_normal.jpg
64 ms
-98ULFCW_normal.jpeg
62 ms
O1ZR-SDt_normal.jpeg
63 ms
Cd3KpseUAAAFzRd.jpg:small
62 ms
Cd2MPZOVIAEUDMP.jpg:small
61 ms
CdSCHNMUMAAduKR.jpg:small
66 ms
Cd05RE2VIAAKr00.jpg:small
64 ms
Cd1UGlkXIAADDKH.jpg:small
63 ms
CdxnpgTUIAApaj9.jpg:small
66 ms
Cdxf9cXUEAA0KJ6.jpg:small
64 ms
CdxVfMfUEAECE6L.jpg:small
62 ms
Cdweh8BWwAAiiA6.jpg:small
66 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
176 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
195 ms
logo_footer.png
860 ms
icon_magnifying_lens.gif
861 ms
sprite.png
861 ms
sprite.png
810 ms
cent_takeover.jpg
1019 ms
sprite_pointers.png
785 ms
hero_slide_blank.png
792 ms
bg_home_promo_full.png
754 ms
btn_carousel_arrows.gif
748 ms
bg_diamond_outlined.png
748 ms
jot.html
2 ms
nr-885.min.js
115 ms
90a95d8474
103 ms
clx.com accessibility score
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
Buttons do not have an accessible name
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
Heading elements are not in a sequentially-descending order
clx.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
clx.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Clx.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 Clx.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.
clx.com
Open Graph description is not detected on the main page of Clx. 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: