Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

postident.deutschepost.de

Sichere, persönliche Identifikation mit POSTIDENT | Deutsche Post

Page Load Speed

3.6 sec in total

First Response

391 ms

Resources Loaded

2.9 sec

Page Rendered

300 ms

About Website

Click here to check amazing POSTIDENT Deutsche Post content for Germany. Otherwise, check out these important facts you probably never knew about postident.deutschepost.de

Kunden-Identifizierung sofort und sicher per POSTIDENT: in der Filiale vor Ort oder online per Videochat, mit neuem Ausweis (eID) oder per Foto-Ident.

Visit postident.deutschepost.de

Key Findings

We analyzed Postident.deutschepost.de page load time and found that the first response time was 391 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

postident.deutschepost.de performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.306

38/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

postident.deutschepost.de

391 ms

postident

666 ms

postident.html

356 ms

otSDKStub.js

113 ms

clientlibs-styles.min.084d914cc76e96e5cac1895ad1d19ef6.css

31 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Postident.deutschepost.de, 70% (31 requests) were made to Deutschepost.de and 14% (6 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Deutschepost.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 570.7 kB (62%)

Content Size

923.1 kB

After Optimization

352.4 kB

In fact, the total size of Postident.deutschepost.de main page is 923.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. 60% of websites need less resources to load. HTML takes 304.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 265.0 kB

  • Original 304.7 kB
  • After minification 256.0 kB
  • After compression 39.7 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 48.8 kB, which is 16% 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 265.0 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 12.3 kB

  • Original 196.1 kB
  • After minification 183.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. POSTIDENT Deutsche Post images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 124.1 kB

  • Original 220.5 kB
  • After minification 219.3 kB
  • After compression 96.3 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 124.1 kB or 56% of the original size.

CSS Optimization

-84%

Potential reduce by 169.3 kB

  • Original 201.8 kB
  • After minification 199.6 kB
  • After compression 32.5 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. Postident.deutschepost.de needs all CSS files to be minified and compressed as it can save up to 169.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (56%)

Requests Now

36

After Optimization

16

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of POSTIDENT Deutsche Post. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

postident.deutschepost.de accessibility score

91

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

postident.deutschepost.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

postident.deutschepost.de SEO score

73

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postident.deutschepost.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Postident.deutschepost.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 data is detected on the main page of POSTIDENT Deutsche Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: