Report Summary

  • 3

    Performance

    Renders faster than
    29% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    29% of websites

  • 84

    SEO

    Google-friendlier than
    60% of websites

shaze.in

Shop For Luxury At Shaze.in - Elevate Your Premium Lifestyle

Page Load Speed

10.1 sec in total

First Response

1.7 sec

Resources Loaded

8 sec

Page Rendered

434 ms

shaze.in screenshot

About Website

Welcome to shaze.in homepage info - get ready to check Shaze best content for India right away, or after learning these important things about shaze.in

Discover our range of bold designs that accentuate your wardrobe and living room. Barware, Hosting, Perfumes, Watches, Décor, Fashion Jewellery & more.

Visit shaze.in

Key Findings

We analyzed Shaze.in page load time and found that the first response time was 1.7 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Shaze.in rating and web reputation

Performance Metrics

shaze.in performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.725

6/100

15%

TTI (Time to Interactive)

Value30.1 s

0/100

10%

Network Requests Diagram

index.aspx

1747 ms

css

26 ms

css

38 ms

css

46 ms

Common1.css

1107 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 18% of them (17 requests) were addressed to the original Shaze.in, 49% (45 requests) were made to S3-ap-southeast-1.amazonaws.com and 3% (3 requests) were made to Evbk2-sg.gsecondscreen.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source S3-ap-southeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (32%)

Content Size

3.7 MB

After Optimization

2.5 MB

In fact, the total size of Shaze.in main page is 3.7 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. 50% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 351.9 kB

  • Original 378.1 kB
  • After minification 200.9 kB
  • After compression 26.1 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. This page needs HTML code to be minified as it can gain 177.2 kB, which is 47% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 351.9 kB or 93% of the original size.

Image Optimization

-6%

Potential reduce by 155.3 kB

  • Original 2.4 MB
  • After minification 2.2 MB

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. Shaze images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 394.5 kB

  • Original 591.6 kB
  • After minification 552.5 kB
  • After compression 197.1 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 394.5 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 305.0 kB

  • Original 361.8 kB
  • After minification 325.8 kB
  • After compression 56.8 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. Shaze.in needs all CSS files to be minified and compressed as it can save up to 305.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (41%)

Requests Now

85

After Optimization

50

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

Accessibility Review

shaze.in accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

<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

Best Practices

shaze.in best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

shaze.in SEO score

84

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

High

Tap targets are not sized appropriately

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