Website review, no card needed

lacviet.vn logo

lacviet.vn website review

Visit site (opens in a new tab)Reviewed 27 October 202650 issues · 96 checks

This review found 50 issues worth fixing on lacviet.vn, 24 of them high impact, across 96 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.9 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.3 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
263 ms139 msMay 9Oct 24249 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026160 ms
May 16, 2026155 ms
May 23, 2026155 ms
May 30, 2026153 ms
Jun 6, 2026159 ms
Jun 13, 2026168 ms
Jun 20, 2026170 ms
Jun 27, 2026166 ms
Jul 4, 2026162 ms
Jul 11, 2026163 ms
Jul 18, 2026161 ms
Jul 25, 2026164 ms
Aug 1, 2026168 ms
Aug 8, 2026181 ms
Aug 15, 2026183 ms
Aug 22, 2026193 ms
Aug 29, 2026193 ms
Sep 5, 2026192 ms
Sep 12, 2026206 ms
Sep 19, 2026216 ms
Sep 26, 2026231 ms
Oct 3, 2026241 ms
Oct 10, 2026241 ms
Oct 17, 2026246 ms
Oct 24, 2026249 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lacviet.vn (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lacviet.vn at 1.7 s1.7 s
  2. lacviet.vn at 3.4 s3.4 s
  3. lacviet.vn at 5.1 s5.1 s
  4. lacviet.vn at 6.7 s6.7 s
  5. lacviet.vn at 8.4 s8.4 s
  6. lacviet.vn at 10.1 s10.1 s
  7. lacviet.vn at 11.8 s11.8 s
  8. lacviet.vn at 13.5 s13.5 s

Speed

11 to fix30
  • Render-blocking requests

    8.7 s

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

  • Reduce unused CSS

    3.1 s · 712 KiB

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

  • Improve image delivery

    1.1 s · 2.0 MB

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

  • Reduce unused JavaScript

    2.1 s · 926 KiB

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

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 4.4 s

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

  • 3,701 HTML elements

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

  • Use efficient cache lifetimes

    950 ms · 756 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and codx.vn and others), adding 1.6 MB and 655 ms of main-thread time.

  • Google Tag Manager adds 240 ms

    240 ms

    Google Tag Manager costs a phone 240 ms of main-thread work and 349 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.

  • codx.vn adds 123 ms

    123 ms

    codx.vn costs a phone 123 ms of main-thread work and 796 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.

  • Font display

    250 ms

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

  • Minify CSS

    150 ms · 26 KiB

    26 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • 11 long tasks on the main thread

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

  • Minify JavaScript

    33 KiB

    33 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 446 ms

    446 ms

    Your server sent the HTML in 446 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 7.7 s

    7.7 s

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

  • Largest Contentful Paint: 20.0 s

    20.0 s

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

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 34.2 s

    34.2 s

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

  • Cumulative Layout Shift: 0.398

    0.398

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

  • Real-user LCP: 3.2 s

    3.2 s

    Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 251 ms

    251 ms

    Real visitors wait 251 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 57% slower for real visitors

    +57%

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

  • Real-user FCP: 2.9 s

    2.9 s

    Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 25 images without width and height

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

  • Total Blocking Time: 284 ms

    284 ms

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

1 checks passed
  • Real-user CLS: 0.07

    0.07

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

Images and page weight

5 to fix33
  • Page weight: 9.2 MB in 236 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 236 requests on a phone: images 5.5 MB (98), scripts 2.1 MB (54) and stylesheets 1.1 MB (60). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    689 KiB

    11 images are downloaded at several times the size a phone draws them, for example add-us-as-preferred-source-on-google-e1782464440741.png at 389 px wide, shown at 108 px. Resized copies would save about 689 KiB.

  • 12 images in older formats

    12 images (2.2 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.

  • 13 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    bg-cong-nghe-AI-768x430.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 2.6 g of CO₂ per visit

    2.61 g

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

Accessibility

12 to fixGoogle 7584
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 81 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 10 images without alt text

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

  • All page content should be contained by landmarks (13 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

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

  • ARIA role should be appropriate for the element (14 elements)

    ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • Meta description is long (229 characters)

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

  • 348 internal links, 60 external

    The homepage links to 348 pages on lacviet.vn and 60 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Lạc Việt – Công ty cung cấp giải pháp chuyển đổi số TOÀN DIỆN”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Lạc Việt - Công ty cung cấp giải pháp chuyển đổi số TOÀN DIỆN”.

  • Canonical URL set

    The canonical URL is https://lacviet.vn/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and Place.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://lacviet.vn/sitemap_index.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,814 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://lacviet.vn/llms.txt (64 KiB, 142 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

3 to fix63
  • 2 linked pages are broken

    Your homepage links to https://lacviet.vn/chuyen-doi-so-nganh-duoc and https://lacviet.vn/kien-thuc-quan-tri, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 linked page hidden from search

    https://lacviet.vn/giai-phap-quan-ly-nang-luong-va-giam-phat-thai-carbon is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://lacviet.vn/khach-hang has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://lacviet.vn/giai-phap-quan-ly-nang-luong-va-giam-phat-thai-carbon, https://lacviet.vn/giai-phap-chuyen-doi-so, https://lacviet.vn/chuyen-doi-so-nganh-logistics and https://lacviet.vn/chuyen-doi-so-trong-giao-duc took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 11 small tap targets

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

  • 1 low-resolution image

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • No call to action on the first screen

    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 calls to action

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

  • Local business without LocalBusiness data

    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.

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

  • No risk reducer

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

  • About 2,045 words of copy

    The homepage carries about 2,045 words of visible text.

4 checks passed
  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks, 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 5 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar 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.

  • 3 cookies set on arrival

    3

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

  • No consent tool detected

    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.

  • 13 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lacviet.vn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Quang Trung Software City Development Company

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on lacviet.vn, including 24 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25