Tools & Wizards About Us
ankr.network screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ankr.network

Ankr | The Fastest Web3 Infrastructure

Page Load Speed

8 sec in total

First Response

11 ms

Resources Loaded

1.7 sec

Page Rendered

6.3 sec

ankr.network screenshot

About Website

Click here to check amazing Ankr content for United States. Otherwise, check out these important facts you probably never knew about ankr.network

Build on Web3 with a fast, reliable and distributed network of blockchain nodes. Earn with Liquid Staking and integrate it to power your app.

Visit ankr.network

Key Findings

We analyzed Ankr.network page load time and found that the first response time was 11 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ankr.network performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value46,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.873

0/100

15%

TTI (Time to Interactive)

Value57.8 s

0/100

10%

Network Requests Diagram

ankr.network

11 ms

www.ankr.com

40 ms

stylesheet.css

18 ms

stylesheet.css

39 ms

stylesheet.css

39 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ankr.network, 75% (52 requests) were made to Ankr.com and 10% (7 requests) were made to Assets.ankr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Assets.ankr.com.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ankr.network main page is 1.4 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 289.5 kB

  • Original 334.1 kB
  • After minification 334.1 kB
  • After compression 44.6 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 289.5 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-1%

Potential reduce by 147 B

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 23.0 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

-43%

Potential reduce by 1.5 kB

  • Original 3.5 kB
  • After minification 3.2 kB
  • After compression 2.0 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. Ankr.network needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (58%)

Requests Now

62

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ankr.network

ankr.network

11 ms

www.ankr.com

www.ankr.com

40 ms

stylesheet.css

stylesheet.css

18 ms

stylesheet.css

stylesheet.css

39 ms

stylesheet.css

stylesheet.css

39 ms

icon

icon

65 ms

css2

css2

84 ms

embed.js

embed.js

66 ms

styles.4ccb09d5.chunk.css

styles.4ccb09d5.chunk.css

42 ms

index.js

index.js

164 ms

polyfills-ff39e0ca5416ac95875f.js

polyfills-ff39e0ca5416ac95875f.js

216 ms

main-eee24f51f7ca33095b20.js

main-eee24f51f7ca33095b20.js

38 ms

webpack-ba962f8588eb4860f62b.js

webpack-ba962f8588eb4860f62b.js

55 ms

framework.e78a44aa1cf7f14aed31.js

framework.e78a44aa1cf7f14aed31.js

57 ms

4f149b58.b82f7cf51bed7b921283.js

4f149b58.b82f7cf51bed7b921283.js

39 ms

commons.2a38f01ae11f62b00185.js

commons.2a38f01ae11f62b00185.js

56 ms

42cfd6867196eb8062e2a8a4faabd85a49cc5ded.fbc8fbb89724dc2179b7.js

42cfd6867196eb8062e2a8a4faabd85a49cc5ded.fbc8fbb89724dc2179b7.js

53 ms

8ede4c12ee3c4641f47ae2d753835abb6d05ea3f.a728349e464a06f5db68.js

8ede4c12ee3c4641f47ae2d753835abb6d05ea3f.a728349e464a06f5db68.js

53 ms

styles.16fbc46bbd2f89b91fdc.js

styles.16fbc46bbd2f89b91fdc.js

67 ms

_app-54b54659c370b631bf64.js

_app-54b54659c370b631bf64.js

71 ms

19250ba1.98f4ea5eb847df02f68b.js

19250ba1.98f4ea5eb847df02f68b.js

66 ms

e94e41cf8a026f7a9fc543b41cb167182cb40191.594bfebbba699392c315.js

e94e41cf8a026f7a9fc543b41cb167182cb40191.594bfebbba699392c315.js

156 ms

2c6a368393335d240f269c1a617e1ce86a7f9a29.e4f24f609f5b513241d1.js

2c6a368393335d240f269c1a617e1ce86a7f9a29.e4f24f609f5b513241d1.js

155 ms

index-9886619dfa51a738db12.js

index-9886619dfa51a738db12.js

156 ms

_buildManifest.js

_buildManifest.js

159 ms

_ssgManifest.js

_ssgManifest.js

158 ms

gtm.js

gtm.js

338 ms

63229278a62b944e970d6175

63229278a62b944e970d6175

331 ms

arbitrum.svg

arbitrum.svg

990 ms

Avalanche.svg

Avalanche.svg

1316 ms

Binance.svg

Binance.svg

1291 ms

ethereum.svg

ethereum.svg

1305 ms

fandom.svg

fandom.svg

1313 ms

celo.svg

celo.svg

1301 ms

polygon.svg

polygon.svg

1317 ms

polygon-a3ab2ed004368ab8e9e4666a50b45075.svg

