Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

btr.org

BTR.ORG - Make Your Way to Safety & Peace

Page Load Speed

2.2 sec in total

First Response

299 ms

Resources Loaded

1.4 sec

Page Rendered

523 ms

btr.org screenshot

About Website

Welcome to btr.org homepage info - get ready to check BTR best content for United States right away, or after learning these important things about btr.org

At Betrayal Trauma Recovery, you’ll never be blamed for the emotional or psychological abuse you suffered due to your husband's porn use and infidelity.

Visit btr.org

Key Findings

We analyzed Btr.org page load time and found that the first response time was 299 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

btr.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value2,660 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.197

63/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

btr.org

299 ms

www.btr.org

182 ms

style.min.css

23 ms

style.min.css

40 ms

carousel.min.css

38 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 73% of them (54 requests) were addressed to the original Btr.org, 8% (6 requests) were made to Player.vimeo.com and 5% (4 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (476 ms) relates to the external source Web-sdk.smartlook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.8 kB (27%)

Content Size

802.8 kB

After Optimization

583.9 kB

In fact, the total size of Btr.org main page is 802.8 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 601.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 148.9 kB

  • Original 177.9 kB
  • After minification 173.3 kB
  • After compression 29.0 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 148.9 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 69.8 kB

  • Original 601.9 kB
  • After minification 532.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. Obviously, BTR needs image optimization as it can save up to 69.8 kB or 12% 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 50 B

  • Original 23.0 kB
  • After minification 23.0 kB
  • After compression 22.9 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.

Requests Breakdown

Number of requests can be reduced by 35 (54%)

Requests Now

65

After Optimization

30

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BTR. 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 from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

btr.org accessibility score

70

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

btr.org best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

btr.org SEO score

97

Search Engine Optimization Advices

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 Btr.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 Btr.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 BTR. 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: