Tools & Wizards About Us
bean.money screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

bean.money

Beanstalk | A permissionless fiat stablecoin protocol

Page Load Speed

1.6 sec in total

First Response

93 ms

Resources Loaded

1.3 sec

Page Rendered

183 ms

bean.money screenshot

About Website

Click here to check amazing Bean content for Singapore. Otherwise, check out these important facts you probably never knew about bean.money

Beanstalk is a permissionless fiat stablecoin protocol built on Ethereum that uses credit instead of collateral to issue its native stablecoin.

Visit bean.money

Key Findings

We analyzed Bean.money page load time and found that the first response time was 93 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

bean.money performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value3,390 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

bean.money

93 ms

gtm.js

54 ms

a500431e6fee7e86.css

50 ms

af8ebfa3df151a54.css

159 ms

polyfills-5cd94c89d3acac5f.js

506 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 60% of them (25 requests) were addressed to the original Bean.money, 12% (5 requests) were made to Youtube.com and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (561 ms) belongs to the original domain Bean.money.

Page Optimization Overview & Recommendations

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

Content Size

627.6 kB

After Optimization

595.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bean.money main page is 627.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. 55% of websites need less resources to load. Javascripts take 290.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.0 kB

  • Original 13.0 kB
  • After minification 12.8 kB
  • After compression 3.1 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 10.0 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 19.2 kB

  • Original 264.8 kB
  • After minification 245.6 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. Bean images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 290.9 kB
  • After minification 290.9 kB
  • After compression 288.3 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

-0%

Potential reduce by 0 B

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 58.9 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. Bean.money has all CSS files already compressed.

Requests Breakdown

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

Requests Now

37

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bean.money

bean.money

93 ms

gtm.js

gtm.js

54 ms

a500431e6fee7e86.css

a500431e6fee7e86.css

50 ms

af8ebfa3df151a54.css

af8ebfa3df151a54.css

159 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

506 ms

webpack-9b312e20a4e32339.js

webpack-9b312e20a4e32339.js

226 ms

framework-91d7f78b5b4003c8.js

framework-91d7f78b5b4003c8.js

112 ms

main-7f8acbe569c9ddeb.js

main-7f8acbe569c9ddeb.js

83 ms

_app-f5db14abff66116b.js

_app-f5db14abff66116b.js

112 ms

918-409673f92f5be0d5.js

918-409673f92f5be0d5.js

147 ms

index-bb7f27fdacdccd69.js

index-bb7f27fdacdccd69.js

226 ms

_buildManifest.js

_buildManifest.js

225 ms

_ssgManifest.js

_ssgManifest.js

227 ms

_middlewareManifest.js

_middlewareManifest.js

561 ms

eH1j8hu1BbQ

eH1j8hu1BbQ

107 ms

logo.svg

logo.svg

561 ms

beanstalk-white.svg

beanstalk-white.svg

498 ms

beanstalk.svg

beanstalk.svg

495 ms

gitbook.png

gitbook.png

497 ms

discord.png

discord.png

499 ms

snapshot.svg

snapshot.svg

500 ms

basin.svg

basin.svg

555 ms

immunefi.png

immunefi.png

557 ms

github.png

github.png

558 ms

js

js

63 ms

analytics.js

analytics.js

122 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

86 ms

base.js

base.js

120 ms

background-spring.png

background-spring.png

444 ms

collect

collect

107 ms

ad_status.js

ad_status.js

202 ms

FuturaPTMedium.otf

FuturaPTMedium.otf

194 ms

FuturaPTBold.otf

FuturaPTBold.otf

241 ms

collect

collect

248 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

170 ms

embed.js

embed.js

29 ms

id

id

58 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

219 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

222 ms

ga-audiences

ga-audiences

166 ms

Create

Create

158 ms

Accessibility Review

bean.money accessibility score

81

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

High

Links do not have a discernible name

Best Practices

bean.money 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

Page has valid source maps

SEO Factors

bean.money 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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bean.money can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Bean.money 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

bean.money

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