pakawellness.com website review

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 3.2 MB and 819 ms of main-thread time.

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

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

About 464 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

Shopify costs a phone 310 ms of main-thread work and 611 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.

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

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

Google Tag Manager costs a phone 189 ms of main-thread work and 502 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.

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

33 KiB could be saved by minifying CSS.

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

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

Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need.

8 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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PAKA Wellness - 香港人養生系統”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 141 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 3.4 MB in 142 requests on a phone: scripts 1.4 MB (95), fonts 1.3 MB (22) and stylesheets 349 KiB (3). Under 2 MB keeps phones on slow connections fast.

2 images (117 KiB) 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.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 2 <h1> headlines (“#1 個人化養生方案” and “#1 個人化養生方案”). One clear main headline is easier for people and search engines.

The homepage links to 70 pages on pakawellness.com and 10 external pages.

https://www.pakawellness.com/buy/deepzzz, https://www.pakawellness.com/buy/queen, https://www.pakawellness.com/buy/king, https://www.pakawellness.com/buy/tea-dampness, https://www.pakawellness.com/offers/pick and https://www.pakawellness.com/buy/pick are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.pakawellness.com/buy/deepzzz, https://www.pakawellness.com/buy/queen and https://www.pakawellness.com/buy/king all use the title “購買 | PAKA Wellness”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pakawellness.com/buy/deepzzz, https://www.pakawellness.com/buy/queen and https://www.pakawellness.com/buy/king have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pakawellness.com/guide, https://www.pakawellness.com/queen-guide and https://www.pakawellness.com/king-guide have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pakawellness.com/queen, https://www.pakawellness.com/king, https://www.pakawellness.com/tea, https://www.pakawellness.com/tea/liver, https://www.pakawellness.com/guide and https://www.pakawellness.com/queen-guide and 1 other 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.

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

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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