thacogroup.vn website review

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

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

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

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

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

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

About 119 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 510 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Cloudflare CDN and others), adding 1.1 MB and 290 ms of main-thread time.

FontAwesome CDN costs a phone 5 ms of main-thread work and 485 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

43 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.

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

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

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

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

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

2 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 25.3 MB in 104 requests on a phone: images 23.9 MB (47), scripts 634 KiB (22) and fonts 573 KiB (5). Under 2 MB keeps phones on slow connections fast.

11 images weigh 20.3 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example banner-1920-17.png at 1,920 px wide, shown at 390 px. Resized copies would save about 11.1 MB.

22 images (23.3 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.

6 images further down the page (9.9 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 7.16 g of CO₂e: 859.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

19 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 11 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

There are 7 <h1> headlines (“THACO đồng hành cùng Diễn đàn Kinh tế Mùa thu 2026”, “Nữ CBNV THACO rạng rỡ chào mừng Ngày Phụ nữ Việt …” and “Dấu ấn THACO và Hyundai Rotem tại VRT&CON’ 2026”). 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.

Your meta description is 389 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 99 pages on thacogroup.vn and 27 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.

There is no https://thacogroup.vn/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/ and https://thacogroup.vn/thong-tin-co-dong all use the title “THACO - CÔNG TY CỔ PHẦN TẬP ĐOÀN TRƯỜNG HẢI”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thacogroup.vn/lien-he, https://thacogroup.vn/gioi-thieu, https://thacogroup.vn/van-hoa-thaco, https://thacogroup.vn/linh-vuc-hoat-dong/o-to, https://thacogroup.vn/linh-vuc-hoat-dong/nong-nghiep and https://thacogroup.vn/linh-vuc-hoat-dong/co-khi-cong-nghiep-ho-tro and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://thacogroup.vn/thong-tin-co-dong, https://thacogroup.vn/tin-tuc, https://thacogroup.vn/tap-chi and https://thacogroup.vn/su-kien have no <h1> headline, so visitors and search engines get no clear main topic.

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

25 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 1,239 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 5 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.