Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

Page Load Speed

3.2 sec in total

First Response

95 ms

Resources Loaded

2.6 sec

Page Rendered

500 ms

warehouse.space screenshot

About Website

Visit warehouse.space now to see the best up-to-date Warehouse content and also check out these interesting facts you probably never knew about warehouse.space

Visit warehouse.space

Key Findings

We analyzed Warehouse.space page load time and found that the first response time was 95 ms and then it took 3.1 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

warehouse.space performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value44.1 s

0/100

10%

Network Requests Diagram

warehouse.space

95 ms

wlDXaHWHuU4fGn9VVCvgWsCnQn4.js

231 ms

main.min.css

171 ms

animate.css

169 ms

owl.carousel.css

97 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original Warehouse.space, 6% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Warehouse.space.

Page Optimization Overview & Recommendations

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

Content Size

293.8 kB

After Optimization

260.7 kB

In fact, the total size of Warehouse.space main page is 293.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 188.1 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-11%

Potential reduce by 21.0 kB

  • Original 188.1 kB
  • After minification 167.1 kB

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, Warehouse needs image optimization as it can save up to 21.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 12.2 kB

  • Original 104.6 kB
  • After minification 104.6 kB
  • After compression 92.4 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 12.2 kB or 12% of the original size.

CSS Optimization

-1%

Potential reduce by 12 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 1.1 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. Warehouse.space has all CSS files already compressed.

Requests Breakdown

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

Requests Now

61

After Optimization

36

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

Accessibility Review

warehouse.space accessibility score

73

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

Image elements do not have [alt] attributes

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

warehouse.space best practices score

77

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

SEO Factors

warehouse.space SEO score

73

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Warehouse.space can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Warehouse.space main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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