6.6 sec in total
1.4 sec
4 sec
1.2 sec
Click here to check amazing Sorrows content. Otherwise, check out these important facts you probably never knew about sorrows.ca
Our Lady of Sorrows is a Roman Catholic church located in the neighbourhood of The Kingsway in the City of Toronto.
Visit sorrows.caWe analyzed Sorrows.ca page load time and found that the first response time was 1.4 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sorrows.ca performance score
name
value
score
weighting
Value14.7 s
0/100
10%
Value20.9 s
0/100
25%
Value14.8 s
1/100
10%
Value1,860 ms
9/100
30%
Value0.019
100/100
15%
Value26.7 s
0/100
10%
1360 ms
80 ms
55 ms
123 ms
86 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sorrows.ca, 9% (6 requests) were made to Youtube.com and 6% (4 requests) were made to Kendo.cdn.telerik.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Olsorrowset.archtoronto.org.
Page size can be reduced by 420.0 kB (5%)
8.9 MB
8.5 MB
In fact, the total size of Sorrows.ca main page is 8.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 114.7 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 44.0 kB, which is 34% 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 114.7 kB or 88% of the original size.
Potential reduce by 92.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. Sorrows images are well optimized though.
Potential reduce by 181.4 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.
Potential reduce by 31.2 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. Sorrows.ca needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 11% of the original size.
Number of requests can be reduced by 32 (52%)
62
30
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sorrows. 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.
olsorrowset.archtoronto.org
1360 ms
bootstrap.min.css
80 ms
kendo.bootstrap-v4.min.css
55 ms
animate.min.css
123 ms
jquery.fancybox.min.css
86 ms
style.css
111 ms
owl.carousel.min.css
46 ms
owl.theme.default.min.css
95 ms
tiny-slider.css
73 ms
fade-down.css
153 ms
menu.css
135 ms
white-gry.css
145 ms
BotDetectCaptcha.ashx
162 ms
jquery-3.4.1.min.js
268 ms
bootstrap.bundle.min.js
196 ms
menu.js
150 ms
jszip.min.js
44 ms
kendo.all.min.js
74 ms
kendo.aspnetmvc.min.js
38 ms
all.min.js
515 ms
jquery.fancybox.min.js
197 ms
owl.carousel.min.js
169 ms
tiny-slider.js
50 ms
js
87 ms
BotDetectCaptcha.ashx
204 ms
global.css
76 ms
css2
29 ms
preist-collar.jpg
110 ms
cccb-blue-logo.png
135 ms
hispanic-priests-rollup.jpg
174 ms
lourdes-thumbnail.jpg
248 ms
lent-2024---purple-banner.jpg
53 ms
copy-of-gallup-survey.jpg
248 ms
family.jpg
250 ms
volunteer-hands-cropped.jpg
249 ms
senior-wellness-workshop.jpg
246 ms
color-youtube-96.png
93 ms
christian-buehner-k8xjppheo7m-unsplash.jpg
353 ms
cookie-the-pom-gysmaocsdqs-unsplash.jpg
324 ms
mass-card.jpg
785 ms
childrens-liturgy.jpg
326 ms
childrens-choir.jpg
490 ms
kids-movie.jpg
325 ms
monstrance.jpg
843 ms
BotDetectCaptcha.ashx
390 ms
BotDetectCaptcha.ashx
444 ms
BotDetectCaptcha.ashx
443 ms
archto_footer.png
673 ms
ai.0.js
57 ms
font
157 ms
font
231 ms
Cby5BCMCM3E
47 ms
olsorrowset.archtoronto.org
1604 ms
include.js
756 ms
Cby5BCMCM3E
195 ms
BotDetectCaptcha.ashx
1693 ms
BotDetectCaptcha.ashx
1706 ms
www-player.css
37 ms
www-embed-player.js
58 ms
base.js
103 ms
ad_status.js
225 ms
0aSJtfNM8L01cWWskGjXioqOcJ1ilFvu_B1Mexo0pyY.js
133 ms
embed.js
71 ms
id
15 ms
Create
22 ms
GenerateIT
21 ms
sorrows.ca accessibility score
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
Buttons do not have an accessible name
sorrows.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
sorrows.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sorrows.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 Sorrows.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.
sorrows.ca
Open Graph description is not detected on the main page of Sorrows. 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: