6 sec in total
2.1 sec
3.7 sec
229 ms
Visit home.fm now to see the best up-to-date HOME content for United States and also check out these interesting facts you probably never knew about home.fm
106.9 HOME.fm The Music That Makes You Feel Good. We play positive music that is safe for the entire family.
Visit home.fmWe analyzed Home.fm page load time and found that the first response time was 2.1 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
home.fm performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value6.3 s
11/100
25%
Value13.0 s
2/100
10%
Value3,590 ms
1/100
30%
Value0
100/100
15%
Value27.2 s
0/100
10%
2118 ms
77 ms
140 ms
143 ms
140 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 58% of them (30 requests) were addressed to the original Home.fm, 12% (6 requests) were made to Farm2.staticflickr.com and 6% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Home.fm.
Page size can be reduced by 1.3 MB (40%)
3.3 MB
2.0 MB
In fact, the total size of Home.fm main page is 3.3 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. 45% of websites need less resources to load. CSS take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 14.5 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 14.5 kB or 74% of the original size.
Potential reduce by 33.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. HOME images are well optimized though.
Potential reduce by 278.3 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 278.3 kB or 62% of the original size.
Potential reduce by 978.4 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. Home.fm needs all CSS files to be minified and compressed as it can save up to 978.4 kB or 49% of the original size.
Number of requests can be reduced by 29 (59%)
49
20
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HOME. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
home.fm
2118 ms
style.css
77 ms
normalize.css
140 ms
grid.css
143 ms
fonts.css
140 ms
main.css
806 ms
responsive.css
140 ms
mediaelementplayer.css
215 ms
jquery.smartbanner.css
207 ms
modernizr-2.6.2.min.js
272 ms
css3-mediaqueries.js
271 ms
jquery.min.js
30 ms
7f45c1e9_ai1ec_parsed_css.css
607 ms
subscriptions.css
273 ms
widgets.css
280 ms
jquery.js
473 ms
jquery-migrate.min.js
337 ms
plugins-ck.js
338 ms
jquery.smartbanner.js
345 ms
main-ck.js
407 ms
mediaelement-and-player.min.js
537 ms
devicepx-jetpack.js
8 ms
gprofiles.js
56 ms
wpgroho.js
410 ms
e-201611.js
4 ms
ga.js
60 ms
25744491031_1fbe178014_z.jpg
138 ms
25718635662_ea90f0cc96_z.jpg
133 ms
24777142192_971dbbdaf8_z.jpg
134 ms
24542173810_788ed1bd81_z.jpg
164 ms
24210803333_f31a19a9e7_z.jpg
320 ms
24469978609_dfd304fde4_z.jpg
365 ms
Banner_StudentScholarshipsSquare.jpg1.jpeg
537 ms
Leadercast2016_230x116.jpg
536 ms
HOMEfm_NoPinching_230x116.jpg
654 ms
Lecrae2_230x116.jpg
637 ms
PFX_230x116.jpg
632 ms
BannerSoundcloud_HALF.jpg
634 ms
Kansas_230x116.jpg
610 ms
globetrotters_230x116.jpg
611 ms
7RUZ8cKUwEc
122 ms
bariol_regular-webfont.woff
141 ms
g.gif
69 ms
hovercard.css
64 ms
services.css
87 ms
__utm.gif
60 ms
www-embed-player-vflfNyN_r.css
57 ms
www-embed-player.js
93 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
91 ms
ad_status.js
90 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
82 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
83 ms
home.fm accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
home.fm 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
Missing source maps for large first-party JavaScript
home.fm 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 Home.fm 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 Home.fm 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.
home.fm
Open Graph data is detected on the main page of HOME. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: