sapo.vn website review

Google Tag Manager costs a phone 1.6 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 37 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.4 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Freshchat and Facebook and others), adding 2.6 MB and 2.4 s of main-thread time.

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

About 1.0 MB of JavaScript is downloaded but never used on this page.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

Freshchat costs a phone 449 ms of main-thread work and 885 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.

11 files are served with short cache lifetimes, so returning visitors download them again (409 KiB).

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

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

The page has 2,025 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

15 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nền tảng quản lý bán hàng hợp kênh được sử dụng nhiều nhất …”.

Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 158 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.1 MB in 169 requests on a phone: media 4.9 MB (3), images 2.7 MB (69) and scripts 2.6 MB (39). Under 2 MB keeps phones on slow connections fast.

13 images (2.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.

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

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

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

Heading levels should only increase by one: 1 element on the page fails 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.

Your title is 67 characters, so Google will cut it off around 60: “Nền tảng quản lý bán hàng hợp kênh được sử dụng nhiều nhất Việt Nam”.

The homepage links to 104 pages on sapo.vn and 63 external pages.

There is no https://www.sapo.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.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 10 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.