Report Summary

  • 29

    Performance

    Renders faster than
    48% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

post.de

Deutsche Post – Die Post für Deutschland

Page Load Speed

5.9 sec in total

First Response

278 ms

Resources Loaded

4.9 sec

Page Rendered

663 ms

post.de screenshot

About Website

Welcome to post.de homepage info - get ready to check Post best content for Germany right away, or after learning these important things about post.de

Die Deutsche Post im Internet: Porto berechnen, Online Porto drucken, Filialen und Briefkästen finden, Briefmarken und Postprodukte im Online-Shop, Innovative Leistungen, Kundenservice.

Visit post.de

Key Findings

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

Performance Metrics

post.de performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

post.de

278 ms

de.html

52 ms

base.head~2024-05-06-09-44-05-000~cache.js

38 ms

dpag~2024-05-06-09-44-05-000~cache.css

26 ms

launch-815646454707.min.js

21 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Post.de, 89% (55 requests) were made to Deutschepost.de and 5% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Deutschepost.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 411.9 kB (42%)

Content Size

975.1 kB

After Optimization

563.2 kB

In fact, the total size of Post.de main page is 975.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 585.3 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 129.4 kB

  • Original 142.1 kB
  • After minification 110.7 kB
  • After compression 12.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 31.4 kB, which is 22% 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 129.4 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 13.5 kB

  • Original 247.6 kB
  • After minification 234.2 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. Post images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 269.0 kB

  • Original 585.3 kB
  • After minification 585.3 kB
  • After compression 316.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 269.0 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (16%)

Requests Now

58

After Optimization

49

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

post.de accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

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

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

post.de SEO score

86

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

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

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