Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

nestle.com.tw

Nestle: Good Food Good Life 首頁 | 雀巢台灣 Nestle Taiwan

Page Load Speed

7.9 sec in total

First Response

58 ms

Resources Loaded

7.1 sec

Page Rendered

783 ms

nestle.com.tw screenshot

About Website

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

我們是全球最大的食品龍頭秉持Good Food, Good Life的企業。我們相信食物的力量可以提升生活品質滋養並豐富感官,每個人都能充分享受生活。尊重地球永續,並守護下一代的資源。尊重,是雀巢品牌價值的基石。我們致力於形塑一個更美好的世界。

Visit nestle.com.tw

Key Findings

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

Performance Metrics

nestle.com.tw performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value4,060 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

nestle.com.tw

58 ms

www.nestle.com.tw

405 ms

zh-TW

599 ms

css_mUR5wflejJ_alU6NMT3rEFH0uZXVZA8vyPI_RM4aZkM.css

450 ms

bootstrap.min.css

37 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 92% of them (78 requests) were addressed to the original Nestle.com.tw, 6% (5 requests) were made to Unpkg.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Nestle.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.3 kB (9%)

Content Size

3.5 MB

After Optimization

3.1 MB

In fact, the total size of Nestle.com.tw 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 318.6 kB

  • Original 382.8 kB
  • After minification 320.0 kB
  • After compression 64.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. This page needs HTML code to be minified as it can gain 62.7 kB, which is 16% 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 318.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 27 B

  • Original 2.6 MB
  • After minification 2.6 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

-0%

Potential reduce by 234 B

  • Original 221.9 kB
  • After minification 221.9 kB
  • After compression 221.7 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.

CSS Optimization

-0%

Potential reduce by 366 B

  • Original 210.6 kB
  • After minification 210.5 kB
  • After compression 210.2 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.com.tw has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (44%)

Requests Now

78

After Optimization

44

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

Accessibility Review

nestle.com.tw 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

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.com.tw 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

High

Missing source maps for large first-party JavaScript

SEO Factors

nestle.com.tw 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

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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