Tools & Wizards About Us
weazy.in screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

weazy.in

Weazy - Best Ecommerce Platform | Ecommerce Website Builder

Page Load Speed

20.6 sec in total

First Response

1.3 sec

Resources Loaded

13.8 sec

Page Rendered

5.5 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 1.3 sec and then it took 19.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

weazy.in performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

weazy.in

1322 ms

css2

43 ms

css2

55 ms

fontawesome.css

983 ms

brands.css

1345 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 56% of them (41 requests) were addressed to the original Weazy.in, 19% (14 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Blogsadmin.weazy.in. The less responsive or slowest element that took the longest time to load (9.1 sec) belongs to the original domain Weazy.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 684.1 kB (7%)

Content Size

9.7 MB

After Optimization

9.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 51.8 kB

  • Original 65.1 kB
  • After minification 50.4 kB
  • After compression 13.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 23% 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 51.8 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 465.8 kB

  • Original 9.2 MB
  • After minification 8.8 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.6 kB

  • Original 171.5 kB
  • After minification 171.5 kB
  • After compression 108.9 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.6 kB or 37% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 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

1322 ms

css2

css2

43 ms

css2

css2

55 ms

fontawesome.css

fontawesome.css

983 ms

brands.css

brands.css

1345 ms

solid.css

solid.css

1267 ms

line-awesome.min.css

line-awesome.min.css

949 ms

bootstrap.min.css

bootstrap.min.css

1010 ms

swiper-bundle.min.css

swiper-bundle.min.css

1284 ms

style.css

style.css

3153 ms

js

js

82 ms

sdk.js

sdk.js

35 ms

email-decode.min.js

email-decode.min.js

986 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

37 ms

bootstrap.min.js

bootstrap.min.js

1966 ms

swiper-bundle.min.js

swiper-bundle.min.js

1987 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

2255 ms

wow.min.js

wow.min.js

2233 ms

main.js

main.js

2306 ms

ScrollMagic.min.js

ScrollMagic.min.js

41 ms

debug.addIndicators.min.js

debug.addIndicators.min.js

51 ms

jquery-1.12.4.js

jquery-1.12.4.js

4222 ms

jquery.counterup.min.js

jquery.counterup.min.js

2967 ms

modernizr.custom.js

modernizr.custom.js

3273 ms

draggabilly.pkgd.min.js

draggabilly.pkgd.min.js

3274 ms

elastiStack.js

elastiStack.js

3309 ms

css2

css2

24 ms

widget

widget

1236 ms

logo-black.png

logo-black.png

1036 ms

india.png

india.png

1296 ms

banner.jpg

banner.jpg

6268 ms

2.jpg

2.jpg

978 ms

Restaurant%20image.png

Restaurant%20image.png

2530 ms

1.jpg

1.jpg

1921 ms

3.jpg

3.jpg

1919 ms

1.jpg

1.jpg

2001 ms

2.jpg

2.jpg

3241 ms

3.jpg

3.jpg

3155 ms

4.jpg

4.jpg

2894 ms

5.jpg

5.jpg

2935 ms

about.jpg

about.jpg

4432 ms

9.jpeg

9.jpeg

4631 ms

aakash.jpg

aakash.jpg

3887 ms

1.png

1.png

4439 ms

2.png

2.png

4203 ms

3.png

3.png

4883 ms

sdk.js

sdk.js

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

127 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

133 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

150 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

149 ms

fa-solid-900.ttf

fa-solid-900.ttf

9097 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

113 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

112 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

112 ms

pxiByp8kv8JHgFVrLFj_V1s.ttf

pxiByp8kv8JHgFVrLFj_V1s.ttf

113 ms

pxiGyp8kv8JHgFVrLPTedw.ttf

pxiGyp8kv8JHgFVrLPTedw.ttf

114 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

114 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

114 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

115 ms

la-solid-900.woff

la-solid-900.woff

4368 ms

la-regular-400.woff

la-regular-400.woff

7008 ms

fa-brands-400.ttf

fa-brands-400.ttf

6308 ms

fetch_latest_update

fetch_latest_update

861 ms

website

website

246 ms

floatbutton1_91yhxHJAKn3JBwukUQ098f-1W7bBXYfzbYjqq3lClUJ2rTbyrjBiQd4nYFVD5hBu_.css

floatbutton1_91yhxHJAKn3JBwukUQ098f-1W7bBXYfzbYjqq3lClUJ2rTbyrjBiQd4nYFVD5hBu_.css

601 ms

floatbutton1_fHhL9IuH2KCQKHWL4MorQH8JLuM7B9a9tXA6y0HDnNl_MvqIw_aL4Op_V-QdkXEl_.js

floatbutton1_fHhL9IuH2KCQKHWL4MorQH8JLuM7B9a9tXA6y0HDnNl_MvqIw_aL4Op_V-QdkXEl_.js

886 ms

1708667576.png

1708667576.png

2098 ms

1708427305.jpg

1708427305.jpg

2132 ms

1708345566.jpg

1708345566.jpg

3102 ms

siq_nUNN3S_HLwb37_ohNsijSS5AR1dVYEwuQl3qPcCeJ-gCSlQr9mtPWoHJ1wbZ-0PQ_.ttf

siq_nUNN3S_HLwb37_ohNsijSS5AR1dVYEwuQl3qPcCeJ-gCSlQr9mtPWoHJ1wbZ-0PQ_.ttf

143 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

67

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

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: