3.3 sec in total
145 ms
2.7 sec
446 ms
Visit yahoo.ca now to see the best up-to-date Yahoo content for Canada and also check out these interesting facts you probably never knew about yahoo.ca
Latest news coverage, email, free stock quotes, live scores and video are just the beginning. Discover more every day at Yahoo!
Visit yahoo.caWe analyzed Yahoo.ca page load time and found that the first response time was 145 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
yahoo.ca performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value4.9 s
28/100
25%
Value4.7 s
69/100
10%
Value490 ms
59/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
145 ms
40 ms
677 ms
31 ms
4 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yahoo.ca, 56% (50 requests) were made to S.yimg.com and 4% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (677 ms) relates to the external source Ca.yahoo.com.
Page size can be reduced by 938.5 kB (57%)
1.7 MB
717.7 kB
In fact, the total size of Yahoo.ca main page is 1.7 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. 75% 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 576.6 kB which makes up the majority of the site volume.
Potential reduce by 396.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. This page needs HTML code to be minified as it can gain 61.4 kB, which is 12% 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 396.4 kB or 77% of the original size.
Potential reduce by 815 B
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. Yahoo images are well optimized though.
Potential reduce by 379.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 379.8 kB or 66% of the original size.
Potential reduce by 161.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. Yahoo.ca needs all CSS files to be minified and compressed as it can save up to 161.5 kB or 78% of the original size.
Number of requests can be reduced by 38 (48%)
79
41
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yahoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
yahoo.ca
145 ms
ca.yahoo.com
40 ms
ca.yahoo.com
677 ms
combo
31 ms
atomic-min.css
4 ms
combo
8 ms
g-r-min.js
15 ms
yahoo_en-US_f_p_142x37.png
24 ms
pc_icons_btns_sprite_0720_330pm.png
16 ms
uh.woff
5 ms
yglyphs.woff
4 ms
stacyedash1024_635x250_1456720688.jpg
26 ms
stacyedash1024_120x48_1456720688.jpg
47 ms
jlaw-larson-gaga_120x48_1456718981.jpg
47 ms
brie-victims-ipad_120x48_1456725302.jpg
74 ms
lenoardo1024_120x48_1456722491.jpg
74 ms
chris-rock_120x48_1456711522.jpg
73 ms
t.gif
75 ms
chrisrock.jpg
77 ms
ae5b4feadfc30b567323315e098a4a23
76 ms
9f3ff19bd1bb93cc5ab06a2b28370ff6.jpeg
75 ms
916c2d26f7b73b372b48de8788c6748c
35 ms
1452198305135-9787.jpg
35 ms
1453745903883-4621.jpg
36 ms
1456253206954-9147.jpg
37 ms
1426609770531-7583.jpg
37 ms
combo
54 ms
combo
75 ms
r-csc.html
51 ms
r-sf.html
24 ms
cs_0.2.js
29 ms
sfext-min.js
24 ms
combo
49 ms
combo
39 ms
yi
425 ms
a
503 ms
a
528 ms
rapidworker_1_2.js
301 ms
fpc.pl
304 ms
combo
15 ms
combo
7 ms
combo
15 ms
combo
6 ms
p2
11 ms
today;ids=%5B%22id-1991351%22%2C%22id-1991202%22%2C%22id-1991304%22%2C%22id-1991354%22%2C%22id-1991149%22%5D;startIndex=55;ui=%7B%22viewer_off_network%22%3Atrue%2C%22viewer%22%3Afalse%2C%22pcsExclusions%22%3Afalse%7D
62 ms
banner
282 ms
yi
108 ms
banner
308 ms
yi
107 ms
yql
176 ms
yql
181 ms
yql
162 ms
yql
60 ms
adsbygoogle.js
37 ms
get-user-id
98 ms
ca-pub-5786243031610172.js
9 ms
zrt_lookup.html
36 ms
show_ads_impl.js
83 ms
get-user-id
135 ms
cfcm.ashx
128 ms
pixel
132 ms
ads
169 ms
ads
169 ms
osd.js
22 ms
rightmedia
39 ms
pixel
22 ms
rightmedia
4 ms
0.gif
12 ms
%7BSSP_USER_ID%7D
85 ms
Pix-1x1.gif
56 ms
300X250_generic.html
9 ms
scriptLoader.min.0.5.2.js
7 ms
ConvergeMonkey
142 ms
300X250_generic.html
4 ms
It_was_such_pain_such-e477977a66e4f1a934b18ee839233601
75 ms
13ee4ba36d5763bff8336edc7f23adb6
77 ms
b1d59a9f920628b970a2f4f7ff70e709
72 ms
video.tvinnotime.com@f1cd3873-34b0-38fb-9a36-a0a8f7313676_FULL.png
84 ms
2d3cb9ae6cd6f8447c3f5bbfa1ebc9c207d447bb.jpg
58 ms
71ecf37d-68e4-45dc-8787-a943e10319de_EvAw98UvX8SL3vCVoPOJpJoOvPCRBDn1AlTaDCPDikDLPRpQDCYPSc4qtx71wieJfBJaJuzET1k-_2_0.jpg
58 ms
02ee3696ac904ecb8ba408d0fae36e83
59 ms
cdec593ec42a87af2a9433792b8fb0ae
59 ms
7b7b1017f4ed035c5a6fc311c891f43b
57 ms
video.tvinnotime.com@c6887fd9-2ced-3af3-8184-8959a1e6e5f9_FULL.png
59 ms
video.tvinnotime.com@73aa40c1-6ae3-3486-8111-1349e605391a_FULL.png
69 ms
ycp.js
81 ms
combo
67 ms
pc_flags_sprite_0317_Regular_630pm.png
25 ms
combo
4 ms
yahoo.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yahoo.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
Browser errors were logged to the console
Page has valid source maps
yahoo.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 Yahoo.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 Yahoo.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.
yahoo.ca
Open Graph data is detected on the main page of Yahoo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: