Tools & Wizards About Us
chri.ca screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

chri.ca

CHRI

Page Load Speed

4.6 sec in total

First Response

136 ms

Resources Loaded

3.9 sec

Page Rendered

605 ms

chri.ca screenshot

About Website

Visit chri.ca now to see the best up-to-date CHRI content for Canada and also check out these interesting facts you probably never knew about chri.ca

CHRI 99.1FM Faith Family Community

Visit chri.ca

Key Findings

We analyzed Chri.ca page load time and found that the first response time was 136 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

chri.ca performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.26

47/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

chri.ca

136 ms

www.chri.ca

249 ms

817 ms

index.php

1470 ms

template.css

126 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 80% of them (67 requests) were addressed to the original Chri.ca, 5% (4 requests) were made to Chriradio.disqus.com and 4% (3 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Chri.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (63%)

Content Size

1.9 MB

After Optimization

701.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chri.ca main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 229.0 kB

  • Original 265.2 kB
  • After minification 202.5 kB
  • After compression 36.2 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 62.7 kB, which is 24% 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 229.0 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 240.9 kB
  • After minification 238.8 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. CHRI images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 791.1 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 389.0 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 791.1 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 163.6 kB

  • Original 201.3 kB
  • After minification 150.9 kB
  • After compression 37.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. Chri.ca needs all CSS files to be minified and compressed as it can save up to 163.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (79%)

Requests Now

78

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chri.ca

chri.ca

136 ms

www.chri.ca

www.chri.ca

249 ms

817 ms

index.php

index.php

1470 ms

template.css

template.css

126 ms

icomoon.css

icomoon.css

129 ms

btcontentslider.css

btcontentslider.css

127 ms

chosen.css

chosen.css

136 ms

finder.css

finder.css

174 ms

addons.css

addons.css

191 ms

template-j30.css

template-j30.css

194 ms

layout.css

layout.css

196 ms

template.css

template.css

226 ms

usertools.css

usertools.css

233 ms

css3.css

css3.css

256 ms

mega.css

mega.css

275 ms

typo.css

typo.css

270 ms

template-j30.css

template-j30.css

297 ms

layout.css

layout.css

294 ms

template.css

template.css

339 ms

modules.css

modules.css

337 ms

layout-extra-wide.css

layout-extra-wide.css

335 ms

css3.css

css3.css

353 ms

mega.css

mega.css

367 ms

mootools-core.js

mootools-core.js

463 ms

core.js

core.js

401 ms

mootools-more.js

mootools-more.js

584 ms

jquery.min.js

jquery.min.js

470 ms

jquery-noconflict.js

jquery-noconflict.js

436 ms

jquery-migrate.min.js

jquery-migrate.min.js

466 ms

main.js

main.js

510 ms

bootstrap.min.js

bootstrap.min.js

529 ms

seobanners.js

seobanners.js

530 ms

core.js

core.js

541 ms

mega.rjd.js

mega.rjd.js

580 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

657 ms

jquery.noconflict.js

jquery.noconflict.js

596 ms

jquery.masonry.js

jquery.masonry.js

600 ms

css

css

14 ms

jquery.mediaqueries.js

jquery.mediaqueries.js

562 ms

mega.js

mega.js

533 ms

slides.js

slides.js

555 ms

default.js

default.js

548 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

587 ms

chosen.jquery.min.js

chosen.jquery.min.js

563 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

542 ms

jslazyloading_v1.4.3.min.js

jslazyloading_v1.4.3.min.js

540 ms

stylesheet.css

stylesheet.css

661 ms

blank.gif

blank.gif

88 ms

analytics.js

analytics.js

62 ms

chri-bg.jpg

chri-bg.jpg

353 ms

arrow.png

arrow.png

82 ms

bullet.png

bullet.png

82 ms

icon-search.png

icon-search.png

195 ms

texgyreadventor-bold-webfont.woff

texgyreadventor-bold-webfont.woff

195 ms

social-bg.png

social-bg.png

180 ms

social-instagram.png

social-instagram.png

179 ms

social-youtube.png

social-youtube.png

180 ms

comment_grey.png

comment_grey.png

232 ms

chri-listen.jpg

chri-listen.jpg

239 ms

chri-donate-bg.jpg

chri-donate-bg.jpg

241 ms

20th-partners.jpg

20th-partners.jpg

357 ms

collect

collect

128 ms

sdk.js

sdk.js

123 ms

embed

embed

1052 ms

count.js

count.js

151 ms

re-left.png

re-left.png

92 ms

re-right.png

re-right.png

146 ms

collect

collect

67 ms

count.js

count.js

46 ms

111 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

20 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

43 ms

count-data.js

count-data.js

3 ms

count-data.js

count-data.js

34 ms

layout-mobile.css

layout-mobile.css

65 ms

layout-mobile-port.css

layout-mobile-port.css

61 ms

layout-tablet.css

layout-tablet.css

61 ms

layout-normal.css

layout-normal.css

62 ms

layout-wide.css

layout-wide.css

61 ms

86bfef538e3f5c2dbae228ac1a980264embedcompiled_fastui.css

86bfef538e3f5c2dbae228ac1a980264embedcompiled_fastui.css

2 ms

rs=ANwU0p5JPs6qSEH6Mqqr_TcQWibRWn_q4A

rs=ANwU0p5JPs6qSEH6Mqqr_TcQWibRWn_q4A

13 ms

client.js

client.js

63 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

Accessibility Review

chri.ca accessibility score

93

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

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

High

Links do not have a discernible name

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

chri.ca best practices score

58

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

Browser errors were logged to the console

SEO Factors

chri.ca SEO score

98

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 Chri.ca 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 Chri.ca 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

chri.ca

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