Website review, no card needed

magicmystics.com logo

magicmystics.com website review

Visit site (opens in a new tab)Reviewed 12 November 202632 issues · 74 checks

This review found 32 issues worth fixing on magicmystics.com, 10 of them high impact, across 74 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

Full-page screenshot of magicmystics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. magicmystics.com at 0.5 s0.5 s
  2. magicmystics.com at 0.9 s0.9 s
  3. magicmystics.com at 1.4 s1.4 s
  4. magicmystics.com at 1.9 s1.9 s
  5. magicmystics.com at 2.3 s2.3 s
  6. magicmystics.com at 2.8 s2.8 s
  7. magicmystics.com at 3.3 s3.3 s
  8. magicmystics.com at 3.7 s3.7 s

Speed

7 to fix61
  • Reduce unused JavaScript

    2.1 s · 368 KiB

    About 368 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Use efficient cache lifetimes

    1.4 s · 250 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 61

    61/100

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

  • Improve image delivery

    300 ms · 46 KiB

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

  • PayPal adds 303 ms

    303 ms

    PayPal costs a phone 303 ms of main-thread work and 391 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.

  • Main-thread work: 2.5 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (PayPal, Facebook and Shopify and others), adding 519 KiB and 369 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 7 KiB

    Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 110 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).

  • Reduce unused CSS

    38 KiB

    About 38 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

    6 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Rose Quartz with Rosebuds on Wood”.

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • 1 image without width and height

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

  • 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
  • Total Blocking Time: 115 ms

    115 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

100
  • About 0.6 g of CO₂ per visit

    0.55 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 66.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 2.0 MB in 164 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 164 requests on a phone: other files 862 KiB (128), scripts 641 KiB (22) and HTML 217 KiB (2). That is a lean page.

  • 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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

  • No page language

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10076
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Magic Mystics - Modern Mysticism, Healing, and Maximum Human Potential”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Tiger's Eye Crystal Spheres”). One clear main headline is easier for people and search engines.

  • Meta description is long (176 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.

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

  • 56 internal links, 6 external

    The homepage links to 56 pages on magicmystics.com and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • 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://magicmystics.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 (453 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 linked pages hidden from search

    https://magicmystics.com/collections/all/sphere and https://magicmystics.com/collections/all/tigers-eye are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 6 pages share a meta description

    https://magicmystics.com/collections/our-favorites, https://magicmystics.com/products/dream-amethyst-3-inch-crystal-sphere, https://magicmystics.com/collections/all/sphere, https://magicmystics.com/collections/all/tigers-eye, https://magicmystics.com/products/3-tigers-eye-sphere and https://magicmystics.com/collections/incense use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 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.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 27 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 'error_message')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 361 words of copy

    The homepage carries about 361 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop Crystals” and “Contact Us”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 magicmystics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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

E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on magicmystics.com, including 12 speed issues, 5 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

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