Website review, no card needed

truehy.hk logo

truehy.hk website review

Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 73 checks

This review found 28 issues worth fixing on truehy.hk, 6 of them high impact, across 73 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of truehy.hk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. truehy.hk at 0.4 s0.4 s
  2. truehy.hk at 0.8 s0.8 s
  3. truehy.hk at 1.1 s1.1 s
  4. truehy.hk at 1.5 s1.5 s
  5. truehy.hk at 1.9 s1.9 s
  6. truehy.hk at 2.3 s2.3 s
  7. truehy.hk at 2.6 s2.6 s
  8. truehy.hk at 3.0 s3.0 s

Speed

5 to fix74
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    300 ms · 335 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and appstle.com and others), adding 1.0 MB and 197 ms of main-thread time.

  • Shopify adds 111 ms

    111 ms

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

  • Improve image delivery

    150 ms · 64 KiB

    5 images could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    150 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

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

  • Use efficient cache lifetimes

    8 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 420 ms of it running JavaScript. That is comfortably low.

  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix68
  • Largest Contentful Paint: 7.4 s

    7.4 s

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

  • Time to Interactive: 11.3 s

    11.3 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 22 ms

    22 ms

    Scripts block the page for only 22 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix69
  • Page weight: 2.8 MB in 222 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 222 requests on a phone: other files 777 KiB (95), scripts 739 KiB (67) and images 642 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    m_th.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).

  • 6 images in older formats

    6 images (714 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.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9495
  • 33 text elements with low contrast

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

  • 15 tap targets too small

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

  • All page content should be contained by landmarks (4 elements)

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9285
  • Meta description is long (186 characters)

    Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 51 internal links, 5 external

    The homepage links to 51 pages on truehy.hk and 5 external pages.

5 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Electrolyte Drinks Hong Kong | Truly Hydrate”.

  • Canonical URL set

    The canonical URL is https://trulyhydrate.com.hk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://trulyhydrate.com.hk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,144 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://trulyhydrate.com.hk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 10 pages without a meta description

    https://trulyhydrate.com.hk/collections/all, https://trulyhydrate.com.hk/pages/why-hydration-matters, https://trulyhydrate.com.hk/pages/reviews, https://trulyhydrate.com.hk/pages/perks, https://trulyhydrate.com.hk/pages/true-hydration and https://trulyhydrate.com.hk/pages/cellular-hydration and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://trulyhydrate.com.hk/products/unsweetened-lemon-water-320ml and https://trulyhydrate.com.hk/products/lemonade-lemongrass-water-320ml use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://trulyhydrate.com.hk/collections/all, https://trulyhydrate.com.hk/collections/shop, https://trulyhydrate.com.hk/pages/true-hydration and https://trulyhydrate.com.hk/pages/cellular-hydration have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://trulyhydrate.com.hk/pages/reviews has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9291
  • 9 small tap targets

    9 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

3 to fix67
  • 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.

  • No analytics detected

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

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

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

  • About 794 words of copy

    The homepage carries about 794 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop”, “Shop Hydration” and “LEARN MORE”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks and 1 trust badge.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 truehy.hk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Wiser Upsell Cross Sell · Klaviyo Email Marketing Sms · Avada Seo Suite · Judge Me Reviews · Appstle Loyalty · weglot.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on truehy.hk, including 8 speed issues, 4 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25