Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

datenschutz.de

Virtuelles Datenschutzbüro – Ein Informationsangebot der öffentlichen Datenschutzinstanzen

Page Load Speed

2.2 sec in total

First Response

439 ms

Resources Loaded

1.6 sec

Page Rendered

128 ms

datenschutz.de screenshot

About Website

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

Internetseite der öffentlichen Datenschutzinstanzen

Visit datenschutz.de

Key Findings

We analyzed Datenschutz.de page load time and found that the first response time was 439 ms and then it took 1.8 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

datenschutz.de performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

datenschutz.de

439 ms

www.datenschutz.de

692 ms

virdsb-basic.css

99 ms

tagcloud.css

197 ms

logo_dynarrow.gif

275 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Datenschutz.de and no external sources were called. The less responsive or slowest element that took the longest time to load (692 ms) belongs to the original domain Datenschutz.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.4 kB (60%)

Content Size

27.5 kB

After Optimization

11.1 kB

In fact, the total size of Datenschutz.de main page is 27.5 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. CSS take 11.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.8 kB

  • Original 9.7 kB
  • After minification 8.9 kB
  • After compression 2.9 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 6.8 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 164 B

  • Original 6.4 kB
  • After minification 6.3 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. Datenschutz images are well optimized though.

CSS Optimization

-83%

Potential reduce by 9.4 kB

  • Original 11.3 kB
  • After minification 8.6 kB
  • After compression 1.9 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. Datenschutz.de needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

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

Accessibility Review

datenschutz.de accessibility score

92

Accessibility Issues

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

Buttons do not have an accessible name

Best Practices

datenschutz.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

datenschutz.de SEO score

99

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

    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 Datenschutz.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 Datenschutz.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 Datenschutz. 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: