Tools & Wizards About Us
ipfs.io screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ipfs.io

About the IPFS.io Public Gateway

Page Load Speed

6.7 sec in total

First Response

104 ms

Resources Loaded

5.1 sec

Page Rendered

1.5 sec

ipfs.io screenshot

About Website

Click here to check amazing IPFS content for United States. Otherwise, check out these important facts you probably never knew about ipfs.io

IPFS.io Public Gateway - Free public service to access IPFS content through your web browser. Bridge between HTTP and decentralized IPFS protocol without installing software.

Visit ipfs.io

Key Findings

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

Performance Metrics

ipfs.io performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

ipfs.io

104 ms

ipfs.io

33 ms

ipfs.tech

1044 ms

entry.DENThJOd.css

631 ms

default.DILa3Uds.css

747 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ipfs.io, 75% (41 requests) were made to Ipfs.tech and 22% (12 requests) were made to Fonts.bunny.net. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Ipfs.tech.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.4 kB (5%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images

In fact, the total size of Ipfs.io main page is 1.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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 81.4 kB

  • Original 99.9 kB
  • After minification 97.9 kB
  • After compression 18.5 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 81.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 4 (10%)

Requests Now

40

After Optimization

36

  • Images
  • CSS

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

Network Requests Diagram

ipfs.io

ipfs.io

104 ms

ipfs.io

ipfs.io

33 ms

ipfs.tech

ipfs.tech

1044 ms

entry.DENThJOd.css

entry.DENThJOd.css

631 ms

default.DILa3Uds.css

default.DILa3Uds.css

747 ms

index.CZYCeseQ.css

index.CZYCeseQ.css

768 ms

Grid.CfsFuo-l.css

Grid.CfsFuo-l.css

749 ms

CarouselCards.BIZdE3Oc.css

CarouselCards.BIZdE3Oc.css

751 ms

star-aurora.Btrdudp9.jpg

star-aurora.Btrdudp9.jpg

1974 ms

constellations-hero.mb3n9Cpg.svg

constellations-hero.mb3n9Cpg.svg

1095 ms

logo-anytype.D87CGOKV.png

logo-anytype.D87CGOKV.png

1154 ms

logo-wiki.OjMrUaRn.png

logo-wiki.OjMrUaRn.png

1529 ms

logo-3S.CGyLsYlv.png

logo-3S.CGyLsYlv.png

1194 ms

portrait-nancy-baker.B02DT8ZX.png

portrait-nancy-baker.B02DT8ZX.png

1450 ms

logo-weather.DgEMB3lt.png

logo-weather.DgEMB3lt.png

1618 ms

logo-snapshot.BNVc9LBP.png

logo-snapshot.BNVc9LBP.png

1589 ms

logo-ipfs.Crkf8JBP.png

logo-ipfs.Crkf8JBP.png

1658 ms

logo-lockheed.evqwyBaz.png

logo-lockheed.evqwyBaz.png

1893 ms

constellation-verifiable.BUIOD6a2.svg

constellation-verifiable.BUIOD6a2.svg

1924 ms

constellation-resilient.CJumKkYl.svg

constellation-resilient.CJumKkYl.svg

1995 ms

constellations-home-get-started.B7ZaHEIB.svg

constellations-home-get-started.B7ZaHEIB.svg

2055 ms

constellation-peer.GMZuA9J9.svg

constellation-peer.GMZuA9J9.svg

2062 ms

constellation-store.yueQFGT_.svg

constellation-store.yueQFGT_.svg

2533 ms

constellation-apps.ClXrZ6aV.svg

constellation-apps.ClXrZ6aV.svg

2333 ms

constellation-tooling.CPuvCqGB.svg

constellation-tooling.CPuvCqGB.svg

2362 ms

ribbon-home-1.Db3iUyss.jpg

ribbon-home-1.Db3iUyss.jpg

2660 ms

ribbon-home-2.xhPE7YJm.jpg

ribbon-home-2.xhPE7YJm.jpg

2825 ms

ribbon-home-3.CsPAOEU8.jpg

ribbon-home-3.CsPAOEU8.jpg

2755 ms

ribbon-home-4.VgWSxiQp.jpg

ribbon-home-4.VgWSxiQp.jpg

2813 ms

ribbon-home-5.CoUvFidO.jpg

ribbon-home-5.CoUvFidO.jpg

2805 ms

ribbon-home-6.Bz70377O.jpg

ribbon-home-6.Bz70377O.jpg

3156 ms

ribbon-home-7.BfnOpgOh.jpg

ribbon-home-7.BfnOpgOh.jpg

3199 ms

ribbon-home-8.DX1iMwOM.jpg

ribbon-home-8.DX1iMwOM.jpg

3260 ms

constellations-home-by-the-numbers.S-T4jkxF.svg

constellations-home-by-the-numbers.S-T4jkxF.svg

3227 ms

portrait-mauve-signweaver-agregore.BlsJpllQ.webp

portrait-mauve-signweaver-agregore.BlsJpllQ.webp

3244 ms

portrait-gabo-h-beaumont-mintter.BSuxrUqO.webp

portrait-gabo-h-beaumont-mintter.BSuxrUqO.webp

3259 ms

portrait-wes-floyd-bacalhau.D41i5AiQ.webp

portrait-wes-floyd-bacalhau.D41i5AiQ.webp

3602 ms

portrait-nancy-baker-cahill-artist.DIzt4Jsw.webp

portrait-nancy-baker-cahill-artist.DIzt4Jsw.webp

3621 ms

portrait-joel-thorstensson-3box-labs.B4Nr6yqK.webp

portrait-joel-thorstensson-3box-labs.B4Nr6yqK.webp

3527 ms

portrait-boris-mann-fission.Bu2TSOOE.webp

portrait-boris-mann-fission.Bu2TSOOE.webp

3137 ms

portrait-thibault-meunier-cloudflare.Ci3pj56s.webp

portrait-thibault-meunier-cloudflare.Ci3pj56s.webp

2987 ms

portrait-roland-kuhn-actyx.D0H1GfsL.webp

portrait-roland-kuhn-actyx.D0H1GfsL.webp

3004 ms

constellations-footer.BvyqPqzA.svg

constellations-footer.BvyqPqzA.svg

3337 ms

ibm-plex-sans-cyrillic-ext-400-normal.woff

ibm-plex-sans-cyrillic-ext-400-normal.woff

53 ms

ibm-plex-sans-vietnamese-400-normal.woff

ibm-plex-sans-vietnamese-400-normal.woff

41 ms

ibm-plex-sans-latin-ext-400-normal.woff

ibm-plex-sans-latin-ext-400-normal.woff

42 ms

ibm-plex-sans-cyrillic-400-normal.woff

ibm-plex-sans-cyrillic-400-normal.woff

53 ms

ibm-plex-sans-latin-400-normal.woff

ibm-plex-sans-latin-400-normal.woff

51 ms

ibm-plex-sans-greek-400-normal.woff

ibm-plex-sans-greek-400-normal.woff

76 ms

ibm-plex-sans-cyrillic-ext-700-normal.woff

ibm-plex-sans-cyrillic-ext-700-normal.woff

50 ms

ibm-plex-sans-vietnamese-700-normal.woff

ibm-plex-sans-vietnamese-700-normal.woff

49 ms

ibm-plex-sans-latin-ext-700-normal.woff

ibm-plex-sans-latin-ext-700-normal.woff

51 ms

ibm-plex-sans-cyrillic-700-normal.woff

ibm-plex-sans-cyrillic-700-normal.woff

51 ms

ibm-plex-sans-latin-700-normal.woff

ibm-plex-sans-latin-700-normal.woff

53 ms

ibm-plex-sans-greek-700-normal.woff

ibm-plex-sans-greek-700-normal.woff

75 ms

Accessibility Review

ipfs.io accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Best Practices

ipfs.io best practices score

92

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

SEO Factors

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

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 Ipfs.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 Ipfs.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

ipfs.io

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