8.7 sec in total
36 ms
8.6 sec
134 ms
Click here to check amazing Player Edge content for Canada. Otherwise, check out these important facts you probably never knew about player.edge.ca
102.1 the Edge
Visit player.edge.caWe analyzed Player.edge.ca page load time and found that the first response time was 36 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
player.edge.ca performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value23.4 s
0/100
25%
Value11.4 s
5/100
10%
Value2,020 ms
7/100
30%
Value0.994
2/100
15%
Value22.9 s
1/100
10%
36 ms
32 ms
25 ms
23 ms
42 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Player.edge.ca, 24% (18 requests) were made to Pbs.twimg.com and 8% (6 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (8 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 795.7 kB (50%)
1.6 MB
785.8 kB
In fact, the total size of Player.edge.ca main page is 1.6 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 988.2 kB which makes up the majority of the site volume.
Potential reduce by 143.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 143.7 kB or 74% of the original size.
Potential reduce by 1.3 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. Player Edge images are well optimized though.
Potential reduce by 571.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 571.8 kB or 58% of the original size.
Potential reduce by 78.9 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. Player.edge.ca needs all CSS files to be minified and compressed as it can save up to 78.9 kB or 84% of the original size.
Number of requests can be reduced by 22 (33%)
67
45
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Player Edge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
player.edge.ca
36 ms
bootstrap-flat-ui-2.0.css
32 ms
style.music.css
25 ms
jquery.smartbanner.css
23 ms
ima3.js
42 ms
bootstrap-jquery-jquery-ui.min.gz.js
65 ms
s_cfnyfm_code.gz.js
63 ms
jquery.smartbanner.min.js
63 ms
gpt.js
4 ms
beacon.js
9 ms
pubads_impl_81.js
59 ms
bg-dots.png
56 ms
cfnyfm.gz.svg
55 ms
widgets.js
50 ms
loading.gif
68 ms
CORUS_RADIO.png
67 ms
lato-regular-webfont.woff
69 ms
lato-light-webfont.woff
75 ms
lato-bold-webfont.woff
69 ms
lato-black-webfont.woff
68 ms
Flat-UI-Icons.woff
216 ms
container.html
53 ms
player-music-desktop-v1.91.js
59 ms
ads
272 ms
sdk.js
183 ms
bridge3.123.0_en.html
72 ms
client.js
30 ms
jwpsrv.js
103 ms
CFNYFM_pl.js
71 ms
CFNYFM.html
64 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
77 ms
wAAABgAAAAAABcAAAQAAAAAAAAAAAAAAAAAAABsEAAAAAAAAAAAAAAACAAAABgAAYAQAAEAFAABABQAAQAYAAEAGAABABAAA4ASAAEAEAABABgAAQAYAAD0D4ABDBIAARgQAAIAEAABABIAASgOAAEMEwABABMAAQAQAAEAGAABABAAAZgQAAEQAAAAAAAoAFAAeAIgAuAEEAWAChgOyA9QECAQqBKQFJgXoBgAGGgYqBkIGgAaSBvQHFgdQB4YHuAABAAAAGwDPAAYAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADAAAAAEAAAAAAAIABwCNAAEAAAAAAAMADABFAAEAAAAAAAQADACiAAEAAAAAAAUACwAkAAEAAAAAAAYADABpAAEAAAAAAAoAGgDGAAMAAQQJAAEAGAAMAAMAAQQJAAIADgCUAAMAAQQJAAMAGABRAAMAAQQJAAQAGACuAAMAAQQJAAUAFgAvAAMAAQQJAAYAGAB1AAMAAQQJAAoANADganctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjEAVgBlAHIAcwBpAG8AbgAgADEALgAxanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
8 ms
s3121694775298
43 ms
like.php
93 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
26 ms
60x60bb.jpg
29 ms
100x100bb.jpg
64 ms
60x60bb.jpg
27 ms
60x60bb.jpg
26 ms
60x60bb.jpg
75 ms
60x60bb.jpg
25 ms
60x60bb.jpg
61 ms
60x60bb.jpg
72 ms
syndication
7822 ms
426114551029850112
7923 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
12 ms
expansion_embed.js
16 ms
osd.js
7693 ms
vpc6VNjRPXV.js
7985 ms
LVx-xkvaJ0b.png
8014 ms
jot
28 ms
35 ms
ads
62 ms
xd_arbiter.php
138 ms
xd_arbiter.php
243 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
CWjzH6QP_normal.jpg
70 ms
WTCWHi0G_normal.jpg
66 ms
o98QwZ-a_normal.jpg
68 ms
9Wn1swUC_normal.jpg
67 ms
CceDPPJW8AEPelJ.jpg:small
68 ms
CceCgwtXEAAdFcZ.jpg:small
70 ms
CcdqyEeWoAAiPuw.jpg:small
69 ms
Ccdo-QvWEAA3xYU.jpg:small
70 ms
CcdU794WEAAQCY4.jpg:small
72 ms
Ccb2og6VIAABL12.jpg:small
84 ms
Ccbo5vbXIAAEKuq.jpg:small
75 ms
CcbddwCWwAAOUaa.jpg:small
75 ms
CcbbLNDW0AAWi2A.jpg:small
74 ms
CcbPvVOWEAYV1zJ.jpg:small
81 ms
CcbNcJMUkAA7PvE.jpg:small
79 ms
CcbDvSfW0AECF0W.jpg:small
85 ms
CcbCCI-XIAEUkjm.jpg:small
83 ms
CcafpxGW0AEzK9d.jpg:small
85 ms
player.edge.ca accessibility score
player.edge.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
player.edge.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 doesn't use 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 Player.edge.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 Player.edge.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.
player.edge.ca
Open Graph data is detected on the main page of Player Edge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: