Tools & Wizards About Us
horex.in screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

horex.in

Buy 100% Real Leather Shoes Online For Men & Women - Horex®

Page Load Speed

7.4 sec in total

First Response

608 ms

Resources Loaded

6.2 sec

Page Rendered

570 ms

horex.in screenshot

About Website

Welcome to horex.in homepage info - get ready to check Horex best content right away, or after learning these important things about horex.in

Horex brand provides 100% genuine leather shoes online. Formal Shoes For Men, Leather Boots, Suede Shoes, etc | Free Shipping | COD Available

Visit horex.in

Key Findings

We analyzed Horex.in page load time and found that the first response time was 608 ms and then it took 6.8 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

horex.in performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value1.02

2/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

horex.in

608 ms

www.horex.in

1495 ms

autoptimize_c53b6811fa9d92daa66b594e8d6655a0.css

1311 ms

autoptimize_single_047f33e76a84f83e5e2be4ca9aacc51d.css

586 ms

css

40 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 52% of them (13 requests) were addressed to the original Horex.in, 16% (4 requests) were made to Fonts.googleapis.com and 8% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Horex.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.3 kB (62%)

Content Size

873.6 kB

After Optimization

332.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Horex.in main page is 873.6 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. 40% of websites need less resources to load. HTML takes 469.5 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 432.7 kB

  • Original 469.5 kB
  • After minification 469.4 kB
  • After compression 36.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 432.7 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-28%

Potential reduce by 62.4 kB

  • Original 222.7 kB
  • After minification 222.7 kB
  • After compression 160.4 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 62.4 kB or 28% of the original size.

CSS Optimization

-29%

Potential reduce by 46.3 kB

  • Original 159.4 kB
  • After minification 159.4 kB
  • After compression 113.1 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. Horex.in needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (76%)

Requests Now

21

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

horex.in

horex.in

608 ms

www.horex.in

www.horex.in

1495 ms

autoptimize_c53b6811fa9d92daa66b594e8d6655a0.css

autoptimize_c53b6811fa9d92daa66b594e8d6655a0.css

1311 ms

autoptimize_single_047f33e76a84f83e5e2be4ca9aacc51d.css

autoptimize_single_047f33e76a84f83e5e2be4ca9aacc51d.css

586 ms

css

css

40 ms

jquery.min.js

jquery.min.js

788 ms

s-202444.js

s-202444.js

24 ms

js

js

78 ms

hooks.min.js

hooks.min.js

570 ms

i18n.min.js

i18n.min.js

579 ms

url.min.js

url.min.js

609 ms

api-fetch.min.js

api-fetch.min.js

946 ms

wp-polyfill.min.js

wp-polyfill.min.js

1365 ms

e-202444.js

e-202444.js

5 ms

autoptimize_6a7181a5d68393482f7cd5c0908252e8.js

autoptimize_6a7181a5d68393482f7cd5c0908252e8.js

1713 ms

css

css

39 ms

css

css

56 ms

css

css

59 ms

gtm.js

gtm.js

111 ms

fbevents.js

fbevents.js

108 ms

Horex-R-yellow1-.png

Horex-R-yellow1-.png

242 ms

font

font

100 ms

font

font

99 ms

ElegantIcons.woff

ElegantIcons.woff

1605 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

790 ms

Accessibility Review

horex.in accessibility score

89

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

Links do not have a discernible name

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

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

SEO Factors

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

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 doesn't use 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 Horex.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 Horex.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

horex.in

Open Graph data is detected on the main page of Horex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: