3.1 sec in total
46 ms
2.4 sec
609 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 46 ms and then it took 3 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.8 s
57/100
10%
Value8.2 s
2/100
25%
Value6.5 s
39/100
10%
Value1,860 ms
9/100
30%
Value0
100/100
15%
Value14.0 s
10/100
10%
46 ms
9 ms
303 ms
66 ms
40 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yahoo.ca, 82% (74 requests) were made to S.yimg.com and 9% (8 requests) were made to Ca.yahoo.com. The less responsive or slowest element that took the longest time to load (942 ms) relates to the external source V-c4eoe517av.wc.yahoodns.net.
Page size can be reduced by 654.4 kB (36%)
1.8 MB
1.2 MB
In fact, the total size of Yahoo.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. 70% of websites need less resources to load. HTML takes 802.4 kB which makes up the majority of the site volume.
Potential reduce by 625.0 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 625.0 kB or 78% of the original size.
Potential reduce by 25.2 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. Yahoo images are well optimized though.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 128 B
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 has all CSS files already compressed.
Number of requests can be reduced by 36 (44%)
82
46
The browser has sent 82 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 34 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yahoo.ca
46 ms
ca.yahoo.com
9 ms
ca.yahoo.com
303 ms
cmp.js
66 ms
tdv2-wafer-utils.customErrorHandler.bcda778b736c3a054af62f437b536e78.js
40 ms
fpDesktop.2e8440661542e9dfceb3228f597ec875.js
50 ms
benji-2.1.39.js
54 ms
wf-clipboard-copy-1.0.2.js
54 ms
wf-caas-1.36.5.js
53 ms
wf-video-3.1.2.js
56 ms
wf-bind-1.1.3.js
55 ms
wf-text-1.2.0.js
56 ms
wf-fetch-1.19.1.js
59 ms
wf-benji-1.1.4.js
59 ms
wf-scrollview-2.22.6.js
57 ms
wf-toggle-1.15.4.js
67 ms
wf-beacon-1.3.4.js
59 ms
wf-action-1.8.1.js
58 ms
wf-template-1.4.3.js
59 ms
wf-menu-1.3.0.js
60 ms
wf-countdown-1.2.5.js
62 ms
wf-form-1.34.5.js
61 ms
wf-lightbox-1.10.6.js
62 ms
wf-native-da-1.0.5.js
63 ms
wf-image-1.4.0.js
63 ms
wf-rapid-1.10.8.js
63 ms
react-wafer-stream.custom.default.34fba140d46159f80d116c63459e57e7.js
64 ms
61bb2d1.caas-hpgrid_with_rightrail.min.js
67 ms
cerebro_min.js
42 ms
yahoo_homepage_en-US_s_f_p_bestfit_homepage.png
43 ms
yahoo_homepage_en-US_s_f_w_bestfit_homepage.png
44 ms
header_1x-1479864976616.min.png
45 ms
spritify-sprite-light-fd484ded-e3dce7a4.png
46 ms
Medium.woff
45 ms
Regular.woff
44 ms
Light.woff
44 ms
ExtraLight.woff
60 ms
Semibold.woff
45 ms
c921f580-0bca-11ef-aff7-7c6a0807cc96.cf.jpg
56 ms
a248eb10-0d2a-11ef-bbfe-4fc83aec46a9.cf.jpg
44 ms
f984ae90-0984-11ef-becb-95027689166f.cf.jpg
44 ms
deabd957074e2757b62629a0095bb7b4.cf.jpg
47 ms
9276b081d5cfb6558ee03099f689d7a6.cf.jpg
38 ms
c547c980-0c83-11ef-bfff-0f8d78fed554.cf.jpg
28 ms
88464ffeb9541d3069715725df602b3c.cf.jpg
31 ms
trendingNow.yhome-atomic.c16f97f81be530fa2b48a1ffeffd4678.min.css
12 ms
analytics-3.54.3.js
42 ms
wf-core-1.65.1.js
47 ms
sh-5.17.91.js
41 ms
homepage-pwa-defer-1.1.6.js
47 ms
safe.min.js
84 ms
advertisement_0.0.19.js
84 ms
d194210076e665d18efc04d1a30727b8.cf.jpg
234 ms
26282bd2a6dd11e87fae80f873ed825d.cf.jpg
239 ms
68c02a21602bca3ebd1c643046917cd6.cf.jpg
237 ms
96abbb44b71804a1f0293e4d24cd1c28.cf.jpg
235 ms
30a79e5e3b6a2b9558d924b6ee2bb9df.cf.jpg
237 ms
f273746a6f595e4d60a149c495a759d4.cf.jpg
239 ms
002772028c73086f2d4acebc2831b005.cf.jpg
238 ms
Oval_x3.png
240 ms
4010e373ee12dadc2caeffd6a20a3edc.cf.jpg
239 ms
f3a00a1a6dd4e332c0245219b9fd9e58.cf.jpg
241 ms
1a0c6da51e77b3a32b01132a5184d803.cf.jpg
242 ms
c3eaf8d0-0ca8-11ef-95f7-9e768d3801a4.cf.jpg
241 ms
f926de3731173582afaf450850f2ba35.cf.jpg
244 ms
f3ab59098695feca5a6b134df78ca1a0.cf.jpg
242 ms
0812692e709c64d32acfd0ce1302298f.cf.jpg
245 ms
bd5a597660014d0fd8b5f48268102e25.cf.jpg
244 ms
c80fda93d3f652813efe8ab7376f5727.cf.jpg
244 ms
91977dc9b0a7b70b2df15c01b2e3fb84.cf.jpg
245 ms
42c4b7b68f362235e9df05777b4f25b9.cf.jpg
245 ms
ddf863a9e3b5d2319f4b79a367f8b800.cf.jpg
246 ms
cs_1.6.0.js
124 ms
remote
557 ms
exp.json
30 ms
perf-vitals_3.2.0.js
28 ms
218 ms
309 ms
412 ms
pixel.gif
942 ms
pixel.gif
48 ms
pixel.gif
22 ms
NotificationHistory.getHistory;count=5;imageTag=img%3A40x40%7C2%7C80;theme=default;notificationTypes=breakingNews;lastUpdate=1715175042;loadInHpViewer=true;includePersonalized=;lang=en-CA;region=CA;partner=yahoo
155 ms
spinner-24x24-anim.gif
3 ms
c576919.caas-hpgrid_with_rightrail.min.css
4 ms
colors_1.1.27.min.css
3 ms
react-wafer-nativeAd.NativeAd.atomic.ltr.d0676534b61aea80519e6db47117d0c6.min.css
4 ms
spaceball.gif
31 ms
http%3A%2F%2Fcdn.taboola.com%2Flibtrc%2Fstatic%2Fthumbnails%2F48cffa8be16c0245eb5620cc69324d88.png
10 ms
remote
304 ms
yahoo.ca accessibility score
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
Links do not have a discernible name
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: