5.9 sec in total
29 ms
2.8 sec
3.1 sec
Visit 20minutes.ch now to see the best up-to-date 20 Minutes content for Switzerland and also check out these interesting facts you probably never knew about 20minutes.ch
Retrouve en direct toutes les dernières infos suisses et internationales grâce à 20 minutes: sport, économie, politique, people, culture et faits divers.
Visit 20minutes.chWe analyzed 20minutes.ch page load time and found that the first response time was 29 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
20minutes.ch performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value7.8 s
3/100
25%
Value5.0 s
64/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
88/100
10%
29 ms
372 ms
478 ms
61 ms
61 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 20minutes.ch, 29% (33 requests) were made to Cdn.unitycms.io and 29% (32 requests) were made to Myshop.20min.ch. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source Fooby.ch.
Page size can be reduced by 419.9 kB (12%)
3.5 MB
3.1 MB
In fact, the total size of 20minutes.ch main page is 3.5 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. 85% 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. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 354.1 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 354.1 kB or 80% of the original size.
Potential reduce by 63.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. 20 Minutes images are well optimized though.
Potential reduce by 148 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 2.6 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. 20minutes.ch has all CSS files already compressed.
Number of requests can be reduced by 31 (32%)
98
67
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 20 Minutes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
20minutes.ch
29 ms
20minutes.ch
372 ms
fr
478 ms
batonturbo.css
61 ms
7957091b394da981.css
61 ms
polyfills-5cd94c89d3acac5f.js
41 ms
20min_durable.js
235 ms
otSDKStub.js
110 ms
2367.75ba5a36b18bfa93.js
84 ms
webpack-d21c0f11e3c88bfb.js
85 ms
framework-e3af041a06f0d0a2.js
85 ms
main-d598ea80fb2de367.js
85 ms
_app-fe2c87909e0ef96f.js
90 ms
3555-a6152d9cec18105e.js
85 ms
index-1e62a65bd9d38d06.js
90 ms
_buildManifest.js
89 ms
_ssgManifest.js
89 ms
_middlewareManifest.js
89 ms
9d7QANU_q5qBPuN-nBxeJ-.jpg
180 ms
20mindaily.w-20min-redesign.html
888 ms
embedded-iframe
442 ms
FswyWD5YqldA6qJsbJWuzq.png
185 ms
3_rN4u_u4oeAUQU3EcbNag.jpg
191 ms
8cZhUb4pqGaA76BRKka7bM.jpg
883 ms
Dl_EkE4JauGB7lzxYtQqhW.png
215 ms
71B16NQEKV7BBLXZ_DvLju.jpg
196 ms
1vLJJb2CaeuBUZsuAmOqj6.jpg
206 ms
EwaxkMQ0q-O9clevXvEugl.jpg
203 ms
AlFpunVI4ucAirdsXnNCsK.gif
296 ms
1RQCXaRZqH9AiAIVY7nn9C.jpg
202 ms
FPpfSjI6acqAWG7P6JtaQ3.jpg
888 ms
0Wis8F3Eqh28XhmrbqBgjJ.jpg
210 ms
9uSJo_0Mafp9ATrx1c42PS.jpg
216 ms
75zReROwKhe8cuPVC9XtlT.jpg
216 ms
2KGt-nmF4J0BvIcE3felG7.jpg
221 ms
7AOtDOc5K_fBjqu5tT4n4d.jpg
224 ms
71B16NQEKV7BBLXZ_DvLju.jpg
221 ms
6xBJuQNL44rBxcBGM30bs9.jpg
226 ms
7odufh8-KETAlaQ8SwWm72.jpg
225 ms
5mkJzcDYarC9VlmhkgsUp2.jpg
228 ms
4Kv5BSJZqgaBgkz-QnUta_.jpg
291 ms
7AOtDOc5K_fBjqu5tT4n4d.jpg
290 ms
BRf67PRzKSHAoV_kxfEOpi.jpg
294 ms
0EsxttIMaVYBjb4PBplu0Q.png
295 ms
Bwu_KB_FKNo827pKAUAY6A.jpg
295 ms
9uSJo_0Mafp9ATrx1c42PS.jpg
302 ms
3L40eWhAani83rU-4iMx07.jpg
302 ms
5_KF-Q8TKbgASl_gL9wG5s.jpg
303 ms
7DmF5lp3as69vJHBpnycht.jpg
304 ms
6xBJuQNL44rBxcBGM30bs9.jpg
305 ms
E0MvJI5HaJfB-jOV4d2l5D.jpg
306 ms
43R3RG0TaIB9CjAdbMOGnz.jpg
307 ms
CEYF14Arq9SA32Bh6hN_lT.jpg
307 ms
BatonTurboWeb-Book.f3973c9d.woff
6 ms
f1aeb90f-3d11-4baf-b163-9b7fc7e715cd.json
93 ms
location
106 ms
otBannerSdk.js
44 ms
BatonTurboWeb-Regular.494c930d.woff
33 ms
BatonTurboWeb-Medium.10714ed3.woff
10 ms
BatonTurboWeb-Heavy.f1126e70.woff
9 ms
fr.json
19 ms
iab2Data.json
65 ms
googleData.json
67 ms
otTCF.js
62 ms
app_20min.eb59b309.css
34 ms
lozad.min.js
417 ms
default.js
429 ms
runtime.d94b3b43.js
413 ms
0.cf60d32b.js
413 ms
1.e2cda89a.js
412 ms
app_20min.118a6106.js
413 ms
otCenterRounded.json
40 ms
otCookieSettingsButton.json
41 ms
otCommonStyles.css
42 ms
gtm.js
265 ms
31ed79734c5459d5c2b8c79132bc.jpg
60 ms
601fffb873e64e8404587c8aec68.png
251 ms
0b7e684ac2962c48149a98956388.png
252 ms
011054dc7ca077619836df7f94ed.png
251 ms
94e65904075690d720f2c5ba56ac.png
251 ms
0c66dd8e939d3f650f952f5fbafe.png
250 ms
iframe-cart.2a869f1a.svg
316 ms
arrow-long.497abb35.svg
254 ms
bb439fd5ced34bfed7697aeed5c9.png
252 ms
1beb022ee13191f0de7050e0b241.png
256 ms
8894017eaf524d1626d2aed2ff31.png
251 ms
8eafb4690b756c40dbcc55bd804e.png
252 ms
09f25a3bf5718634bbe88b9df14c.png
258 ms
bbd3e84b91c2775bdd6ed67e672e.png
256 ms
0232f3789ccf76eea071f76c56fc.png
254 ms
10475975b874eaacbf1b269ee5c2.png
255 ms
b327f5241d566162dce3b1871bfe.png
258 ms
9a611272dbfd4c88a1a709d8357a.png
258 ms
9e3913347a8794811f1dca3d385f.png
256 ms
widget-ecb9b31523.css
305 ms
iframeAutofit.js
244 ms
widget-3db0888c2302613096a2.js
427 ms
20min_de.png
94 ms
BatonTurbo-Regular.5eb8c5d7.woff
319 ms
BatonTurbo-Medium.511b17ac.woff
177 ms
BatonTurbo-Heavy.c5964ec9.woff
351 ms
js
52 ms
21790_3-2_600-400.jpg
725 ms
fooby-big-claim.svg
120 ms
DFPAudiencePixel;ord=9635778239462524;dc_seg=6939994573
98 ms
open-sans-v13-latin-regular-ce65961588.woff
222 ms
open-sans-v13-latin-700-72862e7cf1.woff
169 ms
roboto-slab-v6-latin-regular-fc6efd0243.woff
258 ms
6e935a3f5b389a02da6514a20069.jpg
68 ms
4b9ec20c46c564d6fb592e1552df.jpg
72 ms
d83e4779e34025fc369dd70fd250.jpg
64 ms
82475557f28280171927897a82c6.jpg
71 ms
20minutes.ch accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
20minutes.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
20minutes.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 20minutes.ch can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that 20minutes.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.
20minutes.ch
Open Graph description is not detected on the main page of 20 Minutes. 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: