suchprice.com website review

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

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

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

8 third-party services load with your homepage (growave.io, Google CDN and Yotpo and others), adding 1.2 MB and 495 ms of main-thread time.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

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

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

Google CDN costs a phone 112 ms of main-thread work and 296 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.

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

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

7 images could be 139 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

10 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 419 requests on a phone: scripts 1.4 MB (106), other files 1.0 MB (200) and images 736 KiB (88). Under 2 MB keeps phones on slow connections fast.

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

13 tap targets are too small or too close together to hit reliably with a finger.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There are 2 <h1> headlines (“Suchprice® 優價網” and “搜索我們的商店”). One clear main headline is easier for people and search engines.

The homepage links to 229 pages on suchprice.com and 11 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.

Your homepage links to https://suchprice.com/pages/reward-old, which answers with an error. Visitors hit a dead end and search engines drop it.

https://suchprice.com/collections/all, https://suchprice.com/collections/on-sale, https://suchprice.com/collections/cribs-toddler-beds, https://suchprice.com/collections/high-chairs-booster-seats, https://suchprice.com/collections/bottle-warmers-sterilizers and https://suchprice.com/collections/back-lumbar-support-cushions and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://suchprice.com/blogs/promotions, https://suchprice.com/pages/about-us, https://suchprice.com/collections/on-sale, https://suchprice.com/collections/cribs-toddler-beds, https://suchprice.com/collections/high-chairs-booster-seats and https://suchprice.com/collections/bottle-warmers-sterilizers and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://suchprice.com/collections/back-lumbar-support-cushions, https://suchprice.com/collections/office-chairs and https://suchprice.com/collections/table-bar-stools took over 3 s to send their HTML from our server.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 103 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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 11 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.