3 sec in total
153 ms
1.6 sec
1.3 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 153 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
20minutes.ch performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value11.6 s
0/100
25%
Value5.5 s
55/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.5 s
92/100
10%
153 ms
588 ms
283 ms
84 ms
283 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 20minutes.ch, 37% (23 requests) were made to 20min-images.imgix.net and 29% (18 requests) were made to 20min.ch. The less responsive or slowest element that took the longest time to load (588 ms) belongs to the original domain 20minutes.ch.
Page size can be reduced by 312.5 kB (16%)
2.0 MB
1.7 MB
In fact, the total size of 20minutes.ch main page is 2.0 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. 65% of websites need less resources to load. Images take 873.6 kB which makes up the majority of the site volume.
Potential reduce by 302.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. 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 302.5 kB or 81% of the original size.
Potential reduce by 0 B
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 9.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 359 B
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 needs all CSS files to be minified and compressed as it can save up to 359 B or 19% of the original size.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 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 32 to 1 for JavaScripts and as a result speed up the page load time.
20minutes.ch
153 ms
20minutes.ch
588 ms
fr
283 ms
otSDKStub.js
84 ms
6566f9c6c3b8de6d5f10ed23.js
283 ms
stf.js
72 ms
tentacle.js
51 ms
15cf0aa761d258b0.css
11 ms
72be6148bd527625.css
24 ms
polyfills-c67a75d1b6f99dc8.js
27 ms
pub-0711653372274150
148 ms
beagle.min.js
52 ms
20min_durable.js
244 ms
ebx.js
57 ms
9008-e055df8adcab9cee.js
26 ms
6258-ee9263c324b2588a.js
22 ms
2011-65a71b510fbab6c7.js
26 ms
6426-4d11ae8211be813c.js
30 ms
6811-67975363e290ebdb.js
34 ms
1202.9d30537414c16895.js
33 ms
webpack-2e4098af32c9b396.js
33 ms
framework-4dea08757e550bb8.js
33 ms
main-9dd4b4ab948c657e.js
33 ms
_app-0ae3eeeaf351fa61.js
47 ms
4147-04813076a8ba60be.js
45 ms
index-1ae1d05375d1b4ce.js
47 ms
_buildManifest.js
46 ms
_ssgManifest.js
44 ms
f1aeb90f-3d11-4baf-b163-9b7fc7e715cd.json
131 ms
j.php
145 ms
79549a48-14c3-4ab0-ac46-e9eee96f7678.jpeg
207 ms
1170a542-e53c-4faa-99b8-0aab12a04023.png
182 ms
f1d308c8-f76e-4aca-ba47-14d5a999c28f.jpeg
182 ms
25848862-2535-4de5-85bf-5ccc144d20e0.avif
140 ms
ec981819-4e48-4275-be5e-83aebb5350b7.jpeg
237 ms
7c844ac0-3e36-487e-a91c-5aff66d28632.jpeg
179 ms
ae9f6871-46b0-4fab-94d8-82bd37ae9f0d.jpeg
146 ms
7b726c3d-d4e7-47fa-90e6-f68f8de0480b.avif
238 ms
574cf5cd-3828-4200-89e2-6525b625817c.jpeg
243 ms
fcd26f3d-4583-4214-8f45-1926d19dc288.png
256 ms
4fd8aaa8-0e92-4a0c-9317-27e9fe326b1b.png
248 ms
4dc0ecfc-e35d-4b89-90c2-aa687aade411.jpeg
253 ms
ced8d8ca-2c80-4504-80d9-fd88d424e31b.jpeg
237 ms
244d9a52-e2db-4e7f-be57-61df25018069.jpeg
307 ms
1789f8ae-fc5d-43b1-81dc-1a16d0ac5ba3.jpeg
313 ms
a8f78085-2645-42bc-8429-83141289287f.jpeg
246 ms
b2f78764-68e9-412e-8a4b-354d91f5ff98.jpeg
318 ms
9581dc7d-3564-4690-9a84-931707a3869d.jpeg
251 ms
9b5c147e-a03c-4ae2-b423-f6041ebec5ba.jpeg
324 ms
2aa788a2-2315-438c-a3d5-5523196be4d9.png
261 ms
eaa79ab6-933a-473d-89bb-ef132e2aa7fe.avif
326 ms
f671813c-f3db-4861-8b69-ae3e9d3564c4.jpeg
337 ms
4fdbb567-25ba-4868-b5b0-efd0ca932d2c.png
306 ms
AGSKWxWmkxZ6YtBPLsk53AezKre2dE-8R7HW-Csywc_5NcI_OFtBPaAwmF0mG017FaoZyx8l5jp_sYPlb3sLZAciG25oCCdW9A6_ZjrYLu3Boz27HaGtmghl8myeRR7sq_MhCIvaNOPBZA==
80 ms
location
103 ms
v.gif
100 ms
6566f9c6c3b8de6d5f10ed23.nomodule.js
197 ms
otBannerSdk.js
26 ms
fr.json
32 ms
iab2V2Data.json
41 ms
googleData.json
24 ms
otTCF.js
32 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
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: