6.6 sec in total
1.1 sec
5 sec
502 ms
Click here to check amazing Lofer content for Germany. Otherwise, check out these important facts you probably never knew about lofer.com
Familienurlaub im Salzburger Saalachtal. Ob E-Mountainbiken, Baden in Wilden Wassern oder auf Skiern und beim Winterwandern.
Visit lofer.comWe analyzed Lofer.com page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lofer.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value5.6 s
18/100
25%
Value8.8 s
16/100
10%
Value1,440 ms
15/100
30%
Value0.025
100/100
15%
Value11.6 s
18/100
10%
1129 ms
204 ms
484 ms
204 ms
1222 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 74% of them (46 requests) were addressed to the original Lofer.com, 6% (4 requests) were made to Use.typekit.net and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Lofer.com.
Page size can be reduced by 1.1 MB (35%)
3.1 MB
2.0 MB
In fact, the total size of Lofer.com main page is 3.1 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 97.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. This page needs HTML code to be minified as it can gain 52.3 kB, which is 48% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 97.4 kB or 89% of the original size.
Potential reduce by 29.9 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. Lofer images are well optimized though.
Potential reduce by 576.0 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 576.0 kB or 69% of the original size.
Potential reduce by 374.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. Lofer.com needs all CSS files to be minified and compressed as it can save up to 374.4 kB or 86% of the original size.
Number of requests can be reduced by 31 (55%)
56
25
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lofer. 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 9 to 1 for CSS and as a result speed up the page load time.
1129 ms
lightbox.css
204 ms
c9c4a83c5c5e061f68933042d44059c0.css
484 ms
module_default.css
204 ms
c9c4a83c5c5e061f68933042d44059c0.css
1222 ms
finder.css
208 ms
0b75d46a885e7105c569dc9f3f42ecb6.js
1427 ms
en_lightbox.min.js
306 ms
0b75d46a885e7105c569dc9f3f42ecb6.js
771 ms
rokmediaqueries.js
311 ms
sidemenu.js
409 ms
0b75d46a885e7105c569dc9f3f42ecb6.js
431 ms
acymailing_module.js
523 ms
mootools-mobile.js
535 ms
rokmediaqueries.js
583 ms
roksprocket.js
616 ms
moofx.js
641 ms
roksprocket.request.js
683 ms
strips.js
719 ms
strips-speeds.js
745 ms
features.js
785 ms
0b75d46a885e7105c569dc9f3f42ecb6.js
839 ms
ggi4gat.js
167 ms
mediaelement-and-player.js
232 ms
spotlight.js
113 ms
lofer.com
201 ms
ga.js
5 ms
close.png
233 ms
__utm.gif
121 ms
loading.gif
122 ms
prev.png
123 ms
next.png
120 ms
sprite.png
421 ms
winterurlaub-saalachtal.jpg
324 ms
Skiurlaub-Almenwelt-Saalachtal.jpg
767 ms
Familienurlaub-Rodeln-Winterurlaub.jpg
752 ms
freeski-lofer.jpg
529 ms
conway-lifestyle-71.jpg
769 ms
langlaufen.jpg
750 ms
almenwelt-lofer.jpg
830 ms
printButton.png
635 ms
217e9eb0780ff3d337aae442aa7630c4.jpg
742 ms
unken-winter.jpg
847 ms
bbfff8480f55ec84954499eafa6a4fbc.jpg
850 ms
b6be8312bfb55167c70fee610861a675.jpg
856 ms
d9c8c122cb9e3f84629817b42fe9e9d2.jpg
864 ms
noise.png
871 ms
iframe.php
384 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
819 ms
ur7Q6vcVmKa20PZgtX6IKw4Pewz0Um7IxFK6GsmS9TMff5fRgsMmeMJ6Mk6g5Mb.woff
59 ms
Add-18pjwnxpNlk-iq3TkC4HgNquAtZITMHmrt-JfnSffFERgsMmeMJ6Mk6g5Mw.woff
116 ms
fontawesome-webfont.woff
939 ms
IcoMoon.svg
971 ms
collect
93 ms
p.gif
138 ms
analytics.js
4 ms
style.css
109 ms
collect
14 ms
css
58 ms
print.css
105 ms
sprite-klein-weiss.png
256 ms
JSee5Bn9hpOHBhFZzI16g6CWcynf_cDxXwCLxiixG1c.woff
34 ms
lofer.com 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
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
lofer.com 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
Missing source maps for large first-party JavaScript
lofer.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lofer.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Lofer.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.
lofer.com
Open Graph description is not detected on the main page of Lofer. 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: