5.1 sec in total
328 ms
4.4 sec
332 ms
Visit diepost.ch now to see the best up-to-date Die Post content and also check out these interesting facts you probably never knew about diepost.ch
We power Switzerland. With trustworthy services in the physical and digital worlds. At home, during leisure time and at work.
Visit diepost.chWe analyzed Diepost.ch page load time and found that the first response time was 328 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
diepost.ch performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value3.6 s
60/100
25%
Value7.5 s
27/100
10%
Value3,720 ms
1/100
30%
Value0.039
100/100
15%
Value16.4 s
5/100
10%
328 ms
742 ms
196 ms
888 ms
230 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Diepost.ch, 61% (31 requests) were made to Post.ch and 20% (10 requests) were made to Postshop.ch. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Post.ch.
Page size can be reduced by 1.9 MB (33%)
5.8 MB
3.9 MB
In fact, the total size of Diepost.ch main page is 5.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 129.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. This page needs HTML code to be minified as it can gain 17.9 kB, which is 12% 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.9 kB or 87% of the original size.
Potential reduce by 53.0 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. Die Post images are well optimized though.
Potential reduce by 639.7 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 639.7 kB or 70% of the original size.
Potential reduce by 1.1 MB
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. Diepost.ch needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.
Number of requests can be reduced by 7 (16%)
45
38
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Die 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 8 to 1 for JavaScripts and as a result speed up the page load time.
diepost.ch
328 ms
privat
742 ms
head-portal.min.js
196 ms
main.min.css
888 ms
utag.sync.js
230 ms
jquery-1.11.0.min.js
406 ms
main.min.js
915 ms
post-logo-svg.svg
404 ms
my-post-24-paketautomat-960-593.jpg
432 ms
pickpost-960x593.jpg
416 ms
vorfrankierte-produkte-960-593.jpg
416 ms
utag.js
415 ms
empfaengerservices-pakete-1500-927.jpg
393 ms
SessionState
412 ms
GetFormatDropdown
267 ms
pop-up-post-960-593.jpg
400 ms
molly-monster-960-593.jpg
788 ms
konzern-berichterstattung-960-593.jpg
415 ms
neue-briefmarken-960-593.jpg
691 ms
briefzentrum-haerkingen-960-593.jpg
935 ms
empfaengerservices-pakete-1500-927.jpg
1149 ms
pop-up-post-960-593.jpg
696 ms
my-post-24-paketautomat-960-593.jpg
752 ms
pickpost-960x593.jpg
988 ms
vorfrankierte-produkte-960-593.jpg
1869 ms
GetShopTabHtml
902 ms
molly-monster-960-593.jpg
1367 ms
konzern-berichterstattung-960-593.jpg
1085 ms
SessionData
978 ms
9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff
1026 ms
2a004a53-ac5c-43b3-9eeb-9f74ae4c1609.woff
1181 ms
Posticon-Regular.woff
1229 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
1205 ms
webtrends.hm.min.js
105 ms
webtrends.replicate.min.js
109 ms
wtid.js
106 ms
dcs.gif
119 ms
GetWeightDropdown
1053 ms
dcs.gif
69 ms
A088114.png
841 ms
A091111.png
731 ms
A092841.png
639 ms
694650_WEB160.jpg
538 ms
A089312.png
636 ms
575044_WEB160.jpg
540 ms
A088112.png
1129 ms
688341_WEB160.jpg
840 ms
A092300.png
1238 ms
662688_WEB160.jpg
1046 ms
dcs.gif
111 ms
dcs.gif
24 ms
diepost.ch accessibility score
diepost.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
diepost.ch SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diepost.ch can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Diepost.ch 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.
diepost.ch
Open Graph description is not detected on the main page of Die 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: