Tools & Wizards About Us
loar.de screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

loar.de

LOAR - Hotels und Appartements in Dresden - Versicherungs- und Finanzmakler

Page Load Speed

1.1 sec in total

First Response

278 ms

Resources Loaded

667 ms

Page Rendered

171 ms

loar.de screenshot

About Website

Visit loar.de now to see the best up-to-date LOAR content and also check out these interesting facts you probably never knew about loar.de

Übernachten in Hotels, Appartements und Ferienwohnungen auf dem Weißen Hirsch in Dresden. Buchung von Hotel-Storno- und Reise-Versicherungen.

Visit loar.de

Key Findings

We analyzed Loar.de page load time and found that the first response time was 278 ms and then it took 838 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

loar.de performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

loar.de

278 ms

expe1110.css

130 ms

analytics.js

27 ms

silhouette-dresden.jpg

256 ms

note_brown_banner_l%20V5.gif

223 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 70% of them (7 requests) were addressed to the original Loar.de, 20% (2 requests) were made to Google-analytics.com and 10% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (278 ms) belongs to the original domain Loar.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 24.4 kB (26%)

Content Size

93.6 kB

After Optimization

69.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Loar.de main page is 93.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 42.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 14.6 kB

  • Original 19.2 kB
  • After minification 12.4 kB
  • After compression 4.6 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 6.8 kB, which is 35% 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 14.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 42.6 kB
  • After minification 42.6 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. LOAR images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

CSS Optimization

-90%

Potential reduce by 9.8 kB

  • Original 10.9 kB
  • After minification 7.6 kB
  • After compression 1.1 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. Loar.de needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOAR. According to our analytics all requests are already optimized.

Network Requests Diagram

loar.de

loar.de

278 ms

expe1110.css

expe1110.css

130 ms

analytics.js

analytics.js

27 ms

silhouette-dresden.jpg

silhouette-dresden.jpg

256 ms

note_brown_banner_l%20V5.gif

note_brown_banner_l%20V5.gif

223 ms

Ulenburg-logo_2.gif

Ulenburg-logo_2.gif

210 ms

VillaHerzogLogo.gif

VillaHerzogLogo.gif

219 ms

LOARlogo_2.gif

LOARlogo_2.gif

218 ms

collect

collect

14 ms

js

js

132 ms

Accessibility Review

loar.de accessibility score

93

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

loar.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

loar.de SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loar.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Loar.de main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

loar.de

Open Graph description is not detected on the main page of LOAR. 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: