Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

liebhaberuhren.de

liebhaberuhren.de - This website is for sale! - liebhaberuhren Resources and Information.

Page Load Speed

1.1 sec in total

First Response

525 ms

Resources Loaded

552 ms

Page Rendered

72 ms

liebhaberuhren.de screenshot

About Website

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

This website is for sale! liebhaberuhren.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, liebhaberuhr...

Visit liebhaberuhren.de

Key Findings

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

Performance Metrics

liebhaberuhren.de performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

liebhaberuhren.de

525 ms

seal.png

11 ms

bullet_lime.gif

3 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Liebhaberuhren.de, 67% (2 requests) were made to Img.sedoparking.com. The less responsive or slowest element that took the longest time to load (525 ms) belongs to the original domain Liebhaberuhren.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.1 kB (82%)

Content Size

80.2 kB

After Optimization

14.1 kB

In fact, the total size of Liebhaberuhren.de main page is 80.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 59.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 50.3 kB

  • Original 59.8 kB
  • After minification 55.8 kB
  • After compression 9.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 50.3 kB or 84% of the original size.

Image Optimization

-78%

Potential reduce by 15.8 kB

  • Original 20.4 kB
  • After minification 4.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. Obviously, Liebhaberuhren needs image optimization as it can save up to 15.8 kB or 78% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

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

Accessibility Review

liebhaberuhren.de accessibility score

88

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

liebhaberuhren.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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

liebhaberuhren.de SEO score

90

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liebhaberuhren.de 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 Liebhaberuhren.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.

Social Sharing Optimization

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