Website review, no card needed

cherjoy.com logo

cherjoy.com website review

Visit site (opens in a new tab)Reviewed 12 November 202647 issues · 89 checks

This review found 47 issues worth fixing on cherjoy.com, 14 of them high impact, across 89 checks. The most urgent: page weight: 34.4 MB in 676 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
4.3 s3.5 sJul 18Sep 124.2 s
Show as table
DateReal-visitor load time (LCP)
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20264.0 s
Aug 8, 20263.9 s
Aug 15, 20263.7 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20263.9 s
Sep 12, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
272 ms222 msJul 18Aug 29229 ms
Show as table
DateReal-visitor tap response (INP)
Jul 18, 2026254 ms
Jul 25, 2026257 ms
Aug 1, 2026266 ms
Aug 8, 2026261 ms
Aug 15, 2026232 ms
Aug 22, 2026228 ms
Aug 29, 2026229 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 cherjoy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cherjoy.com at 1.4 s1.4 s
  2. cherjoy.com at 2.9 s2.9 s
  3. cherjoy.com at 4.3 s4.3 s
  4. cherjoy.com at 5.7 s5.7 s
  5. cherjoy.com at 7.2 s7.2 s
  6. cherjoy.com at 8.6 s8.6 s
  7. cherjoy.com at 10.0 s10.0 s
  8. cherjoy.com at 11.5 s11.5 s

Speed

10 to fix51
  • Reduce unused JavaScript

    1.5 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Main-thread work: 12.9 s

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

  • Render-blocking requests

    1.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, easychat.co and Google Tag Manager and others), adding 3.8 MB and 1.1 s of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 758 KiB

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

  • Mobile performance score: 51

    51/100

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

  • Shopify adds 405 ms

    405 ms

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

  • easychat.co adds 215 ms

    215 ms

    easychat.co costs a phone 215 ms of main-thread work and 581 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.

  • 2,677 HTML elements

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

  • Google Tag Manager adds 193 ms

    193 ms

    Google Tag Manager costs a phone 193 ms of main-thread work and 311 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.

  • Reduce unused CSS

    150 ms · 172 KiB

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

  • Improve image delivery

    236 KiB

    11 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    50 KiB

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

  • Minify CSS

    13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • 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: 19 ms

    19 ms

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

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 10.5 s

    10.5 s

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

  • Time to Interactive: 38.0 s

    38.0 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 424 ms

    424 ms

    Scripts block taps and scrolling for 424 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

2 checks passed
  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0.021

    0.021

    The layout barely moves while loading (CLS 0.021, good is under 0.1).

Images and page weight

3 to fix45
  • Page weight: 34.4 MB in 676 requests

    34.4 MB

    Your homepage downloads 34.4 MB in 676 requests on a phone: images 28.5 MB (107), scripts 3.5 MB (236) and other files 1.5 MB (243). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    9_71de5f5c-5f16-4eb9-bdc7-9a5b8c4e8727.svg weighs 8.5 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    373 KiB

    1 image is downloaded at several times the size a phone draws it, for example 9_71de5f5c-5f16-4eb9-bdc7-9a5b8c4e8727.svg at 1,104 px wide, shown at 360 px. Resized copies would save about 373 KiB.

  • 1 image in older formats

    1 image (75 KiB) is 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 9.8 g of CO₂ per visit

    9.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.76 g of CO₂e: 1171.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7790
  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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 (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • ARIA role should be appropriate for the element (27 elements)

    ARIA role should be appropriate for the element: 27 elements on the page fail this check, rated minor by axe-core.

  • 6 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

    Your title is only 21 characters: “Dèlain by CJA 女裝設計師品牌”. 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.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “The New 最新發表”). One clear main headline is easier for people and search engines.

  • Meta description is long (178 characters)

    Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 230 internal links, 5 external

    The homepage links to 230 pages on cherjoy.com and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://cherjoy.com/.

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

AI search readiness

1 to fix88
  • 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 (367 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

6 to fix62
  • 1 page without a title

    https://cherjoy.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://cherjoy.com/customer_authentication/redirect 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://cherjoy.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages share a meta description

    https://cherjoy.com/products/%E7%92%B0%E4%BF%9D%E5%8C%85%E8%A3%9D-%E7%84%A1%E7%B4%99%E8%A2%8B%E5%8F%8A%E7%B7%9E%E5%B8%B6, https://cherjoy.com/collections/clothing, https://cherjoy.com/collections/choice-by-cher, https://cherjoy.com/collections/tweed, https://cherjoy.com/collections/cashmere and https://cherjoy.com/collections/knitwear 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://cherjoy.com/products/%E7%92%B0%E4%BF%9D%E5%8C%85%E8%A3%9D-%E7%84%A1%E7%B4%99%E8%A2%8B%E5%8F%8A%E7%B7%9E%E5%B8%B6, whose canonical is https://cherjoy.com/products/%e7%92%b0%e4%bf%9d%e5%8c%85%e8%a3%9d-%e7%84%a1%e7%b4%99%e8%a2%8b%e5%8f%8a%e7%b7%9e%e5%b8%b6. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://cherjoy.com/customer_authentication/redirect, https://cherjoy.com/products/%E7%92%B0%E4%BF%9D%E5%8C%85%E8%A3%9D-%E7%84%A1%E7%B4%99%E8%A2%8B%E5%8F%8A%E7%B7%9E%E5%B8%B6, https://cherjoy.com/collections/clothing, https://cherjoy.com/collections/choice-by-cher, https://cherjoy.com/collections/new-arrival and https://cherjoy.com/collections/instocks and 9 others 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 131 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 8191
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cornercart Failed to fetch from abt.usecorner.io: AbortError: signal is aborted without reason”.

2 checks passed
  • Tap targets are thumb-sized

    41 of 48 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix61
  • 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.

  • Local business without LocalBusiness data

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

  • Thin social proof

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

  • Only about 249 words

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

  • No opening hours

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

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

4 checks passed
  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 22 cookies set on arrival

    22

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 cherjoy.com, 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 22 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ako Marketing · Delain Lock · Sami Product Labels · Ako Cvs · Hulk Contact Form Builder · Microsoft Clarity · Judge Me Reviews · Scrolly Infinite Scroll · Firework Shoppable Video Ugc · Bucks · Essential Grid Gallery · Ako Demo · Delain Free Gift · Ako Retargeting · Birse · Globo Product Options · Pushowl · Essentials Estimated Delivery · Cornercart · akocommerce.com · elfsight.com · kxcdn.com

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 Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on cherjoy.com, including 16 speed issues, 4 SEO issues and 5 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