Tools & Wizards About Us
oar2.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

oar2.org

OA REGION 2 - Region 2 of Overeaters Anonymous serves California, Hawaii, Mexico and Northern Nevada

Page Load Speed

1.5 sec in total

First Response

121 ms

Resources Loaded

1.2 sec

Page Rendered

189 ms

oar2.org screenshot

About Website

Click here to check amazing OA R2 content. Otherwise, check out these important facts you probably never knew about oar2.org

Region 2 serves California, Hawaii, Mexico and Northern Nevada exists to support individuals in need of recovery from compulsive eating (e.g. overeating, bulimia, anorexia) through empowering all grou...

Visit oar2.org

Key Findings

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

oar2.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

oar2.org

121 ms

www.oar2.org

395 ms

www.oar2.org

254 ms

js

73 ms

sites.css

34 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 24% of them (12 requests) were addressed to the original Oar2.org, 67% (34 requests) were made to Cdn2.editmysite.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (395 ms) belongs to the original domain Oar2.org.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

885.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oar2.org main page is 1.0 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. 60% of websites need less resources to load. Javascripts take 548.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 104.4 kB

  • Original 125.5 kB
  • After minification 123.2 kB
  • After compression 21.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 104.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 345 B

  • Original 305.4 kB
  • After minification 305.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. OA R2 images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 40.0 kB

  • Original 548.6 kB
  • After minification 548.6 kB
  • After compression 508.6 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

-2%

Potential reduce by 853 B

  • Original 51.8 kB
  • After minification 51.8 kB
  • After compression 50.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. Oar2.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (77%)

Requests Now

35

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oar2.org

oar2.org

121 ms

www.oar2.org

www.oar2.org

395 ms

www.oar2.org

www.oar2.org

254 ms

js

js

73 ms

sites.css

sites.css

34 ms

fancybox.css

fancybox.css

31 ms

social-icons.css

social-icons.css

41 ms

main_style.css

main_style.css

109 ms

font.css

font.css

33 ms

font.css

font.css

31 ms

font.css

font.css

31 ms

font.css

font.css

42 ms

font.css

font.css

42 ms

font.css

font.css

41 ms

font.css

font.css

48 ms

site_membership.css

site_membership.css

45 ms

templateArtifacts.js

templateArtifacts.js

118 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

47 ms

stl.js

stl.js

47 ms

main.js

main.js

47 ms

main-membership-site.js

main-membership-site.js

47 ms

commerce-core.js

commerce-core.js

48 ms

main-commerce-browse.js

main-commerce-browse.js

48 ms

mobile.js

mobile.js

195 ms

plugins.js

plugins.js

197 ms

custom.js

custom.js

195 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

51 ms

powr.js

powr.js

46 ms

53 ms

Morning-Breeze.jpg

Morning-Breeze.jpg

73 ms

transparent-logo.png

transparent-logo.png

146 ms

search.svg

search.svg

166 ms

2024-11-20-chairchat_orig.jpg

2024-11-20-chairchat_orig.jpg

144 ms

original-logo-symbol.png

original-logo-symbol.png

145 ms

regular.woff

regular.woff

69 ms

light.woff

light.woff

69 ms

bold.woff

bold.woff

69 ms

app.js

app.js

168 ms

ga.js

ga.js

128 ms

snowday262.js

snowday262.js

102 ms

regular.woff

regular.woff

23 ms

regular.woff

regular.woff

22 ms

light.woff

light.woff

22 ms

bold.woff

bold.woff

23 ms

bold.woff

bold.woff

22 ms

regular.woff

regular.woff

22 ms

light.woff

light.woff

27 ms

regular.ttf

regular.ttf

26 ms

wsocial.svg

wsocial.svg

26 ms

wsocial.woff

wsocial.woff

25 ms

wsocial.woff

wsocial.woff

25 ms

Accessibility Review

oar2.org accessibility score

98

Accessibility Issues

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

oar2.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

oar2.org SEO score

91

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

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

oar2.org

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