Tools & Wizards About Us
metapool.app screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    56% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

metapool.app

Page Load Speed

38.1 sec in total

First Response

487 ms

Resources Loaded

7.9 sec

Page Rendered

29.7 sec

metapool.app screenshot

About Website

Visit metapool.app now to see the best up-to-date Metapool content for United States and also check out these interesting facts you probably never knew about metapool.app

Liquid Stake NEAR with Meta Pool. Receive stNEAR to simultaneously accrue NEAR staking rewards and add APY from other DeFi protocols

Visit metapool.app

Key Findings

We analyzed Metapool.app page load time and found that the first response time was 487 ms and then it took 37.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

metapool.app performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value28,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

metapool.app

487 ms

2097363ef34623d5.css

319 ms

polyfills-5cd94c89d3acac5f.js

553 ms

webpack-42cdea76c8170223.js

546 ms

framework-fc97f3f1282ce3ed.js

704 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 95% of them (58 requests) were addressed to the original Metapool.app, 5% (3 requests) were made to Blog.metapool.app. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Metapool.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.5 kB (28%)

Content Size

402.6 kB

After Optimization

289.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metapool.app main page is 402.6 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. 75% 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 268.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 113.4 kB

  • Original 133.2 kB
  • After minification 132.9 kB
  • After compression 19.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 113.4 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 268.0 kB
  • After minification 268.0 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. Metapool images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 44 B

  • Original 665 B
  • After minification 665 B
  • After compression 621 B

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

-2%

Potential reduce by 12 B

  • Original 728 B
  • After minification 728 B
  • After compression 716 B

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. Metapool.app has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (22%)

Requests Now

55

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metapool.app

metapool.app

487 ms

2097363ef34623d5.css

2097363ef34623d5.css

319 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

553 ms

webpack-42cdea76c8170223.js

webpack-42cdea76c8170223.js

546 ms

framework-fc97f3f1282ce3ed.js

framework-fc97f3f1282ce3ed.js

704 ms

main-fd151b022b8415b7.js

main-fd151b022b8415b7.js

675 ms

_app-cc4ff1e647a0add1.js

_app-cc4ff1e647a0add1.js

702 ms

458-122bab6b544b3f57.js

458-122bab6b544b3f57.js

6184 ms

199-aae4e0f9103acddb.js

199-aae4e0f9103acddb.js

6216 ms

592-161d233b86235312.js

592-161d233b86235312.js

6191 ms

index-86ec9d5235e67080.js

index-86ec9d5235e67080.js

6192 ms

_buildManifest.js

_buildManifest.js

6192 ms

_ssgManifest.js

_ssgManifest.js

6193 ms

_middlewareManifest.js

_middlewareManifest.js

6194 ms

Meta-Yield-Live-Pitching-Competition-Winner-1024x576.png

Meta-Yield-Live-Pitching-Competition-Winner-1024x576.png

277 ms

Meta-Pools-NEARCON-Recap-Day-3-1024x576.png

Meta-Pools-NEARCON-Recap-Day-3-1024x576.png

514 ms

Meta-Pool-First-to-Integrate-Fireblocks-1024x576.png

Meta-Pool-First-to-Integrate-Fireblocks-1024x576.png

515 ms

bg-home-main.svg

bg-home-main.svg

6161 ms

logo.svg

logo.svg

6164 ms

burger.svg

burger.svg

6163 ms

staking-farms-near.svg

staking-farms-near.svg

6164 ms

staking-farms-aurora.svg

staking-farms-aurora.svg

6166 ms

staking-farms-metayield.svg

staking-farms-metayield.svg

6166 ms

staking-farms-metarecipes.svg

staking-farms-metarecipes.svg

6168 ms

trisolaris.svg

trisolaris.svg

6170 ms

refinance.svg

refinance.svg

6172 ms

burrow.svg

burrow.svg

6196 ms

oin.svg

oin.svg

6184 ms

aurigami.svg

aurigami.svg

6198 ms

bastion.svg

bastion.svg

6200 ms

wannaswap.svg

wannaswap.svg

6198 ms

polaris.svg

polaris.svg

6199 ms

bluebit.svg

bluebit.svg

6202 ms

tonic.svg

tonic.svg

6200 ms

benefits-farming.svg

benefits-farming.svg

6210 ms

benefits-borrowing.svg

benefits-borrowing.svg

6212 ms

benefits-lending.svg

benefits-lending.svg

6214 ms

blocksec.svg

blocksec.svg

6218 ms

dragonfly.svg

dragonfly.svg

6228 ms

palmera_crypto.svg

palmera_crypto.svg

6215 ms

iosg_ventures.svg

iosg_ventures.svg

5730 ms

att.svg

att.svg

5731 ms

move.svg

move.svg

5607 ms

inter-all-400-normal.f8403e6f.woff

inter-all-400-normal.f8403e6f.woff

5586 ms

MetaSpace-Regular.woff

MetaSpace-Regular.woff

590 ms

MetaSpace-Light.woff

MetaSpace-Light.woff

520 ms

MetaSpace-Medium.woff

MetaSpace-Medium.woff

518 ms

MetaSpace-Bold.woff

MetaSpace-Bold.woff

424 ms

svc.svg

svc.svg

280 ms

di.svg

di.svg

297 ms

blockwall.svg

blockwall.svg

604 ms

warburg_serres.svg

warburg_serres.svg

602 ms

big_brain_holdings.svg

big_brain_holdings.svg

709 ms

darma.svg

darma.svg

722 ms

staking-farms-bg.svg

staking-farms-bg.svg

902 ms

bg-technology-secure.svg

bg-technology-secure.svg

775 ms

bg-technology-inmediate.svg

bg-technology-inmediate.svg

822 ms

bg-technology-returns.svg

bg-technology-returns.svg

904 ms

bg-security.svg

bg-security.svg

992 ms

bg-comunity.svg

bg-comunity.svg

1015 ms

_error-1995526792b513b2.js

_error-1995526792b513b2.js

1084 ms

Accessibility Review

metapool.app accessibility score

87

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

metapool.app 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

High

Missing source maps for large first-party JavaScript

SEO Factors

metapool.app SEO score

88

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metapool.app 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 Metapool.app 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

metapool.app

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