Tools & Wizards About Us
zenex.in screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

zenex.in

zenex.in -

Page Load Speed

3.1 sec in total

First Response

429 ms

Resources Loaded

2.6 sec

Page Rendered

67 ms

zenex.in screenshot

About Website

Visit zenex.in now to see the best up-to-date Zenex content and also check out these interesting facts you probably never knew about zenex.in

Visit zenex.in

Key Findings

We analyzed Zenex.in page load time and found that the first response time was 429 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

zenex.in performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.344

32/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

zenex.in

429 ms

zenex.in

1064 ms

main.min.css

218 ms

style.min.css

482 ms

woocommerce-layout-grid.min.css

555 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that all of those requests were addressed to Zenex.in and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Zenex.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.7 kB (46%)

Content Size

212.4 kB

After Optimization

114.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Zenex.in main page is 212.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 118.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 97.7 kB

  • Original 118.5 kB
  • After minification 117.4 kB
  • After compression 20.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 97.7 kB or 82% of the original size.

JavaScript Optimization

-0%

Potential reduce by 32 B

  • Original 51.9 kB
  • After minification 51.9 kB
  • After compression 51.9 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

-0%

Potential reduce by 6 B

  • Original 42.0 kB
  • After minification 42.0 kB
  • After compression 42.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. Zenex.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (86%)

Requests Now

14

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zenex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

zenex.in

zenex.in

429 ms

zenex.in

zenex.in

1064 ms

main.min.css

main.min.css

218 ms

style.min.css

style.min.css

482 ms

woocommerce-layout-grid.min.css

woocommerce-layout-grid.min.css

555 ms

woocommerce-grid.min.css

woocommerce-grid.min.css

778 ms

jquery.min.js

jquery.min.js

810 ms

jquery-migrate.min.js

jquery-migrate.min.js

629 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

689 ms

add-to-cart.min.js

add-to-cart.min.js

701 ms

js.cookie.min.js

js.cookie.min.js

738 ms

woocommerce.min.js

woocommerce.min.js

859 ms

frontend.min.js

frontend.min.js

896 ms

sourcebuster.min.js

sourcebuster.min.js

915 ms

order-attribution.min.js

order-attribution.min.js

922 ms

woocommerce-smallscreen-grid.min.css

woocommerce-smallscreen-grid.min.css

209 ms

Accessibility Review

zenex.in accessibility score

100

Accessibility Issues

Best Practices

zenex.in best practices score

92

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

SEO Factors

zenex.in SEO score

92

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zenex.in 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 Zenex.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

zenex.in

Open Graph description is not detected on the main page of Zenex. 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: