Tools & Wizards About Us
nestle.be screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

nestle.be

Nestlé Belgilux : une bonne alimentation pour une meilleure qualité de vie

Page Load Speed

2.8 sec in total

First Response

379 ms

Resources Loaded

2.3 sec

Page Rendered

205 ms

nestle.be screenshot

About Website

Welcome to nestle.be homepage info - get ready to check Nestle best content for Belgium right away, or after learning these important things about nestle.be

Nestlé, leader mondial de nutrition, santé et bien-être, possède des bureaux, des usines et des centres de recherche et développement dans le monde entier.

Visit nestle.be

Key Findings

We analyzed Nestle.be page load time and found that the first response time was 379 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

nestle.be performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value6,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

www.nestle.be

379 ms

fr

552 ms

select2.min.css

199 ms

nestle-commun.min.css

210 ms

nestle-migration.min.css

201 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 80% of them (48 requests) were addressed to the original Nestle.be, 12% (7 requests) were made to Google-analytics.com and 5% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Auth-prod.nestle.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.2 kB (24%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nestle.be main page is 1.4 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. 60% of websites need less resources to load. Images take 980.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 23.1 kB

  • Original 28.8 kB
  • After minification 24.6 kB
  • After compression 5.7 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 4.2 kB, which is 14% 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 23.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 28.5 kB

  • Original 980.1 kB
  • After minification 951.6 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. Nestle images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 128.7 kB

  • Original 229.3 kB
  • After minification 229.2 kB
  • After compression 100.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 128.7 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 155.9 kB

  • Original 191.7 kB
  • After minification 190.6 kB
  • After compression 35.8 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. Nestle.be needs all CSS files to be minified and compressed as it can save up to 155.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (59%)

Requests Now

54

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nestle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.nestle.be

www.nestle.be

379 ms

fr

fr

552 ms

select2.min.css

select2.min.css

199 ms

nestle-commun.min.css

nestle-commun.min.css

210 ms

nestle-migration.min.css

nestle-migration.min.css

201 ms

nestle-widgets.min.css

nestle-widgets.min.css

202 ms

nestle-corporate.min.css

nestle-corporate.min.css

214 ms

TableLayout.min.css

TableLayout.min.css

179 ms

owl.carousel.min.css

owl.carousel.min.css

282 ms

cookiebar.css

cookiebar.css

196 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

301 ms

modernizr.min.js

modernizr.min.js

314 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

315 ms

jquery.cycle2.carousel.min.js

jquery.cycle2.carousel.min.js

318 ms

owl.carousel.min.js

owl.carousel.min.js

318 ms

shortcut.min.js

shortcut.min.js

381 ms

analytics.js

analytics.js

395 ms

bfbs.js

bfbs.js

461 ms

select2.min.js

select2.min.js

398 ms

cookiebar_BE.js

cookiebar_BE.js

395 ms

featurestory.min.js

featurestory.min.js

399 ms

jquery.reveal.min.js

jquery.reveal.min.js

433 ms

behavior-design.min.js

behavior-design.min.js

440 ms

nestlecorporate.min.js

nestlecorporate.min.js

588 ms

ga.js

ga.js

10 ms

__utm.gif

__utm.gif

34 ms

__utm.gif

__utm.gif

23 ms

gtm.js

gtm.js

61 ms

2015%20-%20corporate-logo-150-EN.png

2015%20-%20corporate-logo-150-EN.png

662 ms

v2_layout_design.png

v2_layout_design.png

104 ms

2016%20-%20CSV%20Report%20Home%20Page.jpg

2016%20-%20CSV%20Report%20Home%20Page.jpg

216 ms

2016%20-%20Annual%20report%20Home%20%20Page.jpg

2016%20-%20Annual%20report%20Home%20%20Page.jpg

109 ms

2013FY-HomepageHighlight.jpg

2013FY-HomepageHighlight.jpg

108 ms

2015%20-%20Synerjob%20-%20Alliance%20for%20YOUth%202016%20Home%20Page.jpg

2015%20-%20Synerjob%20-%20Alliance%20for%20YOUth%202016%20Home%20Page.jpg

124 ms

Nestle-150-years-homepage.jpg

Nestle-150-years-homepage.jpg

216 ms

2015%20-%20Club%20Nestl%C3%A9%20%20Feature%20Stories.jpg

2015%20-%20Club%20Nestl%C3%A9%20%20Feature%20Stories.jpg

214 ms

Banner%20Nutrition%20Square_FR.JPG

Banner%20Nutrition%20Square_FR.JPG

215 ms

2015%20-%20Work%20at%20Nestl%C3%A9%20widget%20Home%20Page.jpg

2015%20-%20Work%20at%20Nestl%C3%A9%20widget%20Home%20Page.jpg

227 ms

2015%20-%20CSV%20Rapport%20Widget%20Home%20Page%20FR.jpg

2015%20-%20CSV%20Rapport%20Widget%20Home%20Page%20FR.jpg

266 ms

Roboto-Regular-webfont.woff

Roboto-Regular-webfont.woff

275 ms

Roboto-Medium-webfont.woff

Roboto-Medium-webfont.woff

291 ms

Roboto-Light-webfont.woff

Roboto-Light-webfont.woff

323 ms

popUpVideoTop.png

popUpVideoTop.png

306 ms

loading.gif

loading.gif

314 ms

facebook_off.png

facebook_off.png

349 ms

facebook_on.png

facebook_on.png

368 ms

twitter_off.png

twitter_off.png

503 ms

twitter_on.png

twitter_on.png

408 ms

analytics.js

analytics.js

3 ms

collect

collect

18 ms

collect

collect

69 ms

collect

collect

18 ms

collect

collect

22 ms

collect

collect

59 ms

collect

collect

59 ms

_Incapsula_Resource

_Incapsula_Resource

166 ms

cookie_background.png

cookie_background.png

224 ms

Roboto-Black-webfont.woff

Roboto-Black-webfont.woff

223 ms

_Incapsula_Resource

_Incapsula_Resource

19 ms

print.min.css

print.min.css

112 ms

Accessibility Review

nestle.be accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nestle.be best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nestle.be SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nestle.be 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 Nestle.be 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.

Social Sharing Optimization

nestle.be

Open Graph data is detected on the main page of Nestle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: