Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

holzfragen.de

Sachverständigenbüro für Holzschutz

Page Load Speed

1.9 sec in total

First Response

300 ms

Resources Loaded

1.5 sec

Page Rendered

77 ms

About Website

Click here to check amazing Holzfragen content for Germany. Otherwise, check out these important facts you probably never knew about holzfragen.de

Informationen zum Holzschutz und zu holzzerstörenden Insekten und Pilzen

Visit holzfragen.de

Key Findings

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

Performance Metrics

holzfragen.de performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

holzfragen.de

300 ms

holzfragen.de

430 ms

p_3258725_covf.220h.gif

766 ms

home.jpg

107 ms

index_logo.gif

215 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 86% of them (6 requests) were addressed to the original Holzfragen.de, 14% (1 request) were made to Beuth.de. The less responsive or slowest element that took the longest time to load (766 ms) relates to the external source Beuth.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.2 kB (35%)

Content Size

29.1 kB

After Optimization

18.9 kB

In fact, the total size of Holzfragen.de main page is 29.1 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 5% of websites need less resources to load. Images take 16.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 9.4 kB

  • Original 12.4 kB
  • After minification 11.2 kB
  • After compression 3.0 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 9.4 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 757 B

  • Original 16.7 kB
  • After minification 15.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. Holzfragen images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

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

Accessibility Review

holzfragen.de accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

High

Links do not have a discernible name

Best Practices

holzfragen.de best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

holzfragen.de SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Holzfragen.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 Holzfragen.de main page’s claimed encoding is iso-8859-1. 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

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