Website review, no card needed
cerqular.hk website review
Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 74 checks
This review found 34 issues worth fixing on cerqular.hk, 10 of them high impact, across 74 checks. The most urgent: render-blocking 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
80B- #48,294 of 123,940 reviewed websitesbeats 55%
- #31,919 of 69,719 online storesbeats 48%
- #30,674 of 63,424 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.9 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused JavaScript
640 ms · 491 KiBAbout 491 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 396 KiB24 files are served with short cache lifetimes, so returning visitors download them again (396 KiB).
8 third-party services on the page
8 third-party services load with your homepage (PayPal, Google CDN and Google Tag Manager and others), adding 887 KiB and 863 ms of main-thread time.
Improve image delivery
631 KiB4 images could be 631 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 35 KiBAbout 35 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
150 ms · 24 KiB24 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
4 KiB4 KiB JavaScript is shipped twice across bundles.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re currently upgrading our marketplace platform to serve…”. Most of its time is element render delay (2.3 s).
Total Blocking Time: 221 ms
221 msScripts block taps and scrolling for 221 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
3 images far larger than shown
609 KiB3 images are downloaded at several times the size a phone draws them, for example RAV08241.jpg at 1,570 px wide, shown at 120 px. Resized copies would save about 609 KiB.
Page weight: 3.2 MB in 225 requests
3.2 MBYour homepage downloads 3.2 MB in 225 requests on a phone: scripts 1.2 MB (74), images 891 KiB (7) and other files 815 KiB (120). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (501 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.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “Cerqular HK: Top Trending Brands, Real Reviews & Free Shipping Options – Cerqular Hong Ko…”.
Meta description is long (268 characters)
Your meta description is 268 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.
9 internal links, 6 external
The homepage links to 9 pages on cerqular.hk and 6 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://cerqular.hk/.
Structured data in place
Structured data found: BreadcrumbList.
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://cerqular.hk/sitemap.xml.
AI search readiness
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.
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 (364 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cerqular.hk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://cerqular.hk/pages/swym-share-wishlist has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://cerqular.hk/pages/swym-share-wishlist has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://cerqular.hk/pages/swym-share-wishlist 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.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 1 page 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 1 page that loaded have a <title>.
Best practices
4 small tap targets
4 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 320 words of copy
The homepage carries about 320 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Subscribe” and “Sign up”.
7 short forms
7 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Pinterest Tag and TikTok 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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 3 of them by other companies (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.
31 other companies contacted
Loading the homepage contacts 31 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 cerqular.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Uppromote Affiliate · Inbox · Affliate By Secomapp · webkul.com · akamaized.net
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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on cerqular.hk, including 12 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.