1.7 sec in total
143 ms
1.4 sec
161 ms
Visit homer.ca now to see the best up-to-date Homer content and also check out these interesting facts you probably never knew about homer.ca
Canada's guide to news and information featuring Canadian radio and TV webcasts, job listings, maps, search engines, and other useful resources.
Visit homer.caWe analyzed Homer.ca page load time and found that the first response time was 143 ms and then it took 1.5 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.
homer.ca performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value2.1 s
96/100
25%
Value3.2 s
92/100
10%
Value1,110 ms
23/100
30%
Value0.389
26/100
15%
Value8.7 s
36/100
10%
143 ms
5 ms
56 ms
54 ms
55 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 15% of them (7 requests) were addressed to the original Homer.ca, 17% (8 requests) were made to Apis.google.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 62.9 kB (41%)
151.8 kB
89.0 kB
In fact, the total size of Homer.ca main page is 151.8 kB. 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 59.2 kB which makes up the majority of the site volume.
Potential reduce by 47.1 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 6.5 kB, which is 11% 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 47.1 kB or 83% of the original size.
Potential reduce by 3.1 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. Homer images are well optimized though.
Potential reduce by 12.6 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 12.6 kB or 35% of the original size.
Number of requests can be reduced by 26 (57%)
46
20
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
homer.ca
143 ms
show_ads.js
5 ms
canadaflag.gif
56 ms
menutop.gif
54 ms
menubottom.gif
55 ms
vancouvercanada2.JPG
147 ms
ca-pub-6446269203467944.js
50 ms
zrt_lookup.html
55 ms
show_ads_impl.js
58 ms
Logo_25wht.gif
44 ms
all.js
282 ms
widgets.js
107 ms
in.js
33 ms
menumiddle.gif
101 ms
newscube04.gif
104 ms
ads
286 ms
osd.js
52 ms
plusone.js
99 ms
secureAnonymousFramework
61 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
147 ms
ads
269 ms
sprite_connect_v14.png
54 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
26 ms
fastbutton
93 ms
postmessageRelay
90 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
23 ms
101 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
74 ms
xd_arbiter.php
237 ms
xd_arbiter.php
460 ms
3193398744-postmessagerelay.js
58 ms
rpc:shindig_random.js
62 ms
7465816730207727213
77 ms
abg.js
82 ms
m_js_controller.js
99 ms
googlelogo_color_112x36dp.png
80 ms
13077156096584944014
110 ms
cb=gapi.loaded_0
27 ms
s
39 ms
x_button_blue2.png
45 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
ui
84 ms
jot
121 ms
like.php
88 ms
qeKvIRsJabD.js
481 ms
LVx-xkvaJ0b.png
546 ms
homer.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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
homer.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
homer.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
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
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homer.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 Homer.ca main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
homer.ca
Open Graph description is not detected on the main page of Homer. 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: