Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

klenza.in

Shop Everyday Hygiene Essentials at Best Prices from Klenza – Klenza shop

Page Load Speed

6.7 sec in total

First Response

478 ms

Resources Loaded

5.3 sec

Page Rendered

938 ms

About Website

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.in

Key Findings

We 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.

Performance Metrics

klenza.in performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value7,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 138.6 kB (12%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-79%

Potential reduce by 131.6 kB

  • Original 167.5 kB
  • After minification 163.9 kB
  • After compression 35.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 131.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 191.7 kB
  • After minification 191.7 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. Klenza images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.0 kB

  • Original 661.5 kB
  • After minification 661.4 kB
  • After compression 656.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 2.0 kB

  • Original 173.7 kB
  • After minification 173.7 kB
  • After compression 171.7 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.

Requests Breakdown

Number of requests can be reduced by 46 (72%)

Requests Now

64

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

klenza.in accessibility score

71

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

klenza.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

klenza.in SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: