Website review, no card needed

mycdshop.com logo

mycdshop.com website review

Visit site (opens in a new tab)Reviewed 8 November 202653 issues · 97 checks

This review found 53 issues worth fixing on mycdshop.com, 24 of them high impact, across 97 checks. The most urgent: reduce unused JavaScript. 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.7 s1.5 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 16Oct 3190 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202681 ms
May 23, 202681 ms
May 30, 202683 ms
Jun 6, 202686 ms
Jun 13, 202687 ms
Jun 20, 202683 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202683 ms
Jul 25, 202685 ms
Aug 1, 202683 ms
Aug 8, 202684 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202694 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202688 ms
Oct 3, 202695 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 202695 ms
Oct 31, 202690 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 mycdshop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mycdshop.com at 0.4 s0.4 s
  2. mycdshop.com at 0.8 s0.8 s
  3. mycdshop.com at 1.3 s1.3 s
  4. mycdshop.com at 1.7 s1.7 s
  5. mycdshop.com at 2.1 s2.1 s
  6. mycdshop.com at 2.5 s2.5 s
  7. mycdshop.com at 2.9 s2.9 s
  8. mycdshop.com at 3.4 s3.4 s

Speed

12 to fix55
  • Reduce unused JavaScript

    11.8 s · 1.6 MB

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

  • Use efficient cache lifetimes

    6.1 s · 1.1 MB

    61 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Render-blocking requests

    1.8 s

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

  • Reduce unused CSS

    1.1 s · 210 KiB

    About 210 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Main-thread work: 4.6 s

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

  • 4,492 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (POWr, powrcdn.com and Other Google APIs/SDKs and others), adding 3.5 MB and 1.7 s of main-thread time.

  • Improve image delivery

    950 ms · 669 KiB

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

  • POWr adds 987 ms

    987 ms

    POWr costs a phone 987 ms of main-thread work and 203 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.

  • Mobile performance score: 55

    55/100

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

  • powrcdn.com adds 450 ms

    450 ms

    powrcdn.com costs a phone 450 ms of main-thread work and 2.5 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.

  • Shopify adds 59 ms

    59 ms

    Shopify costs a phone 59 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.

  • Minify JavaScript

    150 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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: 14 ms

    14 ms

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

Core Web Vitals

7 to fix50
  • 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: 41.0 s

    41.0 s

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

  • Speed Index: 16.2 s

    16.2 s

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

  • Time to Interactive: 41.3 s

    41.3 s

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

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Real-user CLS: 0.17

    0.17

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

  • 6 images without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.051

    0.051

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

  • Total Blocking Time: 70 ms

    70 ms

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

Images and page weight

2 to fix60
  • Page weight: 8.3 MB in 318 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 318 requests on a phone: other files 3.0 MB (144), scripts 2.9 MB (98) and images 1.0 MB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    21 KiB

    1 image is downloaded at several times the size a phone draws it, for example Web_Banner_1251_x_1864_px_-mobile_6_e7bd966d-23a9-48a7-b7f0- at 1,251 px wide, shown at 390 px. Resized copies would save about 21 KiB.

  • 1 image in older formats

    1 image (44 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 2.4 g of CO₂ per visit

    2.35 g

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

17 to fixGoogle 6779
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

  • 44 text elements with low contrast

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

  • Hidden but focusable

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

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 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.

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

  • 2 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 16 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 8582
  • 92 links crawlers can't follow

    92 links have no real href, so search engines can't follow them.

  • Title is short (28 characters)

    Your title is only 28 characters: “MYCDSHOP - 延伸影音領域 盡在MYCDSHOP”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (69 characters)

    Your meta description is only 69 characters: “MYCDSHOP是香港音樂唱碟及影視產品的網上購物平台,致力為您提供無盡影音領域,提供更多元化產品選擇,讓您足不出戶都可享受無盡娛樂體驗!”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 275 internal links, 4 external

    The homepage links to 275 pages on mycdshop.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “MYCDSHOP - 延伸影音領域 盡在MYCDSHOP”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://mycdshop.com/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.

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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mycdshop.com/collections/%E7%94%9F%E6%B4%BB%E7%94%A8%E5%93%81, whose canonical is https://mycdshop.com/collections/%e7%94%9f%e6%b4%bb%e7%94%a8%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 2 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 2 pages that loaded have a <title>.

Best practices

4 to fixGoogle 3583
  • 13 small tap targets

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

  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 159 testimonial or review blocks. 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.

  • Only about 159 words

    The homepage has only about 159 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.

2 checks passed
  • 126 short forms

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

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

  • 13 cookies set on arrival

    13

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

  • 28 other companies contacted

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

Apps your storefront loads

Social Login · Judge Me Reviews · Smart Seo · Frontend · powr.io · sharethis.com · chimpstatic.com · amazonaws.com · yotpo.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

  • The footer still says © 2025.

Stack

Framework
jQuery
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 53 issues on mycdshop.com, including 19 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