Website review, no card needed
brother.com.vn website review
Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 82 checks
This review found 37 issues worth fixing on brother.com.vn, 6 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 221 ms |
| May 9, 2026 | 220 ms |
| May 16, 2026 | 224 ms |
| May 23, 2026 | 228 ms |
| May 30, 2026 | 230 ms |
| Jun 6, 2026 | 228 ms |
| Jun 13, 2026 | 224 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 236 ms |
| Jul 11, 2026 | 256 ms |
| Jul 18, 2026 | 267 ms |
| Jul 25, 2026 | 272 ms |
| Aug 1, 2026 | 268 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 278 ms |
| Aug 22, 2026 | 288 ms |
| Aug 29, 2026 | 295 ms |
| Sep 5, 2026 | 309 ms |
| Sep 12, 2026 | 315 ms |
| Sep 19, 2026 | 314 ms |
| Sep 26, 2026 | 317 ms |
| Oct 3, 2026 | 314 ms |
| Oct 10, 2026 | 299 ms |
| Oct 17, 2026 | 329 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.9 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 2.5 MB and 1.5 s of main-thread time.
Use efficient cache lifetimes
600 ms · 510 KiB68 files are served with short cache lifetimes, so returning visitors download them again (510 KiB).
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 48). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 740 ms
740 msGoogle Tag Manager costs a phone 740 ms of main-thread work and 1.1 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.
Facebook adds 400 ms
400 msFacebook costs a phone 400 ms of main-thread work and 432 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.
Reduce unused CSS
300 ms · 90 KiBAbout 90 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.
Improve image delivery
300 ms · 80 KiB2 images could be 80 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 126 ms
126 msGoogle CDN costs a phone 126 ms of main-thread work and 699 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.
Render-blocking requests
200 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.
Legacy JavaScript
41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Real-user INP: 261 ms
261 msReal visitors wait 261 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 221 ms to 329 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 566 ms
566 msScripts block taps and scrolling for 566 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.1
0.1The layout barely moves while loading (CLS 0.1, good is under 0.1).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.3 MB in 143 requests
3.3 MBYour homepage downloads 3.3 MB in 143 requests on a phone: scripts 2.8 MB (45), images 289 KiB (44) and stylesheets 122 KiB (6). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
home-promo-1.webp 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).
1 image far larger than shown
28 KiB1 image is downloaded at several times the size a phone draws it, for example vn_banner_v3.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 28 KiB.
About 0.9 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 113.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
111 internal links, 12 external
The homepage links to 111 pages on brother.com.vn and 12 external pages.
7 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “Brother- Thương hiệu đáng tin cậy trong lĩnh vực sản xuất, kinh doanh máy in văn phòng, máy scan, máy in nhãn và máy ma…”.
One H1 headline
Your main headline reads: “Tối đa hóa hiệu suất & giảm thiểu chi phí”.
Title: 56 characters
Your title is a healthy 56 characters: “Chào mừng quý khách đến với website của Brother Việt Nam”.
Canonical URL set
The canonical URL is https://www.brother.com.vn/vi-vn.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.brother.com.vn/sitemap.xml.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
There is no https://www.brother.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
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (539 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.brother.com.vn/vi-vn/scanners and https://www.brother.com.vn/vi-vn/scanners/all-scanners all use the title “Máy quét | Brother Việt Nam”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.brother.com.vn/vi-vn/supplies has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 204 words
The homepage has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Download Drivers, Manuals, & FAQs”.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
23 other companies contacted
Loading the homepage contacts 23 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 brother.com.vn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on brother.com.vn, including 19 speed issues, 2 SEO issues and 6 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.