12.3 sec in total
2.1 sec
9.7 sec
463 ms
Click here to check amazing Hayfm content. Otherwise, check out these important facts you probably never knew about hayfm.de
This website is for sale! hayfm.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, hayfm.de has it all. ...
Visit hayfm.deWe analyzed Hayfm.de page load time and found that the first response time was 2.1 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hayfm.de performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.0 s
50/100
25%
Value3.8 s
83/100
10%
Value310 ms
78/100
30%
Value0.219
57/100
15%
Value4.0 s
87/100
10%
2131 ms
147 ms
65 ms
294 ms
268 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 60% of them (78 requests) were addressed to the original Hayfm.de, 17% (22 requests) were made to Static.xx.fbcdn.net and 7% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 782.6 kB (60%)
1.3 MB
522.5 kB
In fact, the total size of Hayfm.de main page is 1.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. 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 637.7 kB which makes up the majority of the site volume.
Potential reduce by 43.8 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 43.8 kB or 77% of the original size.
Potential reduce by 5.1 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. Hayfm images are well optimized though.
Potential reduce by 461.9 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 461.9 kB or 72% of the original size.
Potential reduce by 271.8 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. Hayfm.de needs all CSS files to be minified and compressed as it can save up to 271.8 kB or 81% of the original size.
Number of requests can be reduced by 96 (74%)
129
33
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hayfm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
www.hayfm.de
2131 ms
wp-emoji-release.min.js
147 ms
css
65 ms
initaudioplayer-1.css
294 ms
flashblock.css
268 ms
player.css
279 ms
fb-comments-hidewpcomments.css
332 ms
audio1_html5.css
345 ms
mashsb.min.css
437 ms
settings.css
452 ms
captions.css
466 ms
ace-video-container.css
474 ms
tribe-events-full.min.css
514 ms
wp125.css
490 ms
font-awesome.min.css
594 ms
pagenavi-css.css
598 ms
public.css
617 ms
magnific-popup.css
615 ms
ml_audio.css
628 ms
8b1a4f5383c3ce8463428fd0200b1049b49d8030.css
642 ms
v1-silver.css
746 ms
style.css
752 ms
addtoany.min.css
756 ms
fbseo-style.css
769 ms
reset.css
862 ms
text.css
819 ms
960.css
887 ms
superfish.css
903 ms
prettyPhoto.css
899 ms
style.css
1033 ms
custom_style.css
972 ms
style.css
991 ms
swfobject.js
38 ms
jquery.js
1174 ms
jquery-migrate.min.js
1038 ms
amazingaudioplayer.js
1039 ms
initaudioplayer-1.js
1111 ms
soundmanager2-nodebug-jsmin.js
1128 ms
jquery-ui.min.js
59 ms
jwplayer.js
92 ms
jquery-ui.js
8 ms
dmsguestbook.css
1152 ms
jquery.mousewheel.min.js
1043 ms
audio1_html5.js
925 ms
mashsb.min.js
991 ms
css
24 ms
jquery.themepunch.plugins.min.js
1018 ms
jquery.themepunch.revolution.min.js
1003 ms
jquery.magnific-popup.min.js
985 ms
public.js
898 ms
jquery.ui.touch-punch.min.js
901 ms
ai.js
952 ms
jquery.jplayer.min.2.7.1.js
990 ms
mp3-jplayer-2.3.2.js
977 ms
jquery.cycle.all.min.js
967 ms
cycle1_script.js
888 ms
jquery.prettyPhoto.js
892 ms
superfish.combined.js
937 ms
script.js
997 ms
jquery.ml.audio2.js
978 ms
ml.playlist.toggle.js
979 ms
core.min.js
873 ms
widget.min.js
880 ms
mouse.min.js
927 ms
slider.min.js
979 ms
jquery.ui.touch-punch.js
934 ms
custom_params.js
1008 ms
html5mp3playlist-min.js
982 ms
style.css
766 ms
gs_async.js
257 ms
stripe.png
172 ms
bg-header-blau.png
408 ms
HayFM-Logo-265x90px.png
267 ms
searchbox.png
170 ms
sf-menu-bg.png
149 ms
bg-main-schatten.png
172 ms
c1-frame.png
397 ms
slider-3-914x374.jpg
540 ms
slider-controls.png
291 ms
heading_underline.png
298 ms
all.js
85 ms
25867982805_e4d22db79a_s.jpg
196 ms
25241417753_8d3d7af584_s.jpg
213 ms
25241417343_daf54a3e29_s.jpg
346 ms
25237453164_723919e9c7_s.jpg
345 ms
arrow-3-dark.png
376 ms
bg-unter-slider-schatten.png
413 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
126 ms
page.js
117 ms
cycle1_params.php
885 ms
auto-arrows.png
422 ms
137 ms
xd_arbiter.php
29 ms
xd_arbiter.php
37 ms
tribe-events-full-mobile.min.css
136 ms
ping
58 ms
like_box.php
291 ms
kyEKgjk51ZE.css
34 ms
xgj7bXhJNEH.css
39 ms
Czh0gDTFcBt.css
36 ms
N-k91nHCZS2.css
52 ms
ZeuPykSxSED.css
45 ms
IaUW_C3Onoi.css
30 ms
q68gy-v_YMF.js
59 ms
FJmpeSpHpjS.js
75 ms
0wM5s1Khldu.js
43 ms
1bNoFZUdlYZ.js
85 ms
njO1TPvGzoR.js
84 ms
1QuX41zDRrx.js
88 ms
Oagsvfb4VWi.js
86 ms
LTv6ZK-5zxz.js
93 ms
1FCa-btixu2.js
91 ms
969718_10151683696018679_1103512842_n.jpg
171 ms
safe_image.php
3110 ms
safe_image.php
965 ms
safe_image.php
484 ms
421094_10150638046343679_1568980532_n.jpg
32 ms
12806027_937956002978712_327967811623357042_n.jpg
36 ms
1934927_947166058705062_7848364743561445582_n.jpg
88 ms
1901156_232987653710953_6221731906375332232_n.jpg
30 ms
553767_341822839225841_1032715896_n.jpg
28 ms
10354686_10150004552801856_220367501106153455_n.jpg
30 ms
12743482_10153962620138679_7072277737198549190_n.jpg
126 ms
1935613_929841587051342_4849763424702484647_n.jpg
58 ms
wL6VQj7Ab77.png
21 ms
s7jcwEQH7Sx.png
18 ms
QDwYpIaRyfG.png
21 ms
pimRBh7B6ER.png
21 ms
K00K-UgnsKu.png
17 ms
I6-MnjEovm5.js
4 ms
pQrUxxo5oQp.js
5 ms
hayfm.de 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
<frame> or <iframe> elements do not have a title
hayfm.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
hayfm.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hayfm.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Hayfm.de 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.
hayfm.de
Open Graph description is not detected on the main page of Hayfm. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: