vietmap.vn website review

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

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

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

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

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and openai.com and others), adding 2.9 MB and 462 ms of main-thread time.

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

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

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

dktcdn.net costs a phone 8 ms of main-thread work and 2.2 MB 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.

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

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.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.71 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 73 requests on a phone: images 2.1 MB (32), scripts 738 KiB (19) and fonts 158 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

5 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields do not have accessible names (2 elements).

ARIA toggle fields do not have accessible names (1 element).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Elements with role="none" or role="presentation" have conflicts (1 element).

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 83 pages on vietmap.vn and 38 external pages.

https://vietmap.vn/gioi-thieu-map and https://vietmap.vn/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://vietmap.vn/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

https://vietmap.vn/gioi-thieu, https://vietmap.vn/gioi-thieu-map, https://vietmap.vn/collections/all, https://vietmap.vn/camera-hanh-trinh, https://vietmap.vn/thiet-bi-dan-duong-gps and https://vietmap.vn/man-hinh-giai-tri-oto and 7 others took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 error was 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.

3 images are served at too low a resolution for sharp phone screens.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 735 words of visible text.

Before a visitor clicks anything, the page loads 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 13 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.