16.9 sec in total
7.1 sec
9.4 sec
353 ms
Welcome to chapelofgrace.ca homepage info - get ready to check Chapel Of Grace best content right away, or after learning these important things about chapelofgrace.ca
Visit chapelofgrace.caWe analyzed Chapelofgrace.ca page load time and found that the first response time was 7.1 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
chapelofgrace.ca performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value8.5 s
2/100
25%
Value10.0 s
9/100
10%
Value2,090 ms
7/100
30%
Value0.016
100/100
15%
Value16.7 s
5/100
10%
7131 ms
84 ms
109 ms
96 ms
75 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 44% of them (56 requests) were addressed to the original Chapelofgrace.ca, 18% (23 requests) were made to Maps.googleapis.com and 13% (17 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Chapelofgrace.ca.
Page size can be reduced by 1.2 MB (65%)
1.8 MB
639.9 kB
In fact, the total size of Chapelofgrace.ca main page is 1.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. 80% 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 73.6 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 73.6 kB or 80% of the original size.
Potential reduce by 10.0 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. Chapel Of Grace images are well optimized though.
Potential reduce by 735.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 735.0 kB or 68% of the original size.
Potential reduce by 375.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. Chapelofgrace.ca needs all CSS files to be minified and compressed as it can save up to 375.2 kB or 84% of the original size.
Number of requests can be reduced by 82 (67%)
122
40
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chapel Of Grace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
chapelofgrace.ca
7131 ms
wp-emoji-release.min.js
84 ms
flashblock.css
109 ms
player.css
96 ms
style.css
75 ms
style.css
130 ms
jquery-ui-1.9.2.custom.min.css
188 ms
squelch-tabs-and-accordions.css
166 ms
tipsy.css
130 ms
wp-shortcode.css
136 ms
ytprefs.min.css
158 ms
fontfaces.css
218 ms
style.css
205 ms
wen-style.css
171 ms
soundmanager2-nodebug-jsmin.js
280 ms
jquery.js
403 ms
jquery-migrate.min.js
325 ms
js-map.min.js
266 ms
jquery.tipsy.js
265 ms
wp-shortcode.js
251 ms
ytprefs.min.js
331 ms
style-frontpage.css
355 ms
style-mobile.css
329 ms
mediaelementplayer.min.css
334 ms
wp-mediaelement.css
376 ms
front.css
387 ms
ajax.js
394 ms
custom.js
380 ms
play_gif.js
457 ms
spin.js
457 ms
jquery.spin.js
483 ms
frontend.js
457 ms
nivo.slider.min.js
457 ms
core.min.js
465 ms
widget.min.js
486 ms
accordion.min.js
486 ms
tabs.min.js
487 ms
squelch-tabs-and-accordions.js
468 ms
fitvids.min.js
449 ms
wp-embed.min.js
448 ms
mediaelement-and-player.min.js
506 ms
wp-mediaelement.js
416 ms
iframe_api
38 ms
intro_rccg.gif
1837 ms
Facebook.png
152 ms
Twitter.png
152 ms
RSS.png
154 ms
cropped-NEW-RCCG-LOGO-BLACK1.gif
389 ms
ottawa-night-4-e1422285547904.jpg
1283 ms
cropped-Amaziing-grace-dove.jpg
411 ms
pzml_vFBYQY
119 ms
sourcesanspro-regular-webfont.woff
328 ms
sourcesanspro-light-webfont.woff
329 ms
sourcesanspro-extralight-webfont.woff
330 ms
sourcesanspro-semibold-webfont.woff
546 ms
sourcesanspro-bold-webfont.woff
546 ms
elusive.woff
398 ms
sdk.js
91 ms
www-widgetapi.js
27 ms
mOKTkigOsT0
79 ms
loading.gif
395 ms
fn4lmq4vJoM
62 ms
www-embed-player-vflfNyN_r.css
45 ms
www-embed-player.js
248 ms
base.js
330 ms
479 ms
xd_arbiter.php
274 ms
xd_arbiter.php
478 ms
js
318 ms
arrows.png
99 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
104 ms
ad_status.js
103 ms
post.php
379 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
63 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
common.js
17 ms
util.js
36 ms
geocoder.js
53 ms
AuthenticationService.Authenticate
65 ms
GeocodeService.Search
66 ms
map.js
6 ms
marker.js
37 ms
StaticMapService.GetMapImage
127 ms
onion.js
21 ms
openhand_8_8.cur
101 ms
ViewportInfoService.GetViewportInfo
90 ms
stats.js
20 ms
controls.js
21 ms
css
142 ms
transparent.png
77 ms
spotlight-poi.png
78 ms
google4.png
88 ms
mapcnt6.png
88 ms
sv5.png
76 ms
tmapctrl.png
85 ms
cb_scout5.png
95 ms
tmapctrl4.png
95 ms
vt
65 ms
vt
60 ms
vt
50 ms
vt
61 ms
vt
95 ms
vt
59 ms
vt
96 ms
vt
95 ms
vt
97 ms
vt
95 ms
kyEKgjk51ZE.css
102 ms
Czh0gDTFcBt.css
140 ms
DY6CRC1i1Bl.css
181 ms
xgj7bXhJNEH.css
155 ms
N-k91nHCZS2.css
172 ms
q68gy-v_YMF.js
203 ms
FJmpeSpHpjS.js
231 ms
0wM5s1Khldu.js
160 ms
1QuX41zDRrx.js
200 ms
Oagsvfb4VWi.js
250 ms
LTv6ZK-5zxz.js
256 ms
1FCa-btixu2.js
254 ms
njO1TPvGzoR.js
248 ms
1bNoFZUdlYZ.js
254 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
6 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
11 ms
270325_10150179533267614_1760112_n.jpg
89 ms
QDwYpIaRyfG.png
46 ms
I6-MnjEovm5.js
18 ms
pQrUxxo5oQp.js
36 ms
chapelofgrace.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
chapelofgrace.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
chapelofgrace.ca SEO score
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 Chapelofgrace.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 Chapelofgrace.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.
chapelofgrace.ca
Open Graph description is not detected on the main page of Chapel Of Grace. 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: