Tools & Wizards About Us
web3.storage screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

web3.storage

web3.storage ⁂ The simple file storage service for IPFS & Filecoin

Page Load Speed

1.1 sec in total

First Response

110 ms

Resources Loaded

654 ms

Page Rendered

365 ms

web3.storage screenshot

About Website

Visit web3.storage now to see the best up-to-date Web 3 content for Nigeria and also check out these interesting facts you probably never knew about web3.storage

With web3.storage you get all the benefits of decentralized storage and content addressing with the frictionless experience you expect in a modern storage solution. It’s fast, it's open and it&#x...

Visit web3.storage

Key Findings

We analyzed Web3.storage page load time and found that the first response time was 110 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

web3.storage performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

web3.storage

110 ms

e0961c60f094d77b.css

204 ms

8e0ad7d6-8d52ee7ac32e0d22.js

112 ms

4077-a726be5a61057b36.js

49 ms

main-app-1eec784c2ba7f1ea.js

25 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Web3.storage and no external sources were called. The less responsive or slowest element that took the longest time to load (262 ms) belongs to the original domain Web3.storage.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.2 kB (20%)

Content Size

208.3 kB

After Optimization

167.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Web3.storage main page is 208.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 130.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 40.9 kB

  • Original 49.2 kB
  • After minification 49.2 kB
  • After compression 8.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. 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 40.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 28.2 kB
  • After minification 28.2 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. Web 3 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 285 B

  • Original 130.8 kB
  • After minification 130.8 kB
  • After compression 130.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 8 (73%)

Requests Now

11

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web3.storage

web3.storage

110 ms

e0961c60f094d77b.css

e0961c60f094d77b.css

204 ms

8e0ad7d6-8d52ee7ac32e0d22.js

8e0ad7d6-8d52ee7ac32e0d22.js

112 ms

4077-a726be5a61057b36.js

4077-a726be5a61057b36.js

49 ms

main-app-1eec784c2ba7f1ea.js

main-app-1eec784c2ba7f1ea.js

25 ms

3359-c747cbd970f71e54.js

3359-c747cbd970f71e54.js

28 ms

3029-15c53aaba41a6869.js

3029-15c53aaba41a6869.js

25 ms

page-8c01ea415cfc45f4.js

page-8c01ea415cfc45f4.js

36 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

262 ms

email-decode.min.js

email-decode.min.js

28 ms

webpack-96a65961645f1573.js

webpack-96a65961645f1573.js

40 ms

cluster-1.44abf70c.png

cluster-1.44abf70c.png

199 ms

Accessibility Review

web3.storage accessibility score

96

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.

Best Practices

web3.storage 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

High

Browser errors were logged to the console

SEO Factors

web3.storage SEO score

100

Search Engine Optimization Advices

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 Web3.storage 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 Web3.storage 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

web3.storage

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