kpthai.com website review

62 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).

23 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.

About 743 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

About 317 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Your mobile performance score is 50 (desktop: 68). Pages that score under 90 lose visitors before the first paint.

Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).

70 KiB could be saved by minifying CSS.

50 KiB could be saved by minifying JavaScript.

3 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Google Maps and YouTube), adding 219 KiB and 42 ms of main-thread time.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The first text or image appears after 6.1 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 15.1 s. Good is under 3.8 s.

The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.

5 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.9 MB in 68 requests on a phone: images 4.3 MB (31), scripts 1.1 MB (22) and stylesheets 348 KiB (11). Under 2 MB keeps phones on slow connections fast.

I0000269.png weighs 1.4 MB. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example I0000244.png at 800 px wide, shown at 150 px. Resized copies would save about 1.2 MB.

15 images (4.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

14 images further down the page (3.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 links inside paragraphs rely on colour alone to stand out.

1 tap target is too small or too close together to hit reliably with a finger.

35 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

5 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h5, h1 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 6 characters: “kewpie”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“NEW PRODUCT”, “RECIPES” and “PRODUCT CATEGORIES”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://kpthai.com/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 34 pages on kpthai.com and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://kpthai.com/en, / and https://kpthai.com/th all use the title “kewpie”. Search engines can't tell which page to show for a search, so each competes with the others.

/, https://kpthai.com/en/category, https://kpthai.com/en/news/knowledge-and-tips, https://kpthai.com/en/job and https://kpthai.com/th have no meta description, so Google writes the search snippet from whatever text it finds.

https://kpthai.com/en/cookie, https://kpthai.com/en/privacy, https://kpthai.com/en/product-detail/Meatsauce, https://kpthai.com/en/product-detail/Tunacreamsauce and https://kpthai.com/en/product-detail/CreamSauce have no <h1> headline, so visitors and search engines get no clear main topic.

https://kpthai.com/en/category, https://kpthai.com/en/news/news, https://kpthai.com/th and https://kpthai.com/en/news-detail/1/N0000227 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/, https://kpthai.com/en/category, https://kpthai.com/en/news/recipe and https://kpthai.com/en/news/knowledge-and-tips took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://kpthai.pdpanetka.com/api/cookie/cookiesetting?key=Mdd3cr0tCDfsUpfhJ9pRvA%3d%3d' violates the fol…”.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 183 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 2 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.