Website review, no card needed

hktvmall.com logo

hktvmall.com website review

Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 85 checks

This review found 42 issues worth fixing on hktvmall.com, 13 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.7 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
99 ms83 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202695 ms
May 23, 202696 ms
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202695 ms
Jun 27, 202693 ms
Jul 4, 202690 ms
Jul 11, 202687 ms
Jul 18, 202686 ms
Jul 25, 202686 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202686 ms
Aug 22, 202685 ms
Aug 29, 202685 ms
Sep 5, 202685 ms
Sep 12, 202685 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202688 ms
Oct 24, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of hktvmall.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hktvmall.com at 1.0 s1.0 s
  2. hktvmall.com at 2.1 s2.1 s
  3. hktvmall.com at 3.1 s3.1 s
  4. hktvmall.com at 4.1 s4.1 s
  5. hktvmall.com at 5.1 s5.1 s
  6. hktvmall.com at 6.2 s6.2 s
  7. hktvmall.com at 7.2 s7.2 s
  8. hktvmall.com at 8.2 s8.2 s

Speed

6 to fix73
  • Render-blocking requests

    1.7 s

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

  • Font display

    1.3 s

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

  • 7,420 HTML elements

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

  • Mobile performance score: 73

    73/100

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

  • Improve image delivery

    450 ms · 186 KiB

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

  • Use efficient cache lifetimes

    250 KiB

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

  • Reduce unused JavaScript

    173 KiB

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

  • 1 long task on the main thread

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

  • Minify JavaScript

    54 KiB

    54 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    26 KiB

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

  • Reduce unused CSS

    23 KiB

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

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (shoalter.com), adding 1 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 383 ms

    383 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.30

    0.30

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

  • Speed Index: 10.0 s

    10.0 s

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

  • Cumulative Layout Shift: 0.218

    0.218

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20261031_1101_fa_15off_slidera_globechic”. Most of its time is resource load duration (2.1 s).

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

6 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 799 ms

    799 ms

    Real visitors wait 799 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • Total Blocking Time: 9 ms

    9 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.27 g

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

1 checks passed
  • Page weight: 989 KiB in 57 requests

    989 KiB

    Your homepage downloads 989 KiB in 57 requests on a phone: scripts 451 KiB (16), images 362 KiB (11) and HTML 85 KiB (1). That is a lean page.

Accessibility

11 to fixGoogle 5756
  • Invalid ARIA attributes

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

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (1 element).

  • No main landmark

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

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (3 elements).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 tap target too small

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (1 element).

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 4 automated accessibility rules passed

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

SEO

4 to fixGoogle 8577
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (17 characters)

    Your title is only 17 characters: “HKTVmall 香港最大網購平台”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 135 internal links, 29 external

    The homepage links to 135 pages on hktvmall.com and 29 external pages.

5 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “韓國直送時裝!價格緊貼首爾,每週超過3,000件新款時裝上架,週一至週三更可享新到女裝折上折優惠! Fossil、GUESS、Salad、hellolulu、ARTĒ Madrid、周大福及六福珠寶等國際品牌進駐HKTVmall,品牌正貨…”.

  • Canonical URL set

    The canonical URL is https://www.hktvmall.com/hktv/zh/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.hktvmall.com/sitemap.xml.

AI search readiness

2 to fix60
  • No Organization structured data

    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.

  • Parts of the site are closed to 5 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.hktvmall.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.

Other pages

5 to fix57
  • 6 linked pages are broken

    Your homepage links to https://www.hktvmall.com/hktv/zh/fashion, https://www.hktvmall.com/hktv/zh/macau, https://www.hktvmall.com/hktv/zh/pets, https://www.hktvmall.com/hktv/zh/mothernbaby, https://www.hktvmall.com/hktv/zh/gadgetsandelectronics and https://www.hktvmall.com/hktv/zh/homenfamily, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 linked page hidden from search

    https://www.hktvmall.com/hktv/zh/cs-help is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.hktvmall.com/page/cashback has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.hktvmall.com/hktv/zh/cs-help, https://www.hktvmall.com/hktv/zh/thirteenlandmarks and https://www.hktvmall.com/hktv/zh/personalcarenhealth use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.hktvmall.com/page/cashback, https://www.hktvmall.com/hktv/zh/cs-help, https://www.hktvmall.com/hktv/zh/thirteenlandmarks, https://www.hktvmall.com/hktv/zh/supermarket, https://www.hktvmall.com/hktv/zh/personalcarenhealth and https://www.hktvmall.com/hktv/zh/beautynhealth have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.hktvmall.com/page/cashback, https://www.hktvmall.com/hktv/zh/thirteenlandmarks and https://www.hktvmall.com/hktv/zh/personalcarenhealth 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.

  • 1 page slow to respond

    https://www.hktvmall.com/hktv/zh/cs-help took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • 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.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

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

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

  • Only about 78 words

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • 2 short forms

    2 short forms (0 fields at most) are right on the homepage.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 hktvmall.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
- 12/F Trans Asia Centre, 18 Kin Hong Street

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on hktvmall.com, including 13 speed issues, 4 SEO issues and 6 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