8.5 sec in total
973 ms
5.8 sec
1.7 sec
Visit foehr.de now to see the best up-to-date Foehr content for Germany and also check out these interesting facts you probably never knew about foehr.de
Bei uns finden Sie passende Ferienwohnungen, Ferienhäuser und Hotels für Ihren Urlaub an der Nordsee. Buchen Sie jetzt hier Ihren Urlaub auf der Insel Föhr.
Visit foehr.deWe analyzed Foehr.de page load time and found that the first response time was 973 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foehr.de performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.1 s
5/100
25%
Value8.3 s
19/100
10%
Value940 ms
30/100
30%
Value0.043
99/100
15%
Value16.1 s
6/100
10%
973 ms
196 ms
199 ms
197 ms
291 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 87% of them (89 requests) were addressed to the original Foehr.de, 5% (5 requests) were made to Translate.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Foehr.de.
Page size can be reduced by 737.9 kB (27%)
2.8 MB
2.0 MB
In fact, the total size of Foehr.de main page is 2.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. 55% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 53.4 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 53.4 kB or 82% of the original size.
Potential reduce by 79.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. Foehr images are well optimized though.
Potential reduce by 288.6 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 288.6 kB or 59% of the original size.
Potential reduce by 317.0 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. Foehr.de needs all CSS files to be minified and compressed as it can save up to 317.0 kB or 85% of the original size.
Number of requests can be reduced by 52 (51%)
101
49
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foehr. 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 20 to 1 for CSS and as a result speed up the page load time.
www.foehr.de
973 ms
stylesheet_9a91f2f94b.css
196 ms
ext_tt_products.css
199 ms
new_style2014.css
197 ms
new_home.css
291 ms
text-formats-form.css
608 ms
jquery-ui-1.7.2.custom.css
483 ms
new_farbcodes.css
579 ms
scroll.css
293 ms
jquery.js
581 ms
jquery-ui-1.7.2.custom.min.js
967 ms
fluidextresizer.js
393 ms
custom.js
490 ms
common.js
579 ms
merkeranimate.js
587 ms
jquery.cookie.js
673 ms
swfobject.js
674 ms
main.css
673 ms
jquery.min.js
30 ms
jquery-ui.js
10 ms
new_nav.css
681 ms
element.js
49 ms
new_layout2014.css
607 ms
text-formats.css
579 ms
content-right-col.css
581 ms
skrollr.min.js
494 ms
skrollr.menu.min.js
501 ms
js.js
588 ms
jquery.nicescroll.min.js
737 ms
max-light_0-webfont.woff
99 ms
ga.js
37 ms
gplus-32.png
93 ms
status.gif
112 ms
scrollen.png
112 ms
wischenhand.png
113 ms
introtext.png
114 ms
2.png
113 ms
webcam.png
225 ms
anreise.png
226 ms
2.png
227 ms
O.png
228 ms
S.png
228 ms
6.png
228 ms
SW.png
320 ms
SO.png
325 ms
bubble.png
321 ms
flare.png
487 ms
frame.png
324 ms
tel.gif
326 ms
search-button-lupe.gif
386 ms
footer.png
389 ms
claim.jpg
395 ms
logo.jpg
395 ms
unterkunft.png
395 ms
prospekt.png
482 ms
fanseite.png
486 ms
beratung.png
492 ms
karte.png
492 ms
buehne1.jpg
971 ms
max-bolditalic_0-webfont.woff
574 ms
buehne2.jpg
770 ms
clouds-1.png
676 ms
clouds-2.png
1066 ms
daniel-webfont.woff
600 ms
buehne3.gif
3183 ms
gal1.jpg
1257 ms
buehne5.jpg
1536 ms
translateelement.css
93 ms
main.js
193 ms
__utm.gif
17 ms
MaxWeb-Bold.woff
782 ms
buehne6.gif
2738 ms
flagge_fr.gif
963 ms
facebook-logo-transparent_h20.png
1060 ms
youtube_logo_transparent_h20.png
1062 ms
nav-bg-home.gif
1157 ms
nav-bg-insel-home.gif
1050 ms
bg-menu2-insel2.gif
1142 ms
menu2-border.png
1144 ms
supafly-submenu-arrow.gif
1147 ms
nav-bg-familie-home.gif
1237 ms
element_main.js
36 ms
bg-menu2-familie2.gif
1239 ms
translate_24dp.png
57 ms
l
40 ms
cleardot.gif
36 ms
nav-bg-vital-home.gif
1148 ms
bg-menu2-vital.gif
1238 ms
nav-bg-aktiv-home.gif
1244 ms
bg-menu2-aktiv2.gif
1243 ms
nav-bg-kultur-home.gif
1464 ms
te_ctrl3.gif
11 ms
bg-menu2-kultur2.gif
1278 ms
nav-bg-service-home.gif
1274 ms
bg-menu2-service3.gif
1271 ms
menuezieher.png
1364 ms
print.css
99 ms
layout.css
100 ms
nav.css
103 ms
farbcodes.css
388 ms
extensions.css
194 ms
ext_sms_foehr_az.css
104 ms
foehr.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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
foehr.de 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
General
Impact
Issue
Detected JavaScript libraries
foehr.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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foehr.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Foehr.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.
foehr.de
Open Graph data is detected on the main page of Foehr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: