Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

restheart.org

RESTHeart - Ready to use backend for the modern Web.

Page Load Speed

583 ms in total

First Response

58 ms

Resources Loaded

408 ms

Page Rendered

117 ms

restheart.org screenshot

About Website

Click here to check amazing RESTHeart content for Turkey. Otherwise, check out these important facts you probably never knew about restheart.org

Low code Microservices Platform with Polyglot Development Framework, Declarative Security and the Best Data APIs for MongoDB

Visit restheart.org

Key Findings

We analyzed Restheart.org page load time and found that the first response time was 58 ms and then it took 525 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

restheart.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value37.3 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

restheart.org

58 ms

bootstrap.min.css

11 ms

css

38 ms

custom-icons.css

18 ms

custom-icons-ie7.css

19 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 32% of them (11 requests) were addressed to the original Restheart.org, 12% (4 requests) were made to Platform.twitter.com and 12% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (328 ms) relates to the external source Sidecar.gitter.im.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.9 kB (64%)

Content Size

434.2 kB

After Optimization

154.4 kB

In fact, the total size of Restheart.org main page is 434.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. 50% of websites need less resources to load. CSS take 228.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 19.8 kB

  • Original 28.0 kB
  • After minification 25.3 kB
  • After compression 8.3 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 19.8 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 3.7 kB

  • Original 71.1 kB
  • After minification 67.4 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. RESTHeart images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 62.7 kB

  • Original 106.5 kB
  • After minification 106.5 kB
  • After compression 43.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 62.7 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 193.7 kB

  • Original 228.6 kB
  • After minification 202.0 kB
  • After compression 34.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. Restheart.org needs all CSS files to be minified and compressed as it can save up to 193.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (64%)

Requests Now

25

After Optimization

9

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

Accessibility Review

restheart.org accessibility score

65

Accessibility Issues

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA toggle fields do not have accessible names

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.

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

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

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

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

restheart.org SEO score

79

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

High

Image elements do not have [alt] attributes

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

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