Tools & Wizards About Us
reserve.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

reserve.org

Reserve | Stable currency, a human right

Page Load Speed

905 ms in total

First Response

37 ms

Resources Loaded

811 ms

Page Rendered

57 ms

reserve.org screenshot

About Website

Click here to check amazing Reserve content for Venezuela. Otherwise, check out these important facts you probably never knew about reserve.org

Reserve is building technology for Decentralized Token Folios (DTFs)—permissionless, tokenized indexes that create a more accessible financial system.

Visit reserve.org

Key Findings

We analyzed Reserve.org page load time and found that the first response time was 37 ms and then it took 868 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

reserve.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

reserve.org

37 ms

reserve.org

69 ms

style.min.css

23 ms

jquery_3.6.4.min.js

37 ms

lottie.js

58 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 80% of them (83 requests) were addressed to the original Reserve.org, 13% (14 requests) were made to Unpkg.com and 5% (5 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (217 ms) belongs to the original domain Reserve.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 339.5 kB (14%)

Content Size

2.4 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Reserve.org main page is 2.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. Only a small number of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 266.3 kB

  • Original 300.0 kB
  • After minification 227.0 kB
  • After compression 33.7 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. This page needs HTML code to be minified as it can gain 73.0 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 266.3 kB or 89% of the original size.

Image Optimization

-16%

Potential reduce by 72.5 kB

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

JavaScript Optimization

-0%

Potential reduce by 736 B

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.6 MB

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.

Requests Breakdown

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

Requests Now

91

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

reserve.org

reserve.org

37 ms

reserve.org

reserve.org

69 ms

style.min.css

style.min.css

23 ms

jquery_3.6.4.min.js

jquery_3.6.4.min.js

37 ms

lottie.js

lottie.js

58 ms

toc.js

toc.js

69 ms

search.js

search.js

55 ms

sanitizer-polyfill.min.js

sanitizer-polyfill.min.js

45 ms

mark.min.js

mark.min.js

50 ms

minisearch5.0.0.min.js

minisearch5.0.0.min.js

66 ms

lunr.js

lunr.js

68 ms

micromodal.min.js

micromodal.min.js

69 ms

luxon.min.js

luxon.min.js

98 ms

anchor.js

anchor.js

96 ms

noframework.waypoints.min.js

noframework.waypoints.min.js

97 ms

slick.css

slick.css

32 ms

slick-theme.css

slick-theme.css

43 ms

babel.min.js

babel.min.js

97 ms

react.production.min.js

react.production.min.js

97 ms

react-dom.production.min.js

react-dom.production.min.js

66 ms

prop-types.min.js

prop-types.min.js

148 ms

Recharts.js

Recharts.js

68 ms

rtokens.js

rtokens.js

95 ms

desktop_hero.js

desktop_hero.js

96 ms

mobile_hero.js

mobile_hero.js

95 ms

dax_graphic.js

dax_graphic.js

114 ms

rtoken_carousel.js

rtoken_carousel.js

156 ms

slick.min.js

slick.min.js

39 ms

safeAssets.js

safeAssets.js

100 ms

gtm.js

gtm.js

75 ms

fbevents.js

fbevents.js

41 ms

core@2.11.8

core@2.11.8

62 ms

tippy.js@6.3.7

tippy.js@6.3.7

54 ms

react-dom.production.min.js

react-dom.production.min.js

33 ms

Recharts.js

Recharts.js

34 ms

popper.min.js

popper.min.js

31 ms

babel.min.js

babel.min.js

113 ms

react.production.min.js

react.production.min.js

19 ms

tippy-bundle.umd.min.js

tippy-bundle.umd.min.js

16 ms

prop-types.min.js

prop-types.min.js

13 ms

reserve_offwhite.svg

reserve_offwhite.svg

36 ms

mobile_menu.svg

mobile_menu.svg

35 ms

open_link.svg

open_link.svg

36 ms

new-hero-main.webp

new-hero-main.webp

37 ms

Mural_mobile.webp

Mural_mobile.webp

199 ms

btn_arrow_play_blue.svg

btn_arrow_play_blue.svg

36 ms

r-token.png

r-token.png

38 ms

tree.png

tree.png

197 ms

wheat.png

wheat.png

198 ms

roots.png

roots.png

200 ms

spider.png

spider.png

201 ms

open_link_black.svg

open_link_black.svg

200 ms

safe-assets-icon.png

safe-assets-icon.png

201 ms

disclaimer.png

disclaimer.png

202 ms

measuring-compass.png

measuring-compass.png

206 ms

Auditor_ackee.png

Auditor_ackee.png

204 ms

btn_arrow.svg

btn_arrow.svg

204 ms

btn_arrow_blue.svg

btn_arrow_blue.svg

203 ms

Auditor_solidified.png

Auditor_solidified.png

208 ms

Auditor_trail_of_bits.png

Auditor_trail_of_bits.png

206 ms

Auditor_halborn.png

Auditor_halborn.png

205 ms

Auditor_code4rena.png

Auditor_code4rena.png

208 ms

Auditor_trust.png

Auditor_trust.png

206 ms

rtoken-primer-icon.png

rtoken-primer-icon.png

209 ms

RToken_1.webp

RToken_1.webp

210 ms

RToken_2.webp

RToken_2.webp

208 ms

RToken_3.webp

RToken_3.webp

211 ms

RToken_4.webp

RToken_4.webp

210 ms

RToken_5.webp

RToken_5.webp

212 ms

RToken_6.webp

RToken_6.webp

213 ms

faq-icon.png

faq-icon.png

212 ms

arrow-accordion.svg

arrow-accordion.svg

211 ms

faq-graphic.png

faq-graphic.png

215 ms

reserve_blue.svg

reserve_blue.svg

213 ms

open_link_external_blue.svg

open_link_external_blue.svg

215 ms

curve.png

curve.png

217 ms

footer_arrow_black.svg

footer_arrow_black.svg

184 ms

bigone.png

bigone.png

184 ms

huobi.png

huobi.png

185 ms

binance.png

binance.png

183 ms

KCS_Green.png

KCS_Green.png

183 ms

footer_open_link_external.svg

footer_open_link_external.svg

99 ms

register.png

register.png

99 ms

uglycash.png

uglycash.png

101 ms

sentz.png

sentz.png

99 ms

job-emoji1.png

job-emoji1.png

99 ms

reserve.png

reserve.png

97 ms

tally.png

tally.png

98 ms

discourse.png

discourse.png

98 ms

discord.png

discord.png

99 ms

twtr.png

twtr.png

97 ms

docs.png

docs.png

95 ms

github.png

github.png

97 ms

email.png

email.png

98 ms

up_arrow.svg

up_arrow.svg

161 ms

close_cross.svg

close_cross.svg

94 ms

mobile_menu_blue.svg

mobile_menu_blue.svg

144 ms

4swap.png

4swap.png

177 ms

eco_item_close.svg

eco_item_close.svg

175 ms

TWKLausanne-300.ttf

TWKLausanne-300.ttf

85 ms

TWKLausanne-500.ttf

TWKLausanne-500.ttf

83 ms

TWKLausanne-700.ttf

TWKLausanne-700.ttf

85 ms

ajax-loader.gif

ajax-loader.gif

69 ms

slick.woff

slick.woff

9 ms

Accessibility Review

reserve.org 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.

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

Links do not have a discernible name

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

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

reserve.org 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

reserve.org 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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Reserve.org 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 Reserve.org 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

reserve.org

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