Tools & Wizards About Us
recoveryrecord.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

recoveryrecord.com

Recovery Record - Best Practice for Eating Disorders Treatment

Page Load Speed

621 ms in total

First Response

61 ms

Resources Loaded

273 ms

Page Rendered

287 ms

recoveryrecord.com screenshot

About Website

Click here to check amazing Recovery Record content for Australia. Otherwise, check out these important facts you probably never knew about recoveryrecord.com

Recovery Record is the technology enabled best practice for eating disorder treatment. Trusted by thousands of clinicians. Used by hundreds of thousands of patients

Visit recoveryrecord.com

Key Findings

We analyzed Recoveryrecord.com page load time and found that the first response time was 61 ms and then it took 560 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

recoveryrecord.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.335

34/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

recoveryrecord.com

61 ms

www.recoveryrecord.com

44 ms

container_ZVpjLU0H.js

88 ms

bootstrap.css

43 ms

rrv2.css

48 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 8% of them (4 requests) were addressed to the original Recoveryrecord.com, 72% (38 requests) were made to D3buh2p23rhyze.cloudfront.net and 17% (9 requests) were made to D3e0vp65sneg3n.cloudfront.net. The less responsive or slowest element that took the longest time to load (88 ms) relates to the external source D1pgrzq8alzly7.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.5 kB (12%)

Content Size

859.6 kB

After Optimization

759.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Recoveryrecord.com main page is 859.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. 45% of websites need less resources to load. Images take 750.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 34.5 kB

  • Original 42.8 kB
  • After minification 38.0 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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 11% 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 34.5 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 63.1 kB

  • Original 750.0 kB
  • After minification 686.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. Recovery Record images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 609 B

  • Original 39.9 kB
  • After minification 39.9 kB
  • After compression 39.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

-8%

Potential reduce by 2.3 kB

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 24.6 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. Recoveryrecord.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

49

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

recoveryrecord.com

recoveryrecord.com

61 ms

www.recoveryrecord.com

www.recoveryrecord.com

44 ms

container_ZVpjLU0H.js

container_ZVpjLU0H.js

88 ms

bootstrap.css

bootstrap.css

43 ms

rrv2.css

rrv2.css

48 ms

bootstrap-responsive.css

bootstrap-responsive.css

48 ms

home3.css

home3.css

50 ms

home.css

home.css

7 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

49 ms

bootstrap.min.js

bootstrap.min.js

76 ms

jquery.cookie.js

jquery.cookie.js

47 ms

matomo.js

matomo.js

36 ms

header-logo_v3.png

header-logo_v3.png

35 ms

slider-bg.jpg

slider-bg.jpg

20 ms

vert_line_left.png

vert_line_left.png

17 ms

footer_bg.jpg

footer_bg.jpg

17 ms

mobile3.jpg

mobile3.jpg

20 ms

gray_diag.png

gray_diag.png

19 ms

img_corner.png

img_corner.png

24 ms

tablate3.jpg

tablate3.jpg

24 ms

corner_2.png

corner_2.png

21 ms

app-store.png

app-store.png

22 ms

google-play.png

google-play.png

21 ms

mobile_smallversion3.jpg

mobile_smallversion3.jpg

21 ms

tablate_smallversion.jpg

tablate_smallversion.jpg

22 ms

feature-meal-logs.png

feature-meal-logs.png

24 ms

feature-meal-plan.png

feature-meal-plan.png

22 ms

feature-coping-tactic.png

feature-coping-tactic.png

25 ms

feature-messages.png

feature-messages.png

23 ms

feature_chart.png

feature_chart.png

24 ms

down_big_arrow.png

down_big_arrow.png

23 ms

img6a.png

img6a.png

25 ms

img7a.png

img7a.png

25 ms

img8a.png

img8a.png

25 ms

partner_7.png

partner_7.png

27 ms

partner_5.png

partner_5.png

25 ms

partner_3.png

partner_3.png

25 ms

partner_9.png

partner_9.png

26 ms

partner_1a.png

partner_1a.png

27 ms

partner_2.png

partner_2.png

29 ms

partner_united.png

partner_united.png

28 ms

partner_10.png

partner_10.png

26 ms

partner_6.png

partner_6.png

28 ms

partner_12.png

partner_12.png

29 ms

partner_8.png

partner_8.png

30 ms

couple_mobile3.jpg

couple_mobile3.jpg

31 ms

arr.png

arr.png

30 ms

app_store_2x.png

app_store_2x.png

30 ms

google_play_2x.png

google_play_2x.png

29 ms

clinicans_thumb2.jpg

clinicans_thumb2.jpg

32 ms

facebook.png

facebook.png

30 ms

visitor_redshift_events

visitor_redshift_events

84 ms

twitter.png

twitter.png

21 ms

Accessibility Review

recoveryrecord.com accessibility score

97

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.

Best Practices

recoveryrecord.com best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

recoveryrecord.com SEO score

78

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

High

Tap targets are not sized appropriately

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 Recoveryrecord.com 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 Recoveryrecord.com 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

recoveryrecord.com

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