13.7 sec in total
348 ms
12.9 sec
383 ms
Click here to check amazing Maggi content for Switzerland. Otherwise, check out these important facts you probably never knew about maggi.ch
Entdecken Sie die Vielfalt der Maggi Produkte: Unsere kulinarischen Geschmackshelfer, Würzen, Gewürzmischungen und schmackhafte Rezeptideen.
Visit maggi.chWe analyzed Maggi.ch page load time and found that the first response time was 348 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
maggi.ch performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value8.7 s
1/100
25%
Value9.3 s
13/100
10%
Value4,950 ms
0/100
30%
Value0.25
50/100
15%
Value18.5 s
3/100
10%
348 ms
1201 ms
35 ms
33 ms
41 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 87% of them (109 requests) were addressed to the original Maggi.ch, 3% (4 requests) were made to Google-analytics.com and 2% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Maggi.ch.
Page size can be reduced by 446.5 kB (6%)
7.2 MB
6.7 MB
In fact, the total size of Maggi.ch main page is 7.2 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 6.6 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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 39.2 kB or 79% of the original size.
Potential reduce by 15.3 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. Maggi images are well optimized though.
Potential reduce by 252.5 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 252.5 kB or 62% of the original size.
Potential reduce by 139.5 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. Maggi.ch needs all CSS files to be minified and compressed as it can save up to 139.5 kB or 82% of the original size.
Number of requests can be reduced by 54 (45%)
121
67
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maggi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.maggi.ch
348 ms
www.maggi.ch
1201 ms
system.base.css
35 ms
system.menus.css
33 ms
system.messages.css
41 ms
comment.css
39 ms
date.css
40 ms
datepicker.1.7.css
603 ms
field.css
40 ms
footer_sitemap.css
41 ms
node.css
564 ms
search.css
42 ms
views.css
40 ms
ctools.css
558 ms
rate.css
582 ms
locale.css
44 ms
jcarousel-default.css
43 ms
all.css
47 ms
user.css
44 ms
system.theme.css
593 ms
jquery.ui.tabs.css
561 ms
fancybox.css
583 ms
structure.css
585 ms
jquery.js
587 ms
jquery.once.js
590 ms
drupal.js
590 ms
jquery.cookie.js
888 ms
jquery.form.js
593 ms
ajax.js
1306 ms
fr_EpMxEPPva3_S5mQ-WzKl7cBY0JIZs30iuNmBiE0OnMk.js
924 ms
jquery.jcarousel.min.js
606 ms
jcarousel.js
1154 ms
base.js
860 ms
progress.js
861 ms
conversion.js
49 ms
footer_fr.css
859 ms
ajax_view.js
1261 ms
jquery.js
877 ms
jquery.main.js
868 ms
gtm.js
174 ms
fbevents.js
234 ms
141 ms
nestle_family.png
21 ms
barra_bianca.png
333 ms
nestle_shop.png
345 ms
soupe%20viande%20hache%CC%81e_.jpg
1875 ms
image26562.jpg
126 ms
image26886.jpg
1200 ms
image26512.jpg
133 ms
COVER_5_Indienne_0.jpg
455 ms
image26601.jpg
1387 ms
image26607.jpg
1310 ms
image26429_0.jpg
1501 ms
image26376.jpg
1687 ms
14-8763_MaggiCH_Pack_Bouillon_Poudre_Legumes_300g_PackshotDynFront.jpg
2402 ms
ar%C3%ACme-liquide-250g.jpg
1676 ms
Krispy_Escalope-herbes-ail_packshot_2D_1_0.jpg
1989 ms
13-8637_MaggiCH_Pack_IDEE%20pour_Tendre%20et%20Juteux_Poulet%20paprika_PackshotD....jpg
8054 ms
13-8500_MaggiCH_Pack_IDEE-pour_Classic_Emince-zurichoise_Packshot_0.jpg
4836 ms
13-8500_MaggiCH_Pack_Bouillon_Cube_Legumes_80g_PackshotDyn.jpg
1698 ms
MA_Soupe_Chalet_FR.jpg
2641 ms
Polenta%20vue%20de%20face.jpg
5403 ms
quick-lunch-Pasta-Bolo.jpg
2408 ms
kids_menus_00.jpg
3305 ms
menu-legumes.jpg
2861 ms
menu_bien_etre.jpg
3226 ms
kids_menus_01_0.jpg
3550 ms
kids_menus_02.jpg
3770 ms
kids_menus_03_0.jpg
3914 ms
Image-20.ashx_.jpeg
4444 ms
iStock_000014735785Small.jpg
5394 ms
logo-02.png
4243 ms
iStock_000026793481Small.jpg
5161 ms
iStock_000023733849Small.jpg
5319 ms
picto-volailles.png
5154 ms
picto-viandes.png
5429 ms
picto-poissons.png
5489 ms
132 ms
133 ms
picto-legumes.png
5618 ms
ble.png
5679 ms
27E741_0_0.woff
5944 ms
pfreminderpro-medium-web.woff
6999 ms
43 ms
48 ms
48 ms
analytics.js
28 ms
collect
9 ms
collect
59 ms
collect
4 ms
collect
14 ms
collect
66 ms
collect
83 ms
101 ms
27E741_1_0.woff
5757 ms
_Incapsula_Resource
5296 ms
1409
6235 ms
fromage.png
4831 ms
Maggi%20Bouillon.jpg
5117 ms
text-comment.png
4981 ms
logo-nestle.jpg
5002 ms
coopathome-logo-small.png
4988 ms
logo_leshop.jpg
5466 ms
postit-maggiclub.png
5975 ms
check.png
4796 ms
logo.png
4681 ms
sprite.png
4274 ms
sep-03.gif
4268 ms
fd-transparent-noir-2.png
4037 ms
bg-overlay-02.png
4095 ms
sep-01.gif
3473 ms
home.jpg
5602 ms
bg-search.png
3411 ms
bg-title-07.png
3504 ms
bg-title-03.png
3235 ms
btn-close.gif
2907 ms
arrow-02_noir.gif
2983 ms
bg-footer_fr.jpg
2322 ms
bg-footer_150ans_fr.png
2002 ms
_Incapsula_Resource
1519 ms
COVER_3_Epinard.jpg
3098 ms
image26957.jpg
1705 ms
image26429.jpg
1208 ms
bg-title-02.png
1280 ms
bg-overlay.png
1478 ms
structure_print.css
7 ms
maggi.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
maggi.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
maggi.ch SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maggi.ch can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed French language. Our system also found out that Maggi.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.
maggi.ch
Open Graph description is not detected on the main page of Maggi. 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: