6.7 sec in total
478 ms
5.3 sec
938 ms
Click here to check amazing Klenza content for India. Otherwise, check out these important facts you probably never knew about klenza.in
Shop everyday hygiene essentials like sanitizer, disinfectant spray, and more at best prices from Klenza | Pan-India Shipping | Non-toxic | Free from toxic chemicals ☑️ Expertise in germ protection ☑️...
Visit klenza.inWe analyzed Klenza.in page load time and found that the first response time was 478 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
klenza.in performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value17.2 s
0/100
25%
Value11.4 s
5/100
10%
Value7,140 ms
0/100
30%
Value0.013
100/100
15%
Value24.6 s
0/100
10%
478 ms
58 ms
81 ms
72 ms
168 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Klenza.in, 20% (18 requests) were made to Fonts.gstatic.com and 8% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Dwsl60voagnqc.cloudfront.net.
Page size can be reduced by 138.6 kB (12%)
1.2 MB
1.1 MB
In fact, the total size of Klenza.in 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. Only a small number of websites need less resources to load. Javascripts take 661.5 kB which makes up the majority of the site volume.
Potential reduce by 131.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 131.6 kB or 79% of the original size.
Potential reduce by 0 B
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. Klenza images are well optimized though.
Potential reduce by 5.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.0 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. Klenza.in has all CSS files already compressed.
Number of requests can be reduced by 46 (72%)
64
18
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Klenza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
shop.klenza.in
478 ms
pre_theme.min.css
58 ms
theme.css
81 ms
lazysizes.min.js
72 ms
nt_vendor.min.js
168 ms
preloads.js
160 ms
load_feature-eff2497f10d71bbcd02c4372efd22f3c7d74ed699a57073ccf912bd23cecacf4.js
54 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
167 ms
inbox-chat-loader.js
167 ms
shopify-perf-kit-1.0.0.min.js
166 ms
css
182 ms
wc-review.css
195 ms
wc-product-review.js
226 ms
mobilemenu-v2.js
167 ms
salekit-v2.js
165 ms
satcb.min.js
318 ms
Simplify360Chat.js
935 ms
simplify360Style.css
1709 ms
Klenza.json
162 ms
trekkie.storefront.a8ef5c2c4f1c6e0839c6b8857d0a2edb7d22d961.min.js
109 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
109 ms
shopify-boomerang-1.0.0.min.js
143 ms
klenza-01_360x_233fd07b-ab38-4f15-84c3-3aa137e35004_160x.png
175 ms
klenza-01_360x_233fd07b-ab38-4f15-84c3-3aa137e35004_140x.png
287 ms
pxiEyp8kv8JHgFVrJJfedA.woff
98 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
128 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
144 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
146 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
149 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
146 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
148 ms
pxiGyp8kv8JHgFVrJJLucHtG.woff
58 ms
pxiDyp8kv8JHgFVrJJLmg1hVF9eI.woff
56 ms
pxiDyp8kv8JHgFVrJJLm21lVF9eI.woff
58 ms
pxiDyp8kv8JHgFVrJJLmr19VF9eI.woff
58 ms
pxiDyp8kv8JHgFVrJJLmy15VF9eI.woff
60 ms
pxiDyp8kv8JHgFVrJJLm111VF9eI.woff
60 ms
pxiDyp8kv8JHgFVrJJLm81xVF9eI.woff
58 ms
shop.klenza.in
296 ms
css
35 ms
bc5b4e8fb1c3c4d465f8323a3.js
573 ms
smile-shopify.js
342 ms
dbe122fe80a9d4b6ce7ba46c21891898.js
341 ms
globo.menu.init.js
72 ms
wc-product-review.js
71 ms
glass_cleaner_web_1728x.jpg
709 ms
style.min.css
289 ms
css
262 ms
sett_cl.css
282 ms
line-awesome.min.css
268 ms
nt_settings.js
210 ms
SBP7206_360x.jpg
276 ms
fakalles.woff
214 ms
Pe-icon-7-stroke.woff
89 ms
kmKhZrc3Hgbbcjq75U4uslyuy4kn0qNcWxEQCg.woff
5 ms
kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxU.woff
87 ms
la-solid-900.woff
1067 ms
la-regular-400.woff
315 ms
nt_theme.min.js
155 ms
Pe-icon-7-stroke.ttf
454 ms
iframe_api
69 ms
cat.min.js
50 ms
swatch.min.js
34 ms
fakalles.ttf
253 ms
www-widgetapi.js
32 ms
la-regular-400.ttf
666 ms
produc.min.js
112 ms
interactable.min.js
111 ms
shopify_common-33bb9d312118840468a53f36b59c62c1e8f2b7d1a0a77250db9e300441827470.js
97 ms
XdoBo4iiiHg
105 ms
www-player.css
49 ms
www-embed-player.js
141 ms
base.js
182 ms
nt_instagram.min.js
134 ms
customerclnt.min.js
135 ms
module.min.js
135 ms
fakalles.svg
491 ms
ad_status.js
236 ms
Pe-icon-7-stroke.svg
498 ms
IJhwbK6X-i0aSQsKp1U3hsnnNknGAHH8uGjszq9fxxM.js
210 ms
embed.js
59 ms
SBP7171_360x.jpg
339 ms
id
46 ms
search
177 ms
la-solid-900.ttf
940 ms
la-regular-400.svg
314 ms
KFOmCnqEu92Fr1Mu4mxM.woff
16 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
17 ms
Create
125 ms
GenerateIT
13 ms
search
103 ms
klenza.in 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
klenza.in 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
Missing source maps for large first-party JavaScript
klenza.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Klenza.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Klenza.in 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.
klenza.in
Open Graph data is detected on the main page of Klenza. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: