Website review, no card needed
pricerite.com.hk website review
Visit site (opens in a new tab)Reviewed 3 November 202645 issues · 88 checks
This review found 45 issues worth fixing on pricerite.com.hk, 14 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 7.1 s |
| May 23, 2026 | 7.1 s |
| May 30, 2026 | 7.1 s |
| Jun 6, 2026 | 7.1 s |
| Jun 13, 2026 | 7.2 s |
| Jun 20, 2026 | 7.3 s |
| Jun 27, 2026 | 7.4 s |
| Jul 4, 2026 | 7.5 s |
| Jul 11, 2026 | 7.4 s |
| Jul 18, 2026 | 7.3 s |
| Jul 25, 2026 | 7.2 s |
| Aug 1, 2026 | 7.2 s |
| Aug 8, 2026 | 7.4 s |
| Aug 15, 2026 | 7.6 s |
| Aug 22, 2026 | 7.7 s |
| Aug 29, 2026 | 7.6 s |
| Sep 5, 2026 | 7.5 s |
| Sep 12, 2026 | 7.2 s |
| Sep 19, 2026 | 6.9 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 223 ms |
| May 23, 2026 | 228 ms |
| May 30, 2026 | 235 ms |
| Jun 6, 2026 | 239 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 247 ms |
| Jun 27, 2026 | 251 ms |
| Jul 4, 2026 | 253 ms |
| Jul 11, 2026 | 253 ms |
| Jul 18, 2026 | 253 ms |
| Jul 25, 2026 | 254 ms |
| Aug 1, 2026 | 257 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 273 ms |
| Aug 29, 2026 | 271 ms |
| Sep 5, 2026 | 270 ms |
| Sep 12, 2026 | 267 ms |
| Sep 19, 2026 | 263 ms |
| Sep 26, 2026 | 262 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 262 ms |
| Oct 17, 2026 | 264 ms |
| Oct 24, 2026 | 269 ms |
| Oct 31, 2026 | 268 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.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Reduce unused JavaScript
4.1 s · 763 KiBAbout 763 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Improve image delivery
1.3 s · 251 KiB6 images could be 251 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 705 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 4.0 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 Tag Manager, Facebook and Clarity and others), adding 1.6 MB and 1.9 s of main-thread time.
Use efficient cache lifetimes
450 ms · 414 KiB8 files are served with short cache lifetimes, so returning visitors download them again (414 KiB).
Reduce unused CSS
750 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
700 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Facebook adds 533 ms
533 msFacebook costs a phone 533 ms of main-thread work and 344 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 473 ms. During a long task the page ignores taps.
2,037 HTML elements
The page has 2,037 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Builder adds 0 ms
0 msBuilder costs a phone 0 ms of main-thread work and 478 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.
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 16.3 s
16.3 sYour largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “popup”.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Total Blocking Time: 2.5 s
2.5 sScripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 340 ms
340 msReal visitors wait 340 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 898 ms
898 msReal visitors wait 898 ms for your server to start answering (75th percentile). Good is under 800 ms.
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) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 223 ms to 268 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Largest content (LCP) got 52% faster for real visitors
-52%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 7.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 125 requests
3.0 MBYour homepage downloads 3.0 MB in 125 requests on a phone: scripts 2.0 MB (50), images 522 KiB (33) and other files 196 KiB (36). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
91 form fields without a label
91 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor 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. (3 elements).
2 checks passed
Every image has alt text
All 116 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
111 internal links, 18 external
The homepage links to 111 pages on pricerite.com.hk and 18 external pages.
6 checks passed
Meta description: 78 characters
Your meta description is 78 characters: “Pricerite實惠致力搜羅各種優質的傢俬、家品、家電及食品,全方位為顧客打造舒適的家居生活。門市遍布港九新界,亦設有網上商店,成為會員更可盡享多項優惠。”.
Title: 53 characters
Your title is a healthy 53 characters: “Pricerite實惠 | 高品質安全耐用家品傢俬 | 空間管理專家- Pricerite實惠網店(香港)”.
Canonical URL set
The canonical URL is https://www.pricerite.com.hk/hk/zh-hk.
Structured data in place
Structured data found: Organization.
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.pricerite.com.hk/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), 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.pricerite.com.hk/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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, ClaudeBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
1 checks passed
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.
Other pages
4 pages share 2 titles
https://www.pricerite.com.hk/hk/zh-hk and https://www.pricerite.com.hk/hk/zh-hk/rewards-center all use the title “Pricerite實惠 | 高品質安全耐用家品傢俬 | 空間管理專家- Pricerite實惠網店(香港)”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages share a meta description
https://www.pricerite.com.hk/hk/zh-hk/pricerite-eshop-app, https://www.pricerite.com.hk/hk/zh-hk/storeInfo, https://www.pricerite.com.hk/hk/zh-hk/rewards-center, https://www.pricerite.com.hk/hk/zh-hk/category, https://www.pricerite.com.hk/hk/zh-hk/category/%E7%9A%87%E7%89%8C%E7%B3%BB%E5%88%97 and https://www.pricerite.com.hk/hk/zh-hk/category/new-arrivals and 5 others use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.pricerite.com.hk/blog/HKfurniture_solution, whose canonical is https://www.pricerite.com.hk/hk/zh-hk/blog/HKfurniture_solution. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.pricerite.com.hk/hk/zh-hk/pricerite-eshop-app, https://www.pricerite.com.hk/hk/zh-hk/customer-service-center and https://www.pricerite.com.hk/hk/zh-hk/rewards-center have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://www.pricerite.com.hk/hk/zh-hk/pricerite-eshop-app, https://www.pricerite.com.hk/hk/zh-hk/storeInfo, https://www.pricerite.com.hk/hk/zh-hk/customer-service-center, https://www.pricerite.com.hk/hk/zh-hk/rewards-center, https://www.pricerite.com.hk/blog/HKfurniture_solution and https://www.pricerite.com.hk/hk/zh-hk/doubleeleven and 2 others 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.
3 pages slow to respond
https://www.pricerite.com.hk/hk/zh-hk/category/pets, https://www.pricerite.com.hk/category/appliances/large-electric-appliance/television and https://www.pricerite.com.hk/hk/zh-hk/category/furniture/study-room/office-chair took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 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 a meta description
All 15 pages that loaded have a meta description.
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
23 small tap targets
23 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 19 words
The homepage has only about 19 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Close app download banner”.
1 call to action
The homepage has 1 call to action, for example “Close app download banner”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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
15Opening 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.
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 pricerite.com.hk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 1986
- 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 45 issues on pricerite.com.hk, including 24 speed issues, 2 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.