Website review, no card needed
lpbank.com.vn website review
Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 89 checks
This review found 47 issues worth fixing on lpbank.com.vn, 22 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 5.2 s |
| Aug 8, 2026 | 5.9 s |
| Aug 15, 2026 | 6.1 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 6.1 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 6.1 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.0 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 5.9 s |
| Oct 24, 2026 | 6.1 s |
| Oct 31, 2026 | 6.6 s |
| Nov 7, 2026 | 6.7 s |
| Nov 14, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 276 ms |
| Jun 6, 2026 | 274 ms |
| Jun 13, 2026 | 267 ms |
| Jun 20, 2026 | 265 ms |
| Jun 27, 2026 | 283 ms |
| Jul 4, 2026 | 294 ms |
| Jul 11, 2026 | 314 ms |
| Jul 18, 2026 | 325 ms |
| Jul 25, 2026 | 301 ms |
| Aug 1, 2026 | 281 ms |
| Aug 8, 2026 | 253 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 239 ms |
| Aug 29, 2026 | 241 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 247 ms |
| Sep 19, 2026 | 244 ms |
| Sep 26, 2026 | 233 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 226 ms |
| Oct 31, 2026 | 248 ms |
| Nov 7, 2026 | 253 ms |
| Nov 14, 2026 | 246 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
How it loaded on a phone
2.0 s
4.0 s
6.0 s
7.9 s
9.9 s
11.9 s
13.9 s
15.9 s
Speed
Improve image delivery
21.2 s · 12.1 MB20 images could be 12.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 21.2 s faster on a phone.
Reduce unused JavaScript
6.8 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 2.5 MB12 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).
Reduce unused CSS
2.3 s · 447 KiBAbout 447 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 849 KiB 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.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 3.5 MB and 1.3 s of main-thread time.
Font display
750 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).
Minify CSS
300 ms · 95 KiB95 KiB could be saved by minifying CSS.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 327 ms. During a long task the page ignores taps.
Facebook adds 281 ms
281 msFacebook costs a phone 281 ms of main-thread work and 255 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.
fpt.ai adds 2 ms
2 msfpt.ai costs a phone 2 ms of main-thread work and 2.4 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.
Minify JavaScript
150 ms · 35 KiB35 KiB could be saved by minifying JavaScript.
Legacy JavaScript
50 ms · 75 KiBPolyfills for old browsers add 75 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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: 450 ms
450 msYour server sent the HTML in 450 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 68.0 s
68.0 sYour largest element takes 68.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 69.0 s
69.0 sThe page becomes fully interactive after 69.0 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 307 ms
307 msReal visitors wait 307 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.9 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 276 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 624 ms
624 msReal visitors wait 624 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 22.5 MB in 112 requests
22.5 MBYour homepage downloads 22.5 MB in 112 requests on a phone: images 14.6 MB (50), media 4.4 MB (1) and scripts 2.6 MB (31). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 5.9 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
6.0 MB11 images are downloaded at several times the size a phone draws them, for example bc89dd97-8647-477f-821a-7bd07a91016b at 8,000 px wide, shown at 80 px. Resized copies would save about 6.0 MB.
13 images in older formats
13 images (7.6 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.
1 image below the first screen load straight away
1 image further down the page (82 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.4 g of CO₂ per visit
6.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.39 g of CO₂e: 766.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (3 elements)
Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
81 links crawlers can't follow
81 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (36 characters)
Your meta description is only 36 characters: “LPBank - Ngân hàng Lộc Phát Việt Nam”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
66 internal links, 19 external
The homepage links to 66 pages on lpbank.com.vn and 19 external pages.
3 checks passed
Title: 36 characters
Your title is a healthy 36 characters: “LPBank - Ngân hàng Lộc Phát Việt Nam”.
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://lpbank.com.vn/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://lpbank.com.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (901 words), so crawlers that don't run JavaScript still read it.
Other pages
5 linked pages are broken
Your homepage links to https://lpbank.com.vn/the, https://lpbank.com.vn/tai-khoan, https://lpbank.com.vn/tiet-kiem, https://lpbank.com.vn/cho-vay and https://lpbank.com.vn/chuyen-tien-quoc-te, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages share a title
https://lpbank.com.vn/ca-nhan, https://lpbank.com.vn/khach-hang-uu-tien, https://lpbank.com.vn/ve-lpbank and / all use the title “LPBank - Ngân hàng Lộc Phát Việt Nam”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
https://lpbank.com.vn/khach-hang-uu-tien, https://lpbank.com.vn/ve-lpbank and / use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://lpbank.com.vn/khach-hang-uu-tien has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://lpbank.com.vn/khach-hang-uu-tien, https://lpbank.com.vn/ve-lpbank and / took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 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 3 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 791 words of copy
The homepage carries about 791 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
10 other companies contacted
Loading the homepage contacts 10 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 lpbank.com.vn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Analytics
- Google Tag Manager
- Hosting
- Loc Phat Vietnam Joint Stock Commercial Bank
Company
- Founded
- 2008
- Headquarters
- Hanoi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on lpbank.com.vn, including 21 speed issues, 5 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.