tamsuamy.com website review

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

10 images could be 1.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.8 s faster on a phone.

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

Reduce initial server response time. Google estimates savings of 903 ms on a phone.

The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

About 58 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.

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

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

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

5 third-party services load with your homepage (Facebook, JSDelivr CDN and Google Fonts and others), adding 683 KiB and 206 ms of main-thread time.

About 227 KiB of JavaScript is downloaded but never used on this page.

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

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

Polyfills for old browsers add 25 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.

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

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “1”. Most of its time is resource load delay (4.9 s).

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

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

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 7.5 MB in 198 requests on a phone: images 6.2 MB (123), scripts 661 KiB (23) and fonts 374 KiB (17). Under 2 MB keeps phones on slow connections fast.

22 images (1.5 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.

2 images are downloaded at several times the size a phone draws them, for example tamsuamylogo.png at 1,792 px wide, shown at 105 px. Resized copies would save about 471 KiB.

5 images further down the page (756 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 56 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.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

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

Your canonical URL points to website-13bdb9b3.aie.vtc.mybluehost.me, not tamsuamy.com, so Google may credit that host instead.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

3 links have no real href, so search engines can't follow them.

The homepage links to 265 pages on tamsuamy.com and 2 external pages.

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.

There is no https://tamsuamy.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://tamsuamy.com/wishlist, https://tamsuamy.com/product-category/sua, https://tamsuamy.com/product-category/sua/sua-0-12, https://tamsuamy.com/product-category/sua/sua-0-12/be-binh-thuong, https://tamsuamy.com/product-category/sua/sua-0-12/nhe-can and https://tamsuamy.com/product-category/sua/sua-0-12/he-tieu-hoa-nhay-cam and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tamsuamy.com/wishlist, https://tamsuamy.com/product-category/sua, https://tamsuamy.com/product-category/sua/sua-0-12, https://tamsuamy.com/product-category/sua/sua-0-12/be-binh-thuong, https://tamsuamy.com/product-category/sua/sua-0-12/nhe-can and https://tamsuamy.com/product-category/sua/sua-0-12/he-tieu-hoa-nhay-cam and 6 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID”.

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: 7 testimonial or review blocks. 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 890 words of visible text.

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