Tools & Wizards About Us
shupple.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

shupple.com

SHUPPLE: Best eCommerce Platform for D2C Brands, Retail Stores & Local Businesses

Page Load Speed

10.2 sec in total

First Response

463 ms

Resources Loaded

8.9 sec

Page Rendered

878 ms

shupple.com screenshot

About Website

Visit shupple.com now to see the best up-to-date SHUPPLE content for India and also check out these interesting facts you probably never knew about shupple.com

Best E-Commerce Technology Platform partner for your Online Direct To Customer (D2C) sales. Marketplace, Store Website, Chat commerce, Social Media Commerce, SEO, Influencer driven sales - SHUPPLE emp...

Visit shupple.com

Key Findings

We analyzed Shupple.com page load time and found that the first response time was 463 ms and then it took 9.8 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

shupple.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.096

91/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

shupple.com

463 ms

shupple.com

1107 ms

js

83 ms

wp-emoji-release.min.js

659 ms

0bbf3.css

857 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 62% of them (31 requests) were addressed to the original Shupple.com, 24% (12 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Shupple.com.

Page Optimization Overview & Recommendations

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

Content Size

2.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shupple.com main page is 2.6 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 173.9 kB

  • Original 211.0 kB
  • After minification 211.0 kB
  • After compression 37.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. 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 173.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.0 MB
  • After minification 2.0 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. SHUPPLE images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 132 B

  • Original 185.4 kB
  • After minification 185.4 kB
  • After compression 185.3 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 5 B

  • Original 188.9 kB
  • After minification 188.9 kB
  • After compression 188.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. Shupple.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (77%)

Requests Now

31

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

shupple.com

shupple.com

463 ms

shupple.com

shupple.com

1107 ms

js

js

83 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

659 ms

0bbf3.css

0bbf3.css

857 ms

b4eb8.css

b4eb8.css

737 ms

f9c79.css

f9c79.css

1136 ms

dynamic-style.php

dynamic-style.php

2136 ms

css

css

36 ms

630b8.css

630b8.css

994 ms

css

css

47 ms

ad1f1.css

ad1f1.css

1345 ms

c63fb.js

c63fb.js

1771 ms

dde8d.js

dde8d.js

1551 ms

25534.js

25534.js

1694 ms

shupple.com

shupple.com

2130 ms

b7e07.css

b7e07.css

2056 ms

753db.css

753db.css

2434 ms

6d18f.js

6d18f.js

2433 ms

dc06c.js

dc06c.js

2740 ms

63a69.js

63a69.js

2969 ms

b4041.js

b4041.js

2986 ms

dcc3d.js

dcc3d.js

3530 ms

dfacc.js

dfacc.js

3128 ms

loader.js

loader.js

151 ms

5252f.js

5252f.js

3370 ms

29c48.js

29c48.js

3688 ms

1615d.js

1615d.js

3622 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

57 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf

100 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

197 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf

240 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

237 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf

239 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1825 ms

fa-solid-900.woff

fa-solid-900.woff

1982 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

239 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyDPA-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyDPA-9a6Vc.ttf

237 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyCjA-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyCjA-9a6Vc.ttf

235 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9a6Vc.ttf

240 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf

239 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9BO9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9BO9a6Vc.ttf

240 ms

fa-brands-400.woff

fa-brands-400.woff

2051 ms

themify.woff

themify.woff

1981 ms

xfbml.customerchat.js

xfbml.customerchat.js

93 ms

Shupple-text-1.png

Shupple-text-1.png

706 ms

3-1.png

3-1.png

3739 ms

116 ms

195 ms

shupple-homepage-hero.png

shupple-homepage-hero.png

2460 ms

Accessibility Review

shupple.com accessibility score

86

Accessibility Issues

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.

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

shupple.com 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

High

Page has valid source maps

SEO Factors

shupple.com SEO score

86

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

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 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 Shupple.com 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 Shupple.com 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

shupple.com

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