polygon-a3ab2ed004368ab8e9e4666a50b45075.svg

64 ms

binance-85ce97631c09075cb21e939f31631e24.svg

binance-85ce97631c09075cb21e939f31631e24.svg

20 ms

optimist-1d63c187e4c29251c280a733974cfe88.svg

optimist-1d63c187e4c29251c280a733974cfe88.svg

91 ms

aave-dc5f2833e4ceec7f57b63dc33656ab76.svg

aave-dc5f2833e4ceec7f57b63dc33656ab76.svg

259 ms

spiritswap-434c5065e5c73f6215bcd1bdf39718c2.svg

spiritswap-434c5065e5c73f6215bcd1bdf39718c2.svg

92 ms

avalanche-663d2959a5ec9615fe4e85cfaa270c6e.svg

avalanche-663d2959a5ec9615fe4e85cfaa270c6e.svg

255 ms

1inch-exchange-675d94840cf604ef808fb59a66da9866.svg

1inch-exchange-675d94840cf604ef808fb59a66da9866.svg

269 ms

project-galaxy-fbb6c63348da57e43151aada99483601.svg

project-galaxy-fbb6c63348da57e43151aada99483601.svg

272 ms

zapper-6f9fae8f415159938c822d03e5588991.svg

zapper-6f9fae8f415159938c822d03e5588991.svg

266 ms

sushiswap-3eb17b74b41758cc54ce653be3a53cf8.svg

sushiswap-3eb17b74b41758cc54ce653be3a53cf8.svg

264 ms

builders-6676903c2f992525f3ffb0de18b8b767.svg

builders-6676903c2f992525f3ffb0de18b8b767.svg

939 ms

infrastructure-b22cef487be881fdc0b2b423876e78c1.png

infrastructure-b22cef487be881fdc0b2b423876e78c1.png

991 ms

developers-ac9b3667caaca13569d7d98ff5c5d938.svg

developers-ac9b3667caaca13569d7d98ff5c5d938.svg

944 ms

gamers-47bf07615800b1466730b51c88310ac1.svg

gamers-47bf07615800b1466730b51c88310ac1.svg

947 ms

Solana-4e6b884ee4ad73392b23ec339d463d7d.svg

Solana-4e6b884ee4ad73392b23ec339d463d7d.svg

945 ms

Gnosis-f9d778d4132f9af78b03db5ce0b2e0aa.svg

Gnosis-f9d778d4132f9af78b03db5ce0b2e0aa.svg

951 ms

Moonbeam-25d832a3bf62d67237ae412d32aa53e3.svg

Moonbeam-25d832a3bf62d67237ae412d32aa53e3.svg

988 ms

Near-e8cc26c0bc24c373a56bf9a568323677.svg

Near-e8cc26c0bc24c373a56bf9a568323677.svg

991 ms

Nervos-60008ea861fe9594520a1266bb580657.svg

Nervos-60008ea861fe9594520a1266bb580657.svg

993 ms

Optimism-93c81f37cc48a41a071dc5800fdbe35b.svg

Optimism-93c81f37cc48a41a071dc5800fdbe35b.svg

1008 ms

Harmony-79dde015c9a98e109330a3a664f0abf0.svg

Harmony-79dde015c9a98e109330a3a664f0abf0.svg

985 ms

iotex-15c9b105129c9229e198c2340c164d36.svg

iotex-15c9b105129c9229e198c2340c164d36.svg

1025 ms

neutral-62dc30ee144659808da7bb4cb9a32851.svg

neutral-62dc30ee144659808da7bb4cb9a32851.svg

1012 ms

chain-7ea5767feea01e6915fecab2075d9f0b.svg

chain-7ea5767feea01e6915fecab2075d9f0b.svg

1014 ms

decentralized-c40c22aaf4106c88cb3669785422aeac.svg

decentralized-c40c22aaf4106c88cb3669785422aeac.svg

1013 ms

lightning-5071cd61d44dfc7f7582d9a1abeb6866.svg

lightning-5071cd61d44dfc7f7582d9a1abeb6866.svg

1019 ms

Inter-Medium.woff

Inter-Medium.woff

883 ms

TTFirsNeue-DemiBold.woff

TTFirsNeue-DemiBold.woff

780 ms

Inter-Regular.woff

Inter-Regular.woff

880 ms

Inter-SemiBold.woff

Inter-SemiBold.woff

879 ms

Inter-Bold.woff

Inter-Bold.woff

880 ms

iframe.js

iframe.js

728 ms

analytics.js

analytics.js

819 ms

hotjar-3065256.js

hotjar-3065256.js

906 ms

Accessibility Review

ankr.network accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

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

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

ankr.network best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

ankr.network SEO score

92

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

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 Ankr.network 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 Ankr.network 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

ankr.network

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