Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

reaps.org

REAPS | Recycling and Environmental Action Planning Society

Page Load Speed

3.6 sec in total

First Response

767 ms

Resources Loaded

1.8 sec

Page Rendered

1.1 sec

reaps.org screenshot

About Website

Welcome to reaps.org homepage info - get ready to check REAPS best content for Canada right away, or after learning these important things about reaps.org

REAPS (Recycling and Environmental Action Planning Society) fosters environmental stewardship in the Regional District of Fraser-Fort George in British Columbia.

Visit reaps.org

Key Findings

We analyzed Reaps.org page load time and found that the first response time was 767 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

reaps.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

www.reaps.org

767 ms

gtm.js

58 ms

style.min.css

92 ms

style.css

126 ms

reaps-logo.png

42 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 51% of them (22 requests) were addressed to the original Reaps.org, 23% (10 requests) were made to Static.xx.fbcdn.net and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (767 ms) belongs to the original domain Reaps.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.1 kB (22%)

Content Size

1.7 MB

After Optimization

1.3 MB

In fact, the total size of Reaps.org main page is 1.7 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 45.6 kB

  • Original 57.4 kB
  • After minification 53.3 kB
  • After compression 11.8 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 45.6 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 35.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. REAPS images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 5.4 kB

  • Original 68.1 kB
  • After minification 65.8 kB
  • After compression 62.7 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

-86%

Potential reduce by 282.7 kB

  • Original 328.4 kB
  • After minification 325.1 kB
  • After compression 45.7 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. Reaps.org needs all CSS files to be minified and compressed as it can save up to 282.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

26

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

Accessibility Review

reaps.org accessibility score

96

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.

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

<frame> or <iframe> elements do not have a title

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

reaps.org SEO score

89

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

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 Reaps.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 Reaps.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 data is detected on the main page of REAPS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: