1.7 sec in total
90 ms
1.4 sec
283 ms
Visit rogers.ca now to see the best up-to-date Rogers content for Canada and also check out these interesting facts you probably never knew about rogers.ca
Choose from a Wireless Device or Plan that’s right for you! At Rogers we offer various Internet, TV, Home Monitoring, and Home Phone options!
Visit rogers.caWe analyzed Rogers.ca page load time and found that the first response time was 90 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
rogers.ca performance score
90 ms
138 ms
134 ms
110 ms
17 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rogers.ca, 56% (53 requests) were made to Rogers.com and 9% (9 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (307 ms) relates to the external source Rogers.com.
Page size can be reduced by 985.5 kB (49%)
2.0 MB
1.0 MB
In fact, the total size of Rogers.ca main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 40.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. 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 40.7 kB or 75% of the original size.
Potential reduce by 10.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. Rogers images are well optimized though.
Potential reduce by 712.8 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 712.8 kB or 68% of the original size.
Potential reduce by 221.5 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. Rogers.ca needs all CSS files to be minified and compressed as it can save up to 221.5 kB or 84% of the original size.
Number of requests can be reduced by 44 (49%)
90
46
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rogers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
rogers.ca
90 ms
home
138 ms
bootstrap.min.css
134 ms
rui.css
110 ms
rui-typeahead.css
17 ms
rui-modal.css
108 ms
jquery.owl-carousel.css
14 ms
rui-icons.css
111 ms
avenir-next.css
15 ms
satelliteLib-0a2a8ad216e0bf155d349e01be2597c718e73e98.js
150 ms
s_code.js
15 ms
aes.js
17 ms
bold-chat-integration.js
20 ms
rogers.css
27 ms
cms.css
27 ms
homepage-banner.css
32 ms
jquery2.min.js
33 ms
bootstrap.min.js
38 ms
jquery-migrate-1.2.1.min.js
39 ms
rui.js
78 ms
jquery.print.js
48 ms
jquery.owl-carousel.min.js
54 ms
rui-typeahead.js
60 ms
endeca-typeahead-global.js
69 ms
SSOChat.js
77 ms
tealeaf.js
83 ms
homepage-banner.js
83 ms
id
8 ms
mbox-contents-228ba194bbc39b298783d5e563e8a3dd7b6faa96.js
79 ms
id
44 ms
target.js
80 ms
ajax
36 ms
RogersCommunications.js
175 ms
gateway.min.js
95 ms
msie.png
77 ms
firefox.png
66 ms
chrome.png
307 ms
safari.png
64 ms
opera.png
76 ms
logo-inverted.png
66 ms
whats-new-s7.png
68 ms
whats-new-crosell-v2.png
67 ms
whats-new-internet-5.png
66 ms
home-banner-M4-mobile.jpg
69 ms
home-banner-M4-left.png
68 ms
home-banner-new-way-mobile.png
70 ms
home-banner-slot2-new-way.png
71 ms
bottom-banner-mobile.jpg
72 ms
home-banner-slotleft-gcl.png
71 ms
bg-login-banner.png
72 ms
widget-loader-lg.gif
73 ms
satellite-56449f2764746d10bb007ea5.html
76 ms
satellite-5654b6a364746d4382000348.html
68 ms
satellite-5654b6a364746d438200034a.html
69 ms
satellite-5654b6a364746d438200034b.html
162 ms
satellite-5654b6a364746d438200034c.html
75 ms
satellite-56b119db64746d0a7c002d1d.html
76 ms
satellite-5579e57b6266380017ce0400.html
163 ms
conversion.js
53 ms
ga.js
61 ms
avenir-next-light.woff
61 ms
avenir-next-regular.woff
49 ms
avenir-next-medium.woff
53 ms
avenir-next-demi.woff
47 ms
rui-icon.woff
61 ms
avenir-next-medium-italic.woff
54 ms
avenir-next-regular-italic.woff
53 ms
avenir-next-light-italic.woff
61 ms
avenir-next-demi-italic.woff
53 ms
foresee_trigger.js
66 ms
event
111 ms
181 ms
activityi;src=4903503;type=cabun15;cat=bundl0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=5405078823678.195
200 ms
activityi;src=4903503;type=cahoph15;cat=homep0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=5807140632532.537
201 ms
activityi;src=4903707;type=wire2015;cat=wirel0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=3113161954097.4497
218 ms
activityi;src=4903503;type=cabtv15;cat=tv-ho0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=7833553045056.761
216 ms
activityi;src=5366752;type=homemo1;cat=new-h002;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=176561849657.44614
218 ms
s7689923388417
87 ms
__utm.gif
81 ms
activityi;src=4903503;type=cainter1;cat=inter0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=2608012037817.3887
137 ms
fbds.js
76 ms
66 ms
109 ms
conversion.js
37 ms
14 ms
22 ms
23 ms
18 ms
dest5.html
17 ms
vms.js
95 ms
dest4.html
18 ms
Hardware-EN-D.png
28 ms
ibs:dpid=21&dpuuid=163990601885004121375
14 ms
1-desktop-hero-lockup-smallboy.jpg
17 ms
ibs:dpid=358&dpuuid=6770667838499625742
7 ms
rogers.ca SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rogers.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 Rogers.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.
rogers.ca
Open Graph description is not detected on the main page of Rogers. 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: