Tools & Wizards About Us
weazy.in screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

weazy.in

Weazy - Best Ecommerce Platform | Ecommerce Website Builder

Page Load Speed

10.3 sec in total

First Response

30 ms

Resources Loaded

9.2 sec

Page Rendered

1.1 sec

weazy.in screenshot

About Website

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

Set up Your Own online store In few simple steps & enhance your business digitally. Sell Online, Unlimited 24/7 Support, Integrate payments and shipping.

Visit weazy.in

Key Findings

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

Performance Metrics

weazy.in performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.17

70/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

weazy.in

30 ms

weazy.in

1787 ms

css2

44 ms

css2

60 ms

fontawesome.css

812 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 60% of them (42 requests) were addressed to the original Weazy.in, 20% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Weazy.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.9 kB (11%)

Content Size

3.1 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weazy.in main page is 3.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 47.7 kB

  • Original 60.1 kB
  • After minification 45.4 kB
  • After compression 12.3 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 14.7 kB, which is 24% 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 47.7 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 122.6 kB

  • Original 2.7 MB
  • After minification 2.5 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. Weazy images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 103.9 kB

  • Original 226.5 kB
  • After minification 226.5 kB
  • After compression 122.6 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 103.9 kB or 46% of the original size.

CSS Optimization

-37%

Potential reduce by 62.7 kB

  • Original 171.7 kB
  • After minification 171.7 kB
  • After compression 109.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. Weazy.in needs all CSS files to be minified and compressed as it can save up to 62.7 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (57%)

Requests Now

49

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weazy.in

weazy.in

30 ms

weazy.in

weazy.in

1787 ms

css2

css2

44 ms

css2

css2

60 ms

fontawesome.css

fontawesome.css

812 ms

brands.css

brands.css

786 ms

solid.css

solid.css

969 ms

line-awesome.min.css

line-awesome.min.css

1582 ms

bootstrap.min.css

bootstrap.min.css

934 ms

swiper-bundle.min.css

swiper-bundle.min.css

796 ms

style.css

style.css

1558 ms

js

js

90 ms

sdk.js

sdk.js

31 ms

email-decode.min.js

email-decode.min.js

797 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

35 ms

bootstrap.min.js

bootstrap.min.js

1727 ms

swiper-bundle.min.js

swiper-bundle.min.js

1570 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1729 ms

wow.min.js

wow.min.js

1897 ms

main.js

main.js

2455 ms

ScrollMagic.min.js

ScrollMagic.min.js

38 ms

debug.addIndicators.min.js

debug.addIndicators.min.js

46 ms

jquery-1.12.4.js

jquery-1.12.4.js

2465 ms

jquery.counterup.min.js

jquery.counterup.min.js

2350 ms

modernizr.custom.js

modernizr.custom.js

2648 ms

draggabilly.pkgd.min.js

draggabilly.pkgd.min.js

2654 ms

elastiStack.js

elastiStack.js

2799 ms

css2

css2

21 ms

widget

widget

1252 ms

logo-black.jpg

logo-black.jpg

1656 ms

india.png

india.png

1786 ms

banner.jpg

banner.jpg

2895 ms

2.jpg

2.jpg

1971 ms

Restaurant%20image.png

Restaurant%20image.png

2028 ms

1.jpg

1.jpg

1958 ms

3.jpg

3.jpg

2604 ms

1.jpg

1.jpg

2718 ms

2.jpg

2.jpg

2770 ms

3.jpg

3.jpg

2909 ms

4.jpg

4.jpg

2959 ms

5.jpg

5.jpg

3409 ms

about.jpg

about.jpg

3652 ms

9.jpeg

9.jpeg

3559 ms

aakash.jpg

aakash.jpg

3835 ms

1.png

1.png

3844 ms

2.png

2.png

3868 ms

3.png

3.png

4187 ms

sdk.js

sdk.js

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

78 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

83 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

102 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

102 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

100 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

106 ms

fa-solid-900.ttf

fa-solid-900.ttf

5743 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

57 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

57 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

58 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

59 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

58 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

58 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

57 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

82 ms

la-solid-900.woff

la-solid-900.woff

5387 ms

la-regular-400.woff

la-regular-400.woff

4989 ms

fa-brands-400.ttf

fa-brands-400.ttf

5600 ms

website

website

227 ms

floatbutton1_5Exiot6Sf7v3AnSCYZCRZjPr5YSBSZklIEwXMYBHeiQ__HoYNWnSox54GymPQ7Gt_.css

floatbutton1_5Exiot6Sf7v3AnSCYZCRZjPr5YSBSZklIEwXMYBHeiQ__HoYNWnSox54GymPQ7Gt_.css

93 ms

floatbutton1_KaNl0OnNr-PntbIujxJywW7jfCcnE0PhMiK8VBzGxCXPZm7c12lhzhiiesr87QnZ_.js

floatbutton1_KaNl0OnNr-PntbIujxJywW7jfCcnE0PhMiK8VBzGxCXPZm7c12lhzhiiesr87QnZ_.js

108 ms

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

21 ms

Accessibility Review

weazy.in accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

weazy.in best practices score

75

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

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

weazy.in SEO score

75

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

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

weazy.in

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