Website review, no card needed

georgetowncupcake.com logo

georgetowncupcake.com website review

Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 86 checks

This review found 40 issues worth fixing on georgetowncupcake.com, 13 of them high impact, across 86 checks. The most urgent: page weight: 29.0 MB in 341 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
2.3 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 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.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
212 ms136 msMay 16Oct 31202 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026177 ms
May 23, 2026145 ms
May 30, 2026146 ms
Jun 6, 2026155 ms
Jun 13, 2026161 ms
Jun 20, 2026159 ms
Jun 27, 2026157 ms
Jul 4, 2026155 ms
Jul 11, 2026154 ms
Jul 18, 2026155 ms
Jul 25, 2026154 ms
Aug 1, 2026154 ms
Aug 8, 2026148 ms
Aug 15, 2026146 ms
Aug 22, 2026150 ms
Aug 29, 2026146 ms
Sep 5, 2026154 ms
Sep 12, 2026162 ms
Sep 19, 2026171 ms
Sep 26, 2026187 ms
Oct 3, 2026195 ms
Oct 10, 2026201 ms
Oct 17, 2026196 ms
Oct 24, 2026203 ms
Oct 31, 2026202 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 georgetowncupcake.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. georgetowncupcake.com at 0.9 s0.9 s
  2. georgetowncupcake.com at 1.8 s1.8 s
  3. georgetowncupcake.com at 2.7 s2.7 s
  4. georgetowncupcake.com at 3.7 s3.7 s
  5. georgetowncupcake.com at 4.6 s4.6 s
  6. georgetowncupcake.com at 5.5 s5.5 s
  7. georgetowncupcake.com at 6.4 s6.4 s
  8. georgetowncupcake.com at 7.3 s7.3 s

Speed

10 to fix61
  • Main-thread work: 5.7 s

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

  • 5,613 HTML elements

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

  • Improve image delivery

    100 ms · 3.3 MB

    44 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Mobile performance score: 61

    61/100

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

  • Render-blocking requests

    900 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.3 MB and 522 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 460 KiB

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

  • Reduce unused CSS

    300 ms · 51 KiB

    About 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 140 ms

    140 ms

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

  • Klaviyo adds 91 ms

    91 ms

    Klaviyo costs a phone 91 ms of main-thread work and 307 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.

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    19 KiB

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

9 to fix67
  • 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: 10.7 s

    10.7 s

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

  • Time to Interactive: 19.7 s

    19.7 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user INP: 229 ms

    229 ms

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

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

    +26%

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

  • Real-user TTFB: 885 ms

    885 ms

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

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

    255 ms

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • 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: 1.6 s

    1.6 s

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

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

    -18%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 29.0 MB in 341 requests

    29.0 MB

    Your homepage downloads 29.0 MB in 341 requests on a phone: media 19.0 MB (4), images 7.3 MB (83) and scripts 1.5 MB (131). Under 2 MB keeps phones on slow connections fast.

  • About 8.2 g of CO₂ per visit

    8.23 g

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

10 to fixGoogle 7787
  • Hidden but focusable

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

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

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

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

  • 61 links without text

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

  • 2 form fields without a label

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

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

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 8583
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (238 characters)

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 282 internal links, 6 external

    The homepage links to 282 pages on georgetowncupcake.com and 6 external pages.

6 checks passed
  • Title: 40 characters

    Your title is a healthy 40 characters: “Georgetown Cupcake | DC Gourmet Cupcakes”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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 (3,132 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://georgetowncupcake.com/products/custom-dozen 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://georgetowncupcake.com/pages/cupcake-calendar has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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
  • 20 small tap targets

    20 of 58 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

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

    The homepage carries about 592 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop what's new”.

  • 59 calls to action

    The homepage has 59 calls to action, for example “Shop what's new”, “shop all cupcakes” and “new years Sweet start to the year”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 5 cookies set on arrival

    5

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

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
Hosting
Shopify

Company

Founded
2008
Headquarters
Washington, D.C.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on georgetowncupcake.com, including 19 speed issues, 3 SEO issues and 2 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