7.4 sec in total
309 ms
6.2 sec
849 ms
Visit poste.ch now to see the best up-to-date Poste content for Switzerland and also check out these interesting facts you probably never knew about poste.ch
Nous faisons avancer la Suisse. Avec des prestations dignes de confiance, dans les mondes physique et numérique.
Visit poste.chWe analyzed Poste.ch page load time and found that the first response time was 309 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
poste.ch performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.4 s
21/100
25%
Value9.9 s
10/100
10%
Value16,140 ms
0/100
30%
Value0.003
100/100
15%
Value25.3 s
0/100
10%
309 ms
529 ms
654 ms
203 ms
926 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Poste.ch, 60% (31 requests) were made to Post.ch and 19% (10 requests) were made to Postshop.ch. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Post.ch.
Page size can be reduced by 1.9 MB (32%)
5.9 MB
4.0 MB
In fact, the total size of Poste.ch main page is 5.9 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. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 131.5 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.7 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 131.5 kB or 87% of the original size.
Potential reduce by 56.1 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. Poste images are well optimized though.
Potential reduce by 638.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 638.3 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. Poste.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 Poste. 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.
poste.ch
309 ms
www.poste.ch
529 ms
654 ms
head-portal.min.js
203 ms
main.min.css
926 ms
utag.sync.js
51 ms
jquery-1.11.0.min.js
405 ms
main.min.js
1030 ms
post-logo-svg.svg
356 ms
my-post-24-paketautomat-960-593.jpg
1221 ms
pickpost-960x593.jpg
365 ms
vorfrankierte-produkte-960-593.jpg
462 ms
utag.js
353 ms
empfaengerservices-pakete-1500-927.jpg
302 ms
9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff
852 ms
2a004a53-ac5c-43b3-9eeb-9f74ae4c1609.woff
854 ms
Posticon-Regular.woff
975 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
854 ms
SessionState
695 ms
webtrends.hm.min.js
782 ms
webtrends.replicate.min.js
786 ms
wtid.js
776 ms
GetFormatDropdown
444 ms
pop-up-post-960-593.jpg
719 ms
molly-monster-960-593.jpg
1115 ms
konzern-berichterstattung-960-593.jpg
717 ms
neue-briefmarken-960-593.jpg
750 ms
briefzentrum-haerkingen-960-593.jpg
1115 ms
empfaengerservices-pakete-1500-927.jpg
1603 ms
pop-up-post-960-593.jpg
955 ms
my-post-24-paketautomat-960-593.jpg
1052 ms
pickpost-960x593.jpg
1054 ms
vorfrankierte-produkte-960-593.jpg
2147 ms
GetShopTabHtml
1179 ms
molly-monster-960-593.jpg
1506 ms
konzern-berichterstattung-960-593.jpg
1179 ms
SessionData
1105 ms
dcs.gif
286 ms
GetWeightDropdown
880 ms
dcs.gif
99 ms
A093111.png
979 ms
A091111.png
845 ms
A094111.png
840 ms
A090111.png
842 ms
A089312.png
745 ms
662688_WEB160.jpg
908 ms
A089311.png
1144 ms
688341_WEB160.jpg
1142 ms
A088121.png
1439 ms
A088114.png
1437 ms
dcs.gif
81 ms
dcs.gif
46 ms
poste.ch accessibility score
poste.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
poste.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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poste.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 French language. Our system also found out that Poste.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.
poste.ch
Open Graph description is not detected on the main page of Poste. 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: