Website review, no card needed

mycupcakemama.com logo

mycupcakemama.com website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 81 checks

This review found 34 issues worth fixing on mycupcakemama.com, 10 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
934 ms683 msMay 16Oct 31721 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026865 ms
May 23, 2026849 ms
May 30, 2026773 ms
Jun 6, 2026750 ms
Jun 13, 2026746 ms
Jun 20, 2026759 ms
Jun 27, 2026774 ms
Jul 4, 2026823 ms
Jul 11, 2026852 ms
Jul 18, 2026905 ms
Jul 25, 2026891 ms
Aug 1, 2026814 ms
Aug 8, 2026783 ms
Aug 15, 2026768 ms
Aug 22, 2026785 ms
Aug 29, 2026824 ms
Sep 5, 2026856 ms
Sep 12, 2026857 ms
Sep 19, 2026821 ms
Sep 26, 2026822 ms
Oct 3, 2026803 ms
Oct 10, 2026783 ms
Oct 17, 2026774 ms
Oct 24, 2026712 ms
Oct 31, 2026721 ms
Real-visitor tap response (INP)75th percentile, phones
99 ms73 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202677 ms
May 23, 202676 ms
May 30, 202677 ms
Jun 6, 202677 ms
Jun 13, 202678 ms
Jun 20, 202678 ms
Jun 27, 202678 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202683 ms
Jul 25, 202680 ms
Aug 1, 202679 ms
Aug 8, 202680 ms
Aug 15, 202679 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202688 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202695 ms
Oct 24, 202696 ms
Oct 31, 202696 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 mycupcakemama.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mycupcakemama.com at 0.5 s0.5 s
  2. mycupcakemama.com at 1.0 s1.0 s
  3. mycupcakemama.com at 1.5 s1.5 s
  4. mycupcakemama.com at 2.0 s2.0 s
  5. mycupcakemama.com at 2.5 s2.5 s
  6. mycupcakemama.com at 3.0 s3.0 s
  7. mycupcakemama.com at 3.6 s3.6 s
  8. mycupcakemama.com at 4.1 s4.1 s

Speed

9 to fix62
  • Use efficient cache lifetimes

    2.0 s · 442 KiB

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

  • Improve image delivery

    950 ms · 474 KiB

    22 images could be 474 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.

  • Reduce unused JavaScript

    900 ms · 190 KiB

    About 190 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 62

    62/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (elfsight.com, Shopify and Bing Ads and others), adding 1.1 MB and 662 ms of main-thread time.

  • elfsight.com adds 499 ms

    499 ms

    elfsight.com costs a phone 499 ms of main-thread work and 440 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.7 s

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

  • 2,013 HTML elements

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

  • Shopify adds 145 ms

    145 ms

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

  • 3 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 31 KiB

    31 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    150 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Font display

    50 ms

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

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 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: 11 ms

    11 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.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: 14.0 s

    14.0 s

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

  • Speed Index: 8.9 s

    8.9 s

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

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

    +25%

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.7 s

    0.7 s

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

  • Real-user INP: 89 ms

    89 ms

    Real visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.5 s

    0.5 s

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

  • Real-user TTFB: 353 ms

    353 ms

    Real visitors wait 353 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 158 ms

    158 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix83
  • Page weight: 3.1 MB in 273 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 273 requests on a phone: images 1.0 MB (39), scripts 968 KiB (96) and other files 732 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Green_and_White_Folksy_Illustrative_Christmas_Sale_Facebook_ is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 7 images below the first screen load straight away

    7 images further down the page (204 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8993
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • 51 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (2 elements).

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is short (12 characters)

    Your title is only 12 characters: “Cupcake Mama”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 87 internal links, 1 external

    The homepage links to 87 pages on mycupcakemama.com and 1 external page.

5 checks passed
  • Meta description: 81 characters

    Your meta description is 81 characters: “Locally owned shop in Edmonton that specializes in customized cakes and cupcakes.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, ProductGroup and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://mycupcakemama.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://mycupcakemama.com/collections/designer-cupcake, https://mycupcakemama.com/collections/signature-cupcakes, https://mycupcakemama.com/collections/mini-cupcakes and https://mycupcakemama.com/collections/young-ones-and-young-at-heart have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://mycupcakemama.com/pages/about-us has 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 39 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

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

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343159845&Ver=2&mid=c252d512-bc3a-411c-9f74-c118a9681adc&bo=1&sid=782eb840d9b311f1a20e53a717a382d4&vid=783715a0d9b311f1a33a9fdd7b2fa5ec&vids=1&msclkid=N&pi=918639831&l.

  • 10 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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 305 words of copy

    The homepage carries about 305 words of visible text.

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Custom Order”, “Contact Us” and “Shop Cakes”.

  • 6 short forms

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

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 Ads (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.

  • 14 cookies set on arrival

    14

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

  • 21 other companies contacted

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

Apps your storefront loads

Aris Product Options · Nitro Lookbook · Inbox · covet.pics · elfsight.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
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 mycupcakemama.com, including 14 speed issues, 3 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