8.7 sec in total
2.2 sec
6.2 sec
276 ms
Visit leannclean.com now to see the best up-to-date Leannclean content and also check out these interesting facts you probably never knew about leannclean.com
Suffering from Constipation, Hemorrhoids, IBS, Diverticulitis, Acne, Overall fatigue? You have found the natural/safe remedy:-Lean N Clean®
Visit leannclean.comWe analyzed Leannclean.com page load time and found that the first response time was 2.2 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
leannclean.com performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value9.1 s
1/100
25%
Value14.6 s
1/100
10%
Value300 ms
79/100
30%
Value0.166
71/100
15%
Value13.4 s
11/100
10%
2219 ms
198 ms
143 ms
193 ms
199 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 86% of them (95 requests) were addressed to the original Leannclean.com, 11% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Leannclean.com.
Page size can be reduced by 423.4 kB (36%)
1.2 MB
743.9 kB
In fact, the total size of Leannclean.com main page is 1.2 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. Javascripts take 531.1 kB which makes up the majority of the site volume.
Potential reduce by 158.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. 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 158.8 kB or 80% of the original size.
Potential reduce by 39.4 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. Obviously, Leannclean needs image optimization as it can save up to 39.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 103.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 103.3 kB or 19% of the original size.
Potential reduce by 121.9 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. Leannclean.com needs all CSS files to be minified and compressed as it can save up to 121.9 kB or 50% of the original size.
Number of requests can be reduced by 88 (92%)
96
8
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leannclean. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
www.leannclean.com
2219 ms
main.min.css
198 ms
mediaelementplayer-legacy.min.css
143 ms
wp-mediaelement.min.css
193 ms
common-style.css
199 ms
style-index.css
210 ms
blocks.style.build.css
281 ms
woocommerce-layout-grid.min.css
219 ms
woocommerce-grid.min.css
284 ms
header-footer-elementor.css
258 ms
elementor-icons.min.css
282 ms
frontend-lite.min.css
362 ms
swiper.min.css
293 ms
post-5.css
324 ms
global.css
356 ms
post-2.css
349 ms
frontend.css
358 ms
post-633.css
372 ms
post-1621.css
394 ms
font-awesome.min.css
421 ms
simple-line-icons.css
430 ms
htflexboxgrid.css
429 ms
slick.css
438 ms
woolentor-widgets.css
536 ms
sassy-social-share-public.css
458 ms
css
30 ms
fontawesome.min.css
496 ms
solid.min.css
500 ms
regular.min.css
505 ms
jquery.min.js
577 ms
jquery-migrate.min.js
525 ms
jquery.blockUI.min.js
568 ms
add-to-cart.min.js
571 ms
js.cookie.min.js
661 ms
woocommerce.min.js
661 ms
s-202406.js
17 ms
wc-blocks.css
612 ms
submit.js
746 ms
e-202406.js
1 ms
frontend.min.js
612 ms
script.js
540 ms
sourcebuster.min.js
548 ms
order-attribution.min.js
479 ms
wp-polyfill-inert.min.js
529 ms
regenerator-runtime.min.js
528 ms
wp-polyfill.min.js
545 ms
react.min.js
481 ms
hooks.min.js
483 ms
deprecated.min.js
536 ms
dom.min.js
535 ms
react-dom.min.js
621 ms
escape-html.min.js
498 ms
element.min.js
486 ms
is-shallow-equal.min.js
511 ms
i18n.min.js
512 ms
keycodes.min.js
515 ms
priority-queue.min.js
512 ms
compose.min.js
527 ms
private-apis.min.js
512 ms
redux-routine.min.js
513 ms
data.min.js
521 ms
lodash.min.js
530 ms
wc-blocks-registry.js
522 ms
url.min.js
489 ms
api-fetch.min.js
498 ms
wc-settings.js
512 ms
data-controls.min.js
496 ms
html-entities.min.js
497 ms
notices.min.js
478 ms
wc-blocks-middleware.js
493 ms
wc-blocks-data.js
405 ms
dom-ready.min.js
431 ms
a11y.min.js
432 ms
primitives.min.js
460 ms
warning.min.js
446 ms
blocks-components.js
542 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
17 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
26 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
45 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
56 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
57 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
58 ms
blocks-checkout.js
464 ms
KFOjCnqEu92Fr1Mu51TzBic6CsLYl4BO.woff
56 ms
font
109 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsLYl4BO.woff
55 ms
KFOkCnqEu92Fr1Mu51xIIzQXKMny.woff
58 ms
KFOjCnqEu92Fr1Mu51TjASc6CsLYl4BO.woff
59 ms
KFOiCnqEu92Fr1Mu51QrEzAdKevwnYg.woff
171 ms
order-attribution-blocks.min.js
488 ms
slick.min.js
447 ms
accordion.min.js
444 ms
sassy-social-share-public.js
501 ms
frontend.js
458 ms
webpack.runtime.min.js
484 ms
frontend-modules.min.js
432 ms
waypoints.min.js
425 ms
core.min.js
460 ms
frontend.min.js
467 ms
underscore.min.js
484 ms
wp-util.min.js
450 ms
frontend.min.js
443 ms
eicons.woff
580 ms
Lean-N-Clean_logo-removebg.png
467 ms
Images-transparent-shopping-removebg-preview-1.png
494 ms
Leannclean_product_image-removebg-removebg-small.png
460 ms
Leannclean_product_image-showing-powder.png
451 ms
Diana-in-white-jacket.png
452 ms
Image-of-Lab-technician.png
469 ms
woocommerce-smallscreen-grid.min.css
69 ms
leannclean.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
leannclean.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
leannclean.com SEO score
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 Leannclean.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 Leannclean.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.
leannclean.com
Open Graph data is detected on the main page of Leannclean. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: