Website review, no card needed

ameliesfrenchbakery.com logo

ameliesfrenchbakery.com website review

Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 78 checks

This review found 29 issues worth fixing on ameliesfrenchbakery.com, 6 of them high impact, across 78 checks. The most urgent: 3,060 HTML elements. 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.6 s817 msJul 4Oct 171.0 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20262.2 s
Jul 18, 20262.4 s
Aug 22, 20261.2 s
Sep 12, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
139 ms110 msJul 4Oct 17136 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 2026131 ms
Jul 18, 2026131 ms
Aug 22, 2026124 ms
Sep 12, 2026115 ms
Oct 3, 2026113 ms
Oct 10, 2026123 ms
Oct 17, 2026136 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 ameliesfrenchbakery.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ameliesfrenchbakery.com at 0.4 s0.4 s
  2. ameliesfrenchbakery.com at 0.9 s0.9 s
  3. ameliesfrenchbakery.com at 1.3 s1.3 s
  4. ameliesfrenchbakery.com at 1.7 s1.7 s
  5. ameliesfrenchbakery.com at 2.2 s2.2 s
  6. ameliesfrenchbakery.com at 2.6 s2.6 s
  7. ameliesfrenchbakery.com at 3.1 s3.1 s
  8. ameliesfrenchbakery.com at 3.5 s3.5 s

Speed

3 to fix75
  • 3,060 HTML elements

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

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    350 ms · 256 KiB

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

  • Reduce unused CSS

    96 KiB

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

  • 3 long tasks on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 56 KiB and 0 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 175 ms of it running JavaScript. That is comfortably low.

  • Server response: 89 ms

    89 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The official logo for Amélie's French Bakery & Café, featur…”. Most of its time is element render delay (2.0 s).

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

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: 1.3 s

    1.3 s

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

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 558 ms

    558 ms

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

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

    -54%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.0 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).

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    52 KiB

    1 image is downloaded at several times the size a phone draws it, for example tower-gold-600x943.png at 390 px wide, shown at 51 px. Resized copies would save about 52 KiB.

  • 6 images in older formats

    6 images (375 KiB) are 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 0.3 g of CO₂ per visit

    0.27 g

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

2 checks passed
  • Page weight: 992 KiB in 21 requests

    992 KiB

    Your homepage downloads 992 KiB in 21 requests on a phone: images 553 KiB (12), HTML 211 KiB (1) and fonts 187 KiB (5). That is a lean page.

  • Images load when needed

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

Accessibility

11 to fixGoogle 8588
  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • 192 internal links, 7 external

    The homepage links to 192 pages on ameliesfrenchbakery.com and 7 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Voted Best Bakery in North Carolina by Southern Living. Visit Amélie's for croissants, macarons, cakes and coffee at 5 …”.

  • One H1 headline

    Your main headline reads: “A French Bakery That’sNot Afraid of a Little Butter… or A Lot of Personality”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Amélie's French Bakery & Café | Charlotte & Rock Hill”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ImageObject, Organization, WebPage 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://ameliesfrenchbakery.com/sitemap_index.xml.

AI search readiness

100
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, description and contact details; sameAs (social profiles) would complete it.

  • llms.txt published

    The site publishes https://ameliesfrenchbakery.com/llms.txt (13 KiB, 63 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://ameliesfrenchbakery.com/about-us, https://ameliesfrenchbakery.com/meet-the-team, https://ameliesfrenchbakery.com/testimonials, https://ameliesfrenchbakery.com/press-awards, https://ameliesfrenchbakery.com/shop and https://ameliesfrenchbakery.com/cakes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://ameliesfrenchbakery.com/about-us, https://ameliesfrenchbakery.com/meet-the-team, https://ameliesfrenchbakery.com/testimonials, https://ameliesfrenchbakery.com/press-awards, https://ameliesfrenchbakery.com/shop and https://ameliesfrenchbakery.com/cakes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://ameliesfrenchbakery.com/corporate-gifting took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 2 small tap targets

    2 of 6 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

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

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

  • A 8-field form

    Your longest form asks for 8 fields (8 required). Every extra field lowers completion.

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

  • Only about 117 words

    The homepage has only about 117 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
  • 12 calls to action

    The homepage has 12 calls to action, for example “shop”, “Contact Us” and “Order For Pickup”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on ameliesfrenchbakery.com, including 7 speed issues, 1 SEO issue 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