Tools & Wizards About Us
christourking.ca screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

christourking.ca

Christ our King Lutheran Church Mississauga

Page Load Speed

844 ms in total

First Response

90 ms

Resources Loaded

668 ms

Page Rendered

86 ms

christourking.ca screenshot

About Website

Click here to check amazing Christ Our King content. Otherwise, check out these important facts you probably never knew about christourking.ca

We are a member congregation of Lutheran Church-Canada (LCC). LCC is a partner church of The Lutheran Church Missouri Synod (LCMS).

Visit christourking.ca

Key Findings

We analyzed Christourking.ca page load time and found that the first response time was 90 ms and then it took 754 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

christourking.ca performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value8,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

Network Requests Diagram

www.christourking.ca

90 ms

minified.js

38 ms

focus-within-polyfill.js

38 ms

polyfill.min.js

74 ms

thunderbolt-commons.b70ee867.bundle.min.js

107 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Christourking.ca, 47% (15 requests) were made to Static.parastorage.com and 34% (11 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (321 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 615.4 kB (59%)

Content Size

1.0 MB

After Optimization

421.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Christourking.ca 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. 45% of websites need less resources to load. HTML takes 707.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 556.9 kB

  • Original 707.0 kB
  • After minification 705.2 kB
  • After compression 150.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 556.9 kB or 79% of the original size.

Image Optimization

-33%

Potential reduce by 7.7 kB

  • Original 23.3 kB
  • After minification 15.6 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, Christ Our King needs image optimization as it can save up to 7.7 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 50.7 kB

  • Original 306.9 kB
  • After minification 306.9 kB
  • After compression 256.2 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 50.7 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.christourking.ca

www.christourking.ca

90 ms

minified.js

minified.js

38 ms

focus-within-polyfill.js

focus-within-polyfill.js

38 ms

polyfill.min.js

polyfill.min.js

74 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

107 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

108 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

105 ms

lodash.min.js

lodash.min.js

128 ms

react.production.min.js

react.production.min.js

108 ms

react-dom.production.min.js

react-dom.production.min.js

116 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

107 ms

18ba17_2fb5ed7ce1764ceabdef53a582ddc039~mv2.png

18ba17_2fb5ed7ce1764ceabdef53a582ddc039~mv2.png

321 ms

bundle.min.js

bundle.min.js

63 ms

Picture1.png

Picture1.png

236 ms

118 ms

111 ms

110 ms

110 ms

103 ms

103 ms

145 ms

142 ms

138 ms

137 ms

137 ms

deprecation-en.v5.html

deprecation-en.v5.html

9 ms

bolt-performance

bolt-performance

48 ms

deprecation-style.v5.css

deprecation-style.v5.css

10 ms

right-arrow.svg

right-arrow.svg

10 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

18 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

17 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

18 ms

Accessibility Review

christourking.ca accessibility score

96

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

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

christourking.ca SEO score

92

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

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

christourking.ca

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