Tools & Wizards About Us
avascan.info screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

avascan.info

Avalanche Blockchain Explorer | AVAX Explorer | AVASCAN

Page Load Speed

964 ms in total

First Response

10 ms

Resources Loaded

816 ms

Page Rendered

138 ms

avascan.info screenshot

About Website

Click here to check amazing AVASCAN content for United States. Otherwise, check out these important facts you probably never knew about avascan.info

Explore the Avalanche network: search Blockchains, Transactions, Assets, Validators, Delegations, Staking statistics and Supply data

Visit avascan.info

Key Findings

We analyzed Avascan.info page load time and found that the first response time was 10 ms and then it took 954 ms 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

avascan.info performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value33.2 s

0/100

10%

TBT (Total Blocking Time)

Value66,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.789

5/100

15%

TTI (Time to Interactive)

Value81.1 s

0/100

10%

Network Requests Diagram

avascan.info

10 ms

avascan.info

179 ms

gtm.js

80 ms

66ea0b1705f1ec19.css

308 ms

polyfills-c67a75d1b6f99dc8.js

100 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 57% of them (29 requests) were addressed to the original Avascan.info, 39% (20 requests) were made to Cms-cdn.avascan.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (626 ms) belongs to the original domain Avascan.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 315.6 kB (35%)

Content Size

907.2 kB

After Optimization

591.6 kB

  • HTML
  • Images

In fact, the total size of Avascan.info main page is 907.2 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. 60% of websites need less resources to load. Images take 851.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 44.8 kB

  • Original 55.6 kB
  • After minification 55.5 kB
  • After compression 10.8 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 44.8 kB or 81% of the original size.

Image Optimization

-32%

Potential reduce by 270.8 kB

  • Original 851.6 kB
  • After minification 580.8 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, AVASCAN needs image optimization as it can save up to 270.8 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

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

Requests Now

46

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AVASCAN. 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

avascan.info

avascan.info

10 ms

avascan.info

avascan.info

179 ms

gtm.js

gtm.js

80 ms

66ea0b1705f1ec19.css

66ea0b1705f1ec19.css

308 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

100 ms

webpack-09ea8ba4bcbf8d56.js

webpack-09ea8ba4bcbf8d56.js

282 ms

framework-ce84985cd166733a.js

framework-ce84985cd166733a.js

367 ms

main-8561f31a8580e971.js

main-8561f31a8580e971.js

366 ms

_app-29c12c8c3906423b.js

_app-29c12c8c3906423b.js

626 ms

index-32574cdd5d851b03.js

index-32574cdd5d851b03.js

140 ms

_buildManifest.js

_buildManifest.js

188 ms

_ssgManifest.js

_ssgManifest.js

238 ms

Group_313_099958ed87.png

Group_313_099958ed87.png

74 ms

c-chain.86f18e0a2d9d.png

c-chain.86f18e0a2d9d.png

62 ms

svgdefs.svg

svgdefs.svg

367 ms

arrow.png

arrow.png

356 ms

wallet.svg

wallet.svg

357 ms

defs.svg

defs.svg

371 ms

avascan-logocomplete-darkbg.svg

avascan-logocomplete-darkbg.svg

421 ms

logo-coinmarketcap.svg

logo-coinmarketcap.svg

391 ms

logo-coingecko.svg

logo-coingecko.svg

395 ms

logo-coinstats.svg

logo-coinstats.svg

392 ms

logo-stakingrewards.png

logo-stakingrewards.png

420 ms

logo-coinpaprika.svg

logo-coinpaprika.svg

455 ms

logo-messari.svg

logo-messari.svg

461 ms

logo-geckoterminal.svg

logo-geckoterminal.svg

464 ms

metamask.svg

metamask.svg

463 ms

walletconnect.svg

walletconnect.svg

515 ms

Qm_QB_48m15_Tzh_U_Frmu56_QCR_Qjkrkg_Ua_Kfg_Cm_KE_8o3_Rzmu_PJ_removebg_preview_f505a0035a.png

Qm_QB_48m15_Tzh_U_Frmu56_QCR_Qjkrkg_Ua_Kfg_Cm_KE_8o3_Rzmu_PJ_removebg_preview_f505a0035a.png

55 ms

DEXALOT_Logo_Mark_4x_ac1f909cd1.png

DEXALOT_Logo_Mark_4x_ac1f909cd1.png

57 ms

Hubble_Logo_PNG_7c923bf8bf.png

Hubble_Logo_PNG_7c923bf8bf.png

60 ms

uptn-logo-cb623ccecc.png

uptn-logo-cb623ccecc.png

54 ms

Beam_subnet.d5e828c36c75.png

Beam_subnet.d5e828c36c75.png

63 ms

stepnetwork.516bdfd8829a.svg

stepnetwork.516bdfd8829a.svg

57 ms

Xeta_Token_removebg_preview_f0bdab0f76.png

Xeta_Token_removebg_preview_f0bdab0f76.png

60 ms

P_Chain_2_7b541d3879.png

P_Chain_2_7b541d3879.png

60 ms

Playa3ull_Logo_stacked_colour_inv_65e418f60b.png

Playa3ull_Logo_stacked_colour_inv_65e418f60b.png

79 ms

DOS_logo_Circle_446d040f4f.svg

DOS_logo_Circle_446d040f4f.svg

60 ms

small_meld_67fae9147d.png

small_meld_67fae9147d.png

66 ms

X_Chain_2_b7475221d2.png

X_Chain_2_b7475221d2.png

64 ms

Numbers_02_a87d3b077c_e5ef9f696b.png

Numbers_02_a87d3b077c_e5ef9f696b.png

65 ms

Swimmer_050be7d67a.png

Swimmer_050be7d67a.png

64 ms

Immagine_2022_06_14_105600_removebg_preview_ea15bbe651.png

Immagine_2022_06_14_105600_removebg_preview_ea15bbe651.png

78 ms

xplus_icon_8965678998.png

xplus_icon_8965678998.png

79 ms

Sharpnel_logo_chain_e860ab8077.png

Sharpnel_logo_chain_e860ab8077.png

78 ms

loco_b358f674fe.png

loco_b358f674fe.png

80 ms

MIntara_subnet.bb02351f1e67.png

MIntara_subnet.bb02351f1e67.png

79 ms

avascan-header-bg.jpg

avascan-header-bg.jpg

180 ms

ibmplexmono-light-webfont.woff

ibmplexmono-light-webfont.woff

164 ms

rubik-light-webfont.woff

rubik-light-webfont.woff

165 ms

rubik-medium-webfont.woff

rubik-medium-webfont.woff

143 ms

Accessibility Review

avascan.info accessibility score

74

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

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

avascan.info 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

Missing source maps for large first-party JavaScript

SEO Factors

avascan.info SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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 Avascan.info 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 Avascan.info 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

avascan.info

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