2.8 sec in total
553 ms
2.1 sec
178 ms
Click here to check amazing RRC content for Canada. Otherwise, check out these important facts you probably never knew about rrc.ca
Visit rrc.caWe analyzed Rrc.ca page load time and found that the first response time was 553 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
rrc.ca performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value4.9 s
28/100
25%
Value3.2 s
92/100
10%
Value1,010 ms
27/100
30%
Value0.022
100/100
15%
Value10.3 s
25/100
10%
553 ms
208 ms
156 ms
313 ms
106 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 37% of them (35 requests) were addressed to the original Rrc.ca, 22% (21 requests) were made to Static.xx.fbcdn.net and 16% (15 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (655 ms) belongs to the original domain Rrc.ca.
Page size can be reduced by 159.4 kB (7%)
2.3 MB
2.1 MB
In fact, the total size of Rrc.ca main page is 2.3 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 25.4 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 25.4 kB or 72% of the original size.
Potential reduce by 58.4 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. RRC images are well optimized though.
Potential reduce by 55.3 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 55.3 kB or 55% of the original size.
Potential reduce by 20.4 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. Rrc.ca needs all CSS files to be minified and compressed as it can save up to 20.4 kB or 82% of the original size.
Number of requests can be reduced by 36 (39%)
92
56
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RRC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
rrc.ca
553 ms
main_redesign.css
208 ms
rrcforms2.css
156 ms
jquery-1.4.2.min.js
313 ms
jquery.backgroundPosition.js
106 ms
jquery.swfobject.1-1-1.min.js
162 ms
twitter-widget-v2.js
205 ms
main-css.v2.css
161 ms
all.js
293 ms
arrowdown.png
78 ms
new-logo.png
78 ms
Open-Cafe-Banner-Rev-3.jpg
427 ms
RRC_Home-Promos_Lrg_BIT---Mar-15-17-Rev_Banner.jpg
392 ms
Synergy_Web_Banner.jpg
356 ms
RRC_General_Info_Session_900_-_20162.jpg
502 ms
Elain_Legasse_Web_Banner.jpg
392 ms
Jane_s-Join-Us-Banner---Spring-Rev.jpg
453 ms
Home_Page_Did_You_Know4.jpg
391 ms
home_promo_right-tax2016b.jpg
452 ms
home_promo_right-ce2016.jpg
450 ms
home_promo_right-inter2016.jpg
451 ms
bottom_footer.png
476 ms
bottom_divider.png
511 ms
ga.js
34 ms
new_gradient.jpg
382 ms
header_red_v2.jpg
504 ms
top-background-slice.jpg
503 ms
submit-button-new.jpg
505 ms
newsarrow.jpg
600 ms
rednews.gif
600 ms
blogroll.gif
600 ms
twitter.gif
599 ms
facebook.gif
600 ms
youtube.gif
599 ms
flickr.png
655 ms
widgets.js
85 ms
bottom_gradient.png
493 ms
bottom_box_bottom_background.png
544 ms
114 ms
user_timeline.json
49 ms
__utm.gif
17 ms
xd_arbiter.php
133 ms
xd_arbiter.php
259 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
126 ms
like_box.php
226 ms
syndication
130 ms
426813755184271361
213 ms
FbUd6dZS1Af.css
164 ms
dGJLq38YL-C.css
239 ms
f7m6HODnCDd.css
267 ms
Msuaq9yC6iC.css
350 ms
i5_N_HL0uEJ.css
342 ms
_rx8naC75Dy.js
376 ms
x5F9OMjKyLw.js
374 ms
ICDbTSzjQEg.js
306 ms
TTCre3391I0.js
305 ms
njO1TPvGzoR.js
356 ms
b_6HNn_J2BZ.js
357 ms
7cm7D75Y0Sf.js
414 ms
rFmE1g6Dkoz.js
495 ms
336JejShbZp.js
393 ms
1f1e8-1f1e6.png
26 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
32 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
94 ms
884929ad2ba3cf6ea396bd6155fec907_normal.png
75 ms
70cd78f4e331ea01237454ad71362777_normal.jpeg
74 ms
a4a0bcacfd141b6b4f81c231f6893221_normal.jpeg
75 ms
mcac_twitter_profile_normal.jpg
75 ms
e915798f09cf9d7b8a2a5d02e8b09340_normal.jpeg
77 ms
6HXSIK-4_normal.jpeg
76 ms
CcawxmyUUAALFgp.jpg:small
77 ms
CcaUQO4VIAA7NUQ.jpg:small
81 ms
CcZvNxaUYAA6DFK.jpg:small
81 ms
CcZTJwRUYAAgLX-.jpg:small
79 ms
CcUgACAUUAAEI6U.jpg:small
82 ms
CcUTJrCUYAA8-fk.jpg:small
82 ms
CcTXQ3yUYAEXr_1.jpg:small
83 ms
CcRhMqbWIAABWmL.jpg:small
83 ms
CcPNj8aXEAEkvYm.jpg:small
84 ms
jot
27 ms
1505995_10152770221553503_7400215490183061548_n.jpg
202 ms
safe_image.php
177 ms
safe_image.php
210 ms
safe_image.php
249 ms
safe_image.php
321 ms
1422467_10151921266733503_902487304_n.png
231 ms
12801134_10153888527813503_6520590694641246294_n.jpg
306 ms
HEyyDkPknAC.png
55 ms
wL6VQj7Ab77.png
55 ms
s7jcwEQH7Sx.png
55 ms
QDwYpIaRyfG.png
54 ms
a-ZN6WoEOje.png
53 ms
I6-MnjEovm5.js
38 ms
vlXaquuXMrr.js
40 ms
rrc.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
rrc.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
rrc.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rrc.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 Rrc.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.
rrc.ca
Open Graph description is not detected on the main page of RRC. 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: