1.2 sec in total
78 ms
907 ms
172 ms
Click here to check amazing Player FM96 content for Canada. Otherwise, check out these important facts you probably never knew about player.fm96.com
Londons Best Rock FM96!
Visit player.fm96.comWe analyzed Player.fm96.com page load time and found that the first response time was 78 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
player.fm96.com performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value23.7 s
0/100
25%
Value10.9 s
6/100
10%
Value1,410 ms
15/100
30%
Value0.817
4/100
15%
Value22.8 s
1/100
10%
78 ms
47 ms
43 ms
40 ms
54 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Player.fm96.com, 8% (6 requests) were made to Platform.twitter.com and 8% (6 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (704 ms) relates to the external source Corus-player-img.s3.amazonaws.com.
Page size can be reduced by 863.0 kB (55%)
1.6 MB
712.1 kB
In fact, the total size of Player.fm96.com 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. 65% of websites need less resources to load. Javascripts take 983.8 kB which makes up the majority of the site volume.
Potential reduce by 154.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 154.7 kB or 74% of the original size.
Potential reduce by 31.0 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. Obviously, Player FM96 needs image optimization as it can save up to 31.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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 105.6 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.fm96.com needs all CSS files to be minified and compressed as it can save up to 105.6 kB or 84% of the original size.
Number of requests can be reduced by 32 (49%)
65
33
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Player FM96. 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 from 7 to 1 for CSS and as a result speed up the page load time.
player.fm96.com
78 ms
bootstrap-flat-ui-2.0.css
47 ms
style.music.css
43 ms
jquery.smartbanner.css
40 ms
ima3.js
54 ms
bootstrap-jquery-jquery-ui.min.gz.js
39 ms
s_cfplfm_code.gz.js
44 ms
jquery.smartbanner.min.js
36 ms
gpt.js
49 ms
beacon.js
5 ms
bg-dots.png
704 ms
cfplfm.gz.svg
55 ms
widgets.js
40 ms
loading.gif
281 ms
CORUS_RADIO.png
19 ms
lato-regular-webfont.woff
50 ms
lato-light-webfont.woff
49 ms
lato-bold-webfont.woff
64 ms
lato-black-webfont.woff
48 ms
Flat-UI-Icons.woff
199 ms
pubads_impl_82.js
17 ms
ads
314 ms
container.html
16 ms
player-music-desktop-v1.91.js
60 ms
sdk.js
173 ms
bridge3.124.0_en.html
65 ms
client.js
34 ms
jwpsrv.js
94 ms
CFPLFM_pl.js
87 ms
CFPLFM.html
61 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
68 ms
like.php
85 ms
wAAABgAAAAAABcAAAQAAAAAAAAAAAAAAAAAAABsEAAAAAAAAAAAAAAACAAAABgAAYAQAAEAFAABABQAAQAYAAEAGAABABAAA4ASAAEAEAABABgAAQAYAAD0D4ABDBIAARgQAAIAEAABABIAASgOAAEMEwABABMAAQAQAAEAGAABABAAAZgQAAEQAAAAAAAoAFAAeAIgAuAEEAWAChgOyA9QECAQqBKQFJgXoBgAGGgYqBkIGgAaSBvQHFgdQB4YHuAABAAAAGwDPAAYAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADAAAAAEAAAAAAAIABwCNAAEAAAAAAAMADABFAAEAAAAAAAQADACiAAEAAAAAAAUACwAkAAEAAAAAAAYADABpAAEAAAAAAAoAGgDGAAMAAQQJAAEAGAAMAAMAAQQJAAIADgCUAAMAAQQJAAMAGABRAAMAAQQJAAQAGACuAAMAAQQJAAUAFgAvAAMAAQQJAAYAGAB1AAMAAQQJAAoANADganctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjEAVgBlAHIAcwBpAG8AbgAgADEALgAxanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
3 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
19 ms
s3410727057605
42 ms
syndication
117 ms
426429553674690560
213 ms
100x100bb.jpg
137 ms
60x60bb.jpg
31 ms
60x60bb.jpg
14 ms
100x100bb.jpg
19 ms
100x100bb.jpg
19 ms
60x60bb.jpg
23 ms
100x100bb.jpg
25 ms
100x100bb.jpg
24 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
17 ms
qeKvIRsJabD.js
315 ms
LVx-xkvaJ0b.png
349 ms
20 ms
jot
47 ms
xd_arbiter.php
134 ms
xd_arbiter.php
285 ms
expansion_embed.js
15 ms
528251671570158477
36 ms
abg.js
37 ms
m_js_controller.js
44 ms
googlelogo_color_112x36dp.png
23 ms
osd.js
20 ms
s
26 ms
x_button_blue2.png
17 ms
jot
21 ms
proxy.jpg
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
16 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
Ikwai2oI_normal.png
142 ms
mGOpacBm_normal.jpg
174 ms
2WvAAe94_normal.jpg
176 ms
j-bBf44H_normal.jpg
174 ms
134c70e20c7f95d0deb158e945097d79_normal.jpeg
174 ms
0SPhXEVr_normal.jpg
176 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
42 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
87 ms
player.fm96.com accessibility score
player.fm96.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
player.fm96.com 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.fm96.com 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.fm96.com 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.fm96.com
Open Graph data is detected on the main page of Player FM96. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: