Website review, no card needed

logon.com.hk logo

logon.com.hk website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 88 checks

This review found 36 issues worth fixing on logon.com.hk, 11 of them high impact, across 88 checks. The most urgent: 8,833 HTML elements. 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
1.5 s1.2 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
104 ms84 msMay 16Oct 3192 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202686 ms
May 23, 202686 ms
May 30, 202687 ms
Jun 6, 202689 ms
Jun 13, 202689 ms
Jun 20, 202690 ms
Jun 27, 202692 ms
Jul 4, 202693 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202694 ms
Aug 1, 202694 ms
Aug 8, 202696 ms
Aug 15, 202698 ms
Aug 22, 202699 ms
Aug 29, 2026101 ms
Sep 5, 2026100 ms
Sep 12, 2026102 ms
Sep 19, 2026101 ms
Sep 26, 202698 ms
Oct 3, 202692 ms
Oct 10, 202689 ms
Oct 17, 202688 ms
Oct 24, 202689 ms
Oct 31, 202692 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 logon.com.hk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. logon.com.hk at 0.7 s0.7 s
  2. logon.com.hk at 1.4 s1.4 s
  3. logon.com.hk at 2.1 s2.1 s
  4. logon.com.hk at 2.8 s2.8 s
  5. logon.com.hk at 3.5 s3.5 s
  6. logon.com.hk at 4.2 s4.2 s
  7. logon.com.hk at 4.9 s4.9 s
  8. logon.com.hk at 5.6 s5.6 s

Speed

7 to fix67
  • 8,833 HTML elements

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

  • Mobile performance score: 67

    67/100

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

  • Reduce unused JavaScript

    620 ms · 225 KiB

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

  • Improve image delivery

    350 ms · 95 KiB

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

  • Render-blocking requests

    350 ms

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

  • Shopify adds 288 ms

    288 ms

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

  • Main-thread work: 3.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cloudfront.net and go2sdk.com and others), adding 686 KiB and 311 ms of main-thread time.

  • Use efficient cache lifetimes

    92 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    17 KiB

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

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.6 s

    7.6 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Time to Interactive: 7.7 s

    7.7 s

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

  • Cumulative Layout Shift: 0.104

    0.104

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 91 ms

    91 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 318 ms

    318 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 18 ms

    18 ms

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

Images and page weight

2 to fix83
  • Page weight: 2.7 MB in 244 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 244 requests on a phone: other files 1.3 MB (98), scripts 663 KiB (70) and images 628 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    LO_Blind_Box_Web-Banner_Homepage-Banner-_Mobile__600x480_1ea 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).

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.77 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8089
  • Invalid ARIA attributes

    5 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Hidden but focusable

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

  • Interactive controls must not be nested (7 elements)

    Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

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

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

  • 23 links without text

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

  • 1 tap target too small

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

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 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 9280
  • Title is short (13 characters)

    Your title is only 13 characters: “LOG-ON E-Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (230 characters)

    Your meta description is 230 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.

  • One H1 headline

    Your <h1> is empty.

  • 279 internal links, 9 external

    The homepage links to 279 pages on logon.com.hk and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://logon.citysuper.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://logon.citysuper.com.hk/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://logon.citysuper.com.hk/products/tencent-babymonster-choom-starlight-card-301630868 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://logon.citysuper.com.hk/products/tencent-babymonster-choom-starlight-card-301630868 all use the title “LOG-ON E-Shop”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://logon.citysuper.com.hk/collections/member-price-offer has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://logon.citysuper.com.hk/products/tencent-babymonster-choom-starlight-card-301630868 took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9687
  • 113 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Advance Reorder cart fetch error: TypeError: Failed to fetch”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,474 words of copy

    The homepage carries about 1,474 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Online Order and Delivery” and “How to Shop”.

  • 123 short forms

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

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 2 trust badges.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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

  • 15 cookies set on arrival

    15

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 logon.com.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Advance Reorder Repeat Order · Zapiet Pickup Delivery · Min Max Limits By Limitsify · Product Colors · Swym Wishlist Plus · Deco Labels Badges · citysuper.com.hk · cloudfront.net · avada.io

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

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 36 issues on logon.com.hk, including 12 speed issues, 4 SEO issues and 4 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