Report Summary

  • 12

    Performance

    Renders faster than
    32% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 89

    SEO

    Google-friendlier than
    72% of websites

nestle.es

Nutrición, salud y bienestar | Nestlé

Page Load Speed

3.7 sec in total

First Response

330 ms

Resources Loaded

3.1 sec

Page Rendered

228 ms

nestle.es screenshot

About Website

Click here to check amazing Nestle content for Spain. Otherwise, check out these important facts you probably never knew about nestle.es

En Nestlé España tenemos un reto muy claro: contribuir a la nutrición, la salud y el bienestar de las personas.

Visit nestle.es

Key Findings

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

Performance Metrics

nestle.es performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.359

30/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

www.nestle.es

330 ms

es

1317 ms

select2.min.css

56 ms

nestle-commun.min.css

58 ms

nestle-migration.min.css

63 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Nestle.es, 81% (75 requests) were made to Empresa.nestle.es and 8% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Empresa.nestle.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.9 kB (23%)

Content Size

1.6 MB

After Optimization

1.2 MB

In fact, the total size of Nestle.es main page is 1.6 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 36.0 kB

  • Original 44.7 kB
  • After minification 39.2 kB
  • After compression 8.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 5.5 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 36.0 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 34.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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 132.1 kB

  • Original 234.1 kB
  • After minification 234.0 kB
  • After compression 102.0 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 132.1 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 167.4 kB

  • Original 207.8 kB
  • After minification 205.4 kB
  • After compression 40.4 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.es needs all CSS files to be minified and compressed as it can save up to 167.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (52%)

Requests Now

88

After Optimization

42

The browser has sent 88 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 25 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

nestle.es accessibility score

76

Accessibility Issues

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-*] attributes do not match their roles

High

[role] values are not valid

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.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nestle.es SEO score

89

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nestle.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Nestle.es 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

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: