baoquanhoa.com website review

About 4.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 39.3 s faster on a phone.

130 files are served with short cache lifetimes, so returning visitors download them again (12.4 MB).

YouTube costs a phone 3.3 s of main-thread work and 8.7 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.

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

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

12 images could be 441 KiB 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.

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

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

7 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 9.5 MB and 3.5 s of main-thread time.

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

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

Google Fonts costs a phone 0 ms of main-thread work and 312 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.

16 KiB could be saved by minifying JavaScript.

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

9 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 22.7 MB in 282 requests on a phone: images 12.1 MB (78), scripts 8.6 MB (84) and stylesheets 947 KiB (46). Under 2 MB keeps phones on slow connections fast.

40 images (5.7 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.

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

1 image is downloaded at several times the size a phone draws it, for example logo-da-thong-bao-bct.png at 1,024 px wide, shown at 137 px. Resized copies would save about 195 KiB.

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

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

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

4 frames have no title, so screen-reader users cannot tell what they contain.

1 element hidden from screen readers can still receive keyboard focus.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h5, h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 6 <h1> headlines (“1. GÓI DƯỠNG HOA TƯƠI LONGLIFE NHẬP KHẨU ISAREL C…”, “THỰC TẾ GÓI DƯỠNG HOA LONGLIFE SAU 10 NGÀY CẮM BÌ…” and “BÍ QUYẾT SHOP HOA BẢO QUẢN HOA CẮM XỐP, CẮM LẴNG …”). One clear main headline is easier for people and search engines.

Structured data found (ImageObject, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 321 pages on baoquanhoa.com and 48 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://baoquanhoa.com/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.

https://baoquanhoa.com/san-pham-israel, https://baoquanhoa.com/thuoc-duong-hoa-tuoi-longlife-goi-5gr, https://baoquanhoa.com/bot-cam-hoa-danh-cho-shop-hoa-florist, https://baoquanhoa.com/bao-quan-hoa-tuoi-tai-cho-si-tog-galileo, https://baoquanhoa.com/bao-quan-hoa-cho-si-longlife-sl and https://baoquanhoa.com/mau-nhuom-hoa-tuoi-nhap-khau-bot-va-nuoc and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://baoquanhoa.com/san-pham-israel, https://baoquanhoa.com/thuoc-duong-hoa-tuoi-longlife-goi-5gr, https://baoquanhoa.com/bot-cam-hoa-danh-cho-shop-hoa-florist, https://baoquanhoa.com/bao-quan-hoa-cho-si-longlife-sl, https://baoquanhoa.com/mau-nhuom-hoa-tuoi-nhap-khau-bot-va-nuoc and https://baoquanhoa.com/son-xit-mau-hoa-tuoi-nhap-khau-uc and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://baoquanhoa.com/son-xit-mau-hoa-tuoi-nhap-khau-uc took over 3 s to send its HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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 4,667 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 5 cookies, 1 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.