Website review, no card needed
g2000.com.hk website review
Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 82 checks
This review found 38 issues worth fixing on g2000.com.hk, 14 of them high impact, across 82 checks. The most urgent: page weight: 12.7 MB in 244 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75C- #81,104 of 123,862 reviewed websitesbeats 30%
- #51,495 of 69,698 online storesbeats 22%
- #48,600 of 63,406 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 976 ms |
| May 16, 2026 | 943 ms |
| May 23, 2026 | 914 ms |
| May 30, 2026 | 882 ms |
| Jun 6, 2026 | 882 ms |
| Jun 13, 2026 | 907 ms |
| Jun 20, 2026 | 925 ms |
| Jun 27, 2026 | 959 ms |
| Jul 4, 2026 | 994 ms |
| Jul 11, 2026 | 988 ms |
| Jul 18, 2026 | 975 ms |
| Jul 25, 2026 | 972 ms |
| Aug 1, 2026 | 930 ms |
| Aug 8, 2026 | 944 ms |
| Aug 15, 2026 | 955 ms |
| Aug 22, 2026 | 941 ms |
| Aug 29, 2026 | 958 ms |
| Sep 5, 2026 | 961 ms |
| Sep 12, 2026 | 952 ms |
| Sep 19, 2026 | 932 ms |
| Sep 26, 2026 | 909 ms |
| Oct 3, 2026 | 881 ms |
| Oct 10, 2026 | 878 ms |
| Oct 17, 2026 | 900 ms |
| Oct 24, 2026 | 898 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 92 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 93 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 96 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
How it loaded on a phone
0.9 s
1.8 s
2.8 s
3.7 s
4.6 s
5.5 s
6.5 s
7.4 s
Speed
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.5 s 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 (Google CDN, Shopify and Other Google APIs/SDKs and others), adding 10.1 MB and 1.3 s of main-thread time.
Shopify adds 323 ms
323 msShopify costs a phone 323 ms of main-thread work and 8.7 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.
Improve image delivery
750 ms · 364 KiB12 images could be 364 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Google CDN adds 893 ms
893 msGoogle CDN costs a phone 893 ms of main-thread work and 1.3 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.
Reduce unused JavaScript
769 KiBAbout 769 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
450 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 194 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
45 KiB45 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
11 KiB9 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 KiB JavaScript that modern phones do not need.
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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.6 s
7.6 sYour 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 element shown below.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.763
0.763The layout shifts by 0.763 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 498 ms
498 msScripts block taps and scrolling for 498 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image 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-24, real Chrome visitors' tap response (inp) went from 92 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 477 ms
477 msReal visitors wait 477 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 12.7 MB in 244 requests
12.7 MBYour homepage downloads 12.7 MB in 244 requests on a phone: media 8.0 MB (2), scripts 1.8 MB (73) and images 1.5 MB (44). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
44 KiB1 image is downloaded at several times the size a phone draws it, for example Crafted_for_Extraordinary.png at 2,767 px wide, shown at 315 px. Resized copies would save about 44 KiB.
1 image below the first screen load straight away
1 image further down the page (49 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.60 g of CO₂e: 431.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
18 form fields without a label
18 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (8 characters)
Your title is only 8 characters: “G2000 集團”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (275 characters)
Your meta description is 275 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
139 internal links, 6 external
The homepage links to 139 pages on g2000.com.hk and 6 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.g2000.com.hk/en.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, ImageObject, Organization and WebPage.
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.g2000.com.hk/sitemap.xml.
AI search readiness
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 (598 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.g2000.com.hk/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.g2000.com.hk/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.g2000.com.hk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://www.g2000.com.hk/customer_authentication/redirect, https://www.g2000.com.hk/en/products/double-jersey-v-neck-cut-and-sew-top-66241761, https://www.g2000.com.hk/en/products/crepe-shirt-collar-blouse-66241041, https://www.g2000.com.hk/en/products/pure-cotton-ponte-cut-and-sew-top-66243747, https://www.g2000.com.hk/en/products/mock-neck-oversize-fit-short-sleeve-casual-t-shirt-66142226 and https://www.g2000.com.hk/en/products/non-iron-micro-mesh-textured-long-sleeve-dress-shirt-66121122 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.g2000.com.hk/customer_authentication/redirect, https://www.g2000.com.hk/en/collections/menswear and https://www.g2000.com.hk/en/collections/womenswear have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 69 found) and read each the way a search engine does.
3 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.
Best practices
3 small tap targets
3 of 14 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 “Failed to load resource: net::ERR_FAILED”.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 75 trust badges. 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.
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 510 words of copy
The homepage carries about 510 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
25 other companies contacted
Loading the homepage contacts 25 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 g2000.com.hk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Founded
- 1980
- Headquarters
- Hong Kong
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on g2000.com.hk, including 15 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.