Tools & Wizards About Us

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

nestle.co.th

เนสท์เล่ ไทย Good food, Good Life เพื่อคุณภาพชีวิตที่ดี

Page Load Speed

4.1 sec in total

First Response

498 ms

Resources Loaded

3.4 sec

Page Rendered

214 ms

About Website

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

เปิดพลังแห่งอาหารเพิ่มพูนคุณภาพชีวิตที่ดีกับเนสท์เล่ ไทย เพื่อความยั่งยืนด้านอาหาร และการเปลี่ยนแปลงต่อผู้คน ชุมชน สิ่งแวดล้อมโลก

Visit nestle.co.th

Key Findings

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

Performance Metrics

nestle.co.th performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value7,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.346

32/100

15%

TTI (Time to Interactive)

Value21.9 s

2/100

10%

Network Requests Diagram

www.nestle.co.th

498 ms

www.nestle.co.th

143 ms

th

1424 ms

select2.min.css

46 ms

nestle-commun.min.css

54 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 84% of them (59 requests) were addressed to the original Nestle.co.th, 6% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nestle.co.th.

Page Optimization Overview & Recommendations

Page size can be reduced by 345.3 kB (16%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nestle.co.th main page is 2.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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.9 kB

  • Original 50.9 kB
  • After minification 44.7 kB
  • After compression 8.9 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 6.2 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 41.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 20.3 kB

  • Original 1.7 MB
  • After minification 1.7 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 127.4 kB

  • Original 227.4 kB
  • After minification 227.3 kB
  • After compression 99.9 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 127.4 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 155.6 kB

  • Original 191.1 kB
  • After minification 190.1 kB
  • After compression 35.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. Nestle.co.th needs all CSS files to be minified and compressed as it can save up to 155.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (48%)

Requests Now

63

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nestle.co.th accessibility score

84

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

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

nestle.co.th SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

    TH

  • Language Claimed

    TH

  • Encoding

    UTF-8

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