Tools & Wizards About Us
wherehouse.io screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wherehouse.io

Wherehouse | Signup for free as D2C brand or warehouse

Page Load Speed

3.2 sec in total

First Response

44 ms

Resources Loaded

2.7 sec

Page Rendered

498 ms

wherehouse.io screenshot

About Website

Welcome to wherehouse.io homepage info - get ready to check Wherehouse best content for India right away, or after learning these important things about wherehouse.io

We provide on demand warehouses to D2C brands and help them deliver on the same day resulting in better customer experience and optimized supply chain.

Visit wherehouse.io

Key Findings

We analyzed Wherehouse.io page load time and found that the first response time was 44 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wherehouse.io performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value27.3 s

0/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

wherehouse.io

44 ms

www.wherehouse.io

20 ms

bootstrap.min.css

41 ms

css2

56 ms

css2

74 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 56% of them (39 requests) were addressed to the original Wherehouse.io, 11% (8 requests) were made to Unpkg.com and 11% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Wherehouse-prod-content.s3.ap-south-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (22%)

Content Size

5.0 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wherehouse.io main page is 5.0 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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.7 kB

  • Original 37.4 kB
  • After minification 27.7 kB
  • After compression 6.7 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 9.7 kB, which is 26% 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 30.7 kB or 82% of the original size.

Image Optimization

-22%

Potential reduce by 1.1 MB

  • Original 4.9 MB
  • After minification 3.9 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. Obviously, Wherehouse needs image optimization as it can save up to 1.1 MB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 283 B

  • Original 7.6 kB
  • After minification 7.6 kB
  • After compression 7.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.

Requests Breakdown

Number of requests can be reduced by 15 (27%)

Requests Now

55

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wherehouse.io

wherehouse.io

44 ms

www.wherehouse.io

www.wherehouse.io

20 ms

bootstrap.min.css

bootstrap.min.css

41 ms

css2

css2

56 ms

css2

css2

74 ms

swiper-bundle.css

swiper-bundle.css

50 ms

swiper-bundle.min.css

swiper-bundle.min.css

59 ms

index.css

index.css

13 ms

logo.png

logo.png

24 ms

happy-girl.png

happy-girl.png

2525 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

35 ms

swiper-bundle.js

swiper-bundle.js

70 ms

swiper-bundle.min.js

swiper-bundle.min.js

63 ms

index.js

index.js

25 ms

firebase-app.js

firebase-app.js

34 ms

dots.png

dots.png

24 ms

AdobeStock_431639229%201.png

AdobeStock_431639229%201.png

43 ms

triangles%20-%20Copy.png

triangles%20-%20Copy.png

24 ms

main.gif

main.gif

44 ms

box.png

box.png

26 ms

1.png

1.png

32 ms

3.png

3.png

26 ms

2.png

2.png

27 ms

4.png

4.png

32 ms

control.png

control.png

31 ms

visibility.png

visibility.png

32 ms

delight.png

delight.png

41 ms

control1.png

control1.png

41 ms

control2.png

control2.png

41 ms

control3.png

control3.png

41 ms

control4.png

control4.png

42 ms

visibility1.png

visibility1.png

43 ms

visibility2.png

visibility2.png

42 ms

visibility3.png

visibility3.png

43 ms

visibility4.png

visibility4.png

44 ms

delight1.png

delight1.png

44 ms

delight2.png

delight2.png

44 ms

delight3.png

delight3.png

45 ms

delight4.png

delight4.png

44 ms

map.png

map.png

49 ms

steps-mobile.png

steps-mobile.png

46 ms

steps.png

steps.png

46 ms

instagram%201.png

instagram%201.png

47 ms

linkedin-2%201.png

linkedin-2%201.png

47 ms

logomark%20(1).png

logomark%20(1).png

47 ms

swiper-bundle.css

swiper-bundle.css

23 ms

swiper-bundle.min.css

swiper-bundle.min.css

57 ms

swiper-bundle.min.js

swiper-bundle.min.js

17 ms

swiper-bundle.js

swiper-bundle.js

35 ms

lightbg.png

lightbg.png

8 ms

7a91b4v6pa

7a91b4v6pa

61 ms

widget

widget

1255 ms

fbevents.js

fbevents.js

20 ms

darkbg.png

darkbg.png

6 ms

bg-pattern.png

bg-pattern.png

5 ms

background.png

background.png

11 ms

clarity.js

clarity.js

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

45 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDKIw.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffHjDKIw.ttf

38 ms

NaPDcZTIAOhVxoMyOr9n_E7ffEDBKIw.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffEDBKIw.ttf

37 ms

NaPDcZTIAOhVxoMyOr9n_E7ffBzCKIw.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffBzCKIw.ttf

35 ms

NaPecZTIAOhVxoMyOr9n_E7fRMQ.ttf

NaPecZTIAOhVxoMyOr9n_E7fRMQ.ttf

37 ms

website

website

233 ms

floatbutton1_5Exiot6Sf7v3AnSCYZCRZjPr5YSBSZklIEwXMYBHeiQ__HoYNWnSox54GymPQ7Gt_.css

floatbutton1_5Exiot6Sf7v3AnSCYZCRZjPr5YSBSZklIEwXMYBHeiQ__HoYNWnSox54GymPQ7Gt_.css

93 ms

floatbutton1_lJh-PCKLwvK_w7d-UVDeLoqlU29fBKxs0Cl4Q1Mpxjgw-99CjmnEh6pBRIKTVY1v_.js

floatbutton1_lJh-PCKLwvK_w7d-UVDeLoqlU29fBKxs0Cl4Q1Mpxjgw-99CjmnEh6pBRIKTVY1v_.js

100 ms

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

20 ms

c.gif

c.gif

7 ms

Accessibility Review

wherehouse.io accessibility score

82

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.

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

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

wherehouse.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

wherehouse.io SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Wherehouse.io 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 Wherehouse.io 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

wherehouse.io

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