Tools & Wizards About Us
archtoronto.org screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

archtoronto.org

Archdiocese of Toronto - Archdiocese of Toronto

Page Load Speed

7.8 sec in total

First Response

1.6 sec

Resources Loaded

3.7 sec

Page Rendered

2.4 sec

archtoronto.org screenshot

About Website

Visit archtoronto.org now to see the best up-to-date Arch Toronto content for Canada and also check out these interesting facts you probably never knew about archtoronto.org

Led by Archbishop Francis Leo, the Archdiocese of Toronto is home to Catholics in the Greater Toronto Area

Visit archtoronto.org

Key Findings

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

Performance Metrics

archtoronto.org performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,170 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value27.9 s

0/100

10%

Network Requests Diagram

www.archtoronto.org

1641 ms

bootstrap.min.css

105 ms

kendo.bootstrap-v4.min.css

65 ms

animate.min.css

46 ms

jquery.fancybox.min.css

94 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 64% of them (59 requests) were addressed to the original Archtoronto.org, 15% (14 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Archtoronto.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 501.7 kB (4%)

Content Size

11.8 MB

After Optimization

11.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Archtoronto.org main page is 11.8 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. Only a small number of websites need less resources to load. Images take 9.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 271.7 kB

  • Original 298.9 kB
  • After minification 158.0 kB
  • After compression 27.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 140.8 kB, which is 47% 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 271.7 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 450 B

  • Original 9.3 MB
  • After minification 9.3 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. Arch Toronto images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 211.1 kB

  • Original 2.0 MB
  • After minification 2.0 MB
  • After compression 1.8 MB

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 211.1 kB or 11% of the original size.

CSS Optimization

-7%

Potential reduce by 18.4 kB

  • Original 253.4 kB
  • After minification 253.3 kB
  • After compression 235.0 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. Archtoronto.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (42%)

Requests Now

76

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.archtoronto.org

www.archtoronto.org

1641 ms

bootstrap.min.css

bootstrap.min.css

105 ms

kendo.bootstrap-v4.min.css

kendo.bootstrap-v4.min.css

65 ms

animate.min.css

animate.min.css

46 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

94 ms

style.css

style.css

43 ms

owl.carousel.min.css

owl.carousel.min.css

36 ms

owl.theme.default.min.css

owl.theme.default.min.css

52 ms

tiny-slider.css

tiny-slider.css

51 ms

fade-down.css

fade-down.css

98 ms

menu.css

menu.css

95 ms

white-gry.css

white-gry.css

112 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

174 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

112 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

124 ms

menu.js

menu.js

124 ms

jszip.min.js

jszip.min.js

57 ms

kendo.all.min.js

kendo.all.min.js

122 ms

kendo.aspnetmvc.min.js

kendo.aspnetmvc.min.js

91 ms

all.min.js

all.min.js

141 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

124 ms

owl.carousel.min.js

owl.carousel.min.js

133 ms

tiny-slider.js

tiny-slider.js

89 ms

js

js

111 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

697 ms

global.css

global.css

109 ms

css2

css2

83 ms

archto_header.png

archto_header.png

89 ms

rotator-ontario-cottage.jpg

rotator-ontario-cottage.jpg

88 ms

iec-rotator.jpg

iec-rotator.jpg

90 ms

rotator-chaplaincy1.jpg

rotator-chaplaincy1.jpg

89 ms

sharelife-2024.jpg

sharelife-2024.jpg

87 ms

ordination-cta.jpg

ordination-cta.jpg

86 ms

mothers-day-08.jpg

mothers-day-08.jpg

90 ms

relationships.jpg

relationships.jpg

101 ms

abl042124.png

abl042124.png

95 ms

school-group.jpg

school-group.jpg

91 ms

woman-praying-closed-eyes.png

woman-praying-closed-eyes.png

92 ms

367713116_713045767534538_1441635878616514757_n.jpeg

367713116_713045767534538_1441635878616514757_n.jpeg

164 ms

ordination-thumb.jpg

ordination-thumb.jpg

98 ms

cew2024-thumbnail.jpg

cew2024-thumbnail.jpg

99 ms

ordination-thumbnail.jpg

ordination-thumbnail.jpg

187 ms

year-of-prayer-logo-home.png

year-of-prayer-logo-home.png

149 ms

three-people-sitting-and-reading.jpg

three-people-sitting-and-reading.jpg

150 ms

regis-st.-michaels-faculty-of-theology-logo.jpg

regis-st.-michaels-faculty-of-theology-logo.jpg

151 ms

manresa-jesuit-spiritual-renewal-centre-logo.jpg

manresa-jesuit-spiritual-renewal-centre-logo.jpg

187 ms

white-flowers.jpg

white-flowers.jpg

257 ms

st.-mary-of-egypt-refuge-logo.jpg

st.-mary-of-egypt-refuge-logo.jpg

254 ms

may-25---image-only.jpg

may-25---image-only.jpg

161 ms

our-lady-of-the-cape-pilgrim-statue---cropped.jpg

our-lady-of-the-cape-pilgrim-statue---cropped.jpg

217 ms

blue-flowers.jpg

blue-flowers.jpg

256 ms

volunteer-message-image.png

volunteer-message-image.png

252 ms

jubilee-logo-tile.png

jubilee-logo-tile.png

254 ms

cta-pastoral-letter.jpg

cta-pastoral-letter.jpg

255 ms

cathedral-entering.jpg

cathedral-entering.jpg

578 ms

cta---daily-readings.jpg

cta---daily-readings.jpg

577 ms

parish-vitality-cta.jpg

parish-vitality-cta.jpg

575 ms

fr-eric-mah-cover-photo.png

fr-eric-mah-cover-photo.png

649 ms

cta-euthanasia.jpg

cta-euthanasia.jpg

574 ms

arch_coa.jpg

arch_coa.jpg

577 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

643 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

574 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

1033 ms

archto_footer.png

archto_footer.png

570 ms

ai.0.js

ai.0.js

63 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

118 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff

430 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff

432 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff

497 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

498 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

497 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

496 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff

496 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff

498 ms

wlp2gwHKFkZgtmSR3NB0oRJvaw.woff

wlp2gwHKFkZgtmSR3NB0oRJvaw.woff

500 ms

wlppgwHKFkZgtmSR3NB0oRJXsCx2CA.woff

wlppgwHKFkZgtmSR3NB0oRJXsCx2CA.woff

500 ms

wlppgwHKFkZgtmSR3NB0oRJX1C12CA.woff

wlppgwHKFkZgtmSR3NB0oRJX1C12CA.woff

500 ms

kZAizZ86GjE

kZAizZ86GjE

162 ms

video-leo.jpg

video-leo.jpg

431 ms

include.js

include.js

1005 ms

kZAizZ86GjE

kZAizZ86GjE

315 ms

www-player.css

www-player.css

99 ms

www-embed-player.js

www-embed-player.js

126 ms

base.js

base.js

154 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

307 ms

BotDetectCaptcha.ashx

BotDetectCaptcha.ashx

307 ms

ad_status.js

ad_status.js

164 ms

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

133 ms

embed.js

embed.js

27 ms

id

id

49 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

78 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

77 ms

Accessibility Review

archtoronto.org accessibility score

100

Accessibility Issues

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

archtoronto.org SEO score

78

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

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

archtoronto.org

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