Website review, no card needed
fanniemay.com website review
Visit site (opens in a new tab)Reviewed 30 October 202653 issues · 79 checks
This review found 53 issues worth fixing on fanniemay.com, 25 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.3 s |
| May 16, 2026 | 6.4 s |
| May 23, 2026 | 6.5 s |
| May 30, 2026 | 6.7 s |
| Jun 6, 2026 | 7.1 s |
| Jun 13, 2026 | 7.2 s |
| Jun 20, 2026 | 7.2 s |
| Jun 27, 2026 | 6.9 s |
| Jul 4, 2026 | 6.8 s |
| Jul 11, 2026 | 6.8 s |
| Jul 18, 2026 | 6.8 s |
| Jul 25, 2026 | 6.9 s |
| Aug 1, 2026 | 6.9 s |
| Aug 8, 2026 | 6.8 s |
| Aug 15, 2026 | 6.9 s |
| Aug 22, 2026 | 6.9 s |
| Aug 29, 2026 | 7.1 s |
| Sep 5, 2026 | 7.2 s |
| Sep 12, 2026 | 7.1 s |
| Sep 19, 2026 | 7.3 s |
| Sep 26, 2026 | 7.2 s |
| Oct 3, 2026 | 7.2 s |
| Oct 10, 2026 | 7.3 s |
| Oct 17, 2026 | 7.3 s |
| Oct 24, 2026 | 7.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 251 ms |
| May 16, 2026 | 247 ms |
| May 23, 2026 | 251 ms |
| May 30, 2026 | 245 ms |
| Jun 6, 2026 | 252 ms |
| Jun 13, 2026 | 255 ms |
| Jun 20, 2026 | 253 ms |
| Jun 27, 2026 | 257 ms |
| Jul 4, 2026 | 279 ms |
| Jul 11, 2026 | 311 ms |
| Jul 18, 2026 | 337 ms |
| Jul 25, 2026 | 361 ms |
| Aug 1, 2026 | 353 ms |
| Aug 8, 2026 | 350 ms |
| Aug 15, 2026 | 359 ms |
| Aug 22, 2026 | 357 ms |
| Aug 29, 2026 | 360 ms |
| Sep 5, 2026 | 372 ms |
| Sep 12, 2026 | 394 ms |
| Sep 19, 2026 | 429 ms |
| Sep 26, 2026 | 454 ms |
| Oct 3, 2026 | 463 ms |
| Oct 10, 2026 | 464 ms |
| Oct 17, 2026 | 464 ms |
| Oct 24, 2026 | 472 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
How it loaded on a phone
2.3 s
4.5 s
6.8 s
9.0 s
11.3 s
13.5 s
15.8 s
18.0 s
Speed
Use efficient cache lifetimes
10.1 s · 1.9 MB56 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
5.7 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Legacy JavaScript
1.1 s · 133 KiBPolyfills for old browsers add 133 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 5
5/100Your mobile performance score is 5. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
350 ms · 1.2 MB9 images could be 1.2 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Gigya and others), adding 2.7 MB and 1.0 s of main-thread time.
Reduce unused CSS
150 ms · 428 KiBAbout 428 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 436 ms
436 msGoogle Tag Manager costs a phone 436 ms of main-thread work and 667 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 452 ms. During a long task the page ignores taps.
Checkout.com adds 91 ms
91 msCheckout.com costs a phone 91 ms of main-thread work and 593 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.
Optanon adds 95 ms
95 msOptanon costs a phone 95 ms of main-thread work and 364 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.
userway.org adds 36 ms
36 msuserway.org costs a phone 36 ms of main-thread work and 422 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 · 5 KiB5 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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: 78 ms
78 msYour server sent the HTML in 78 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 522 ms
522 msReal visitors wait 522 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 1.04
1.04For real visitors the layout shifts by 1.04 (75th percentile). Good is under 0.1.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 53.2 s
53.2 sYour largest element takes 53.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A hand reaches for a plate of chocolate-covered candies, wi…”.
Speed Index: 29.3 s
29.3 sVisually, the page fills in at 29.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 56.3 s
56.3 sThe page becomes fully interactive after 56.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.773
0.773The layout shifts by 0.773 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 88% slower for real visitors
+88%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 251 ms to 472 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.3 s to 7.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.8 MB in 254 requests
12.8 MBYour homepage downloads 12.8 MB in 254 requests on a phone: images 8.0 MB (52), scripts 3.7 MB (56) and fonts 575 KiB (5). Under 2 MB keeps phones on slow connections fast.
14 images below the first screen load straight away
14 images further down the page (751 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.64 g of CO₂e: 436.7 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
Images must have alternative text (11 elements)
Images must have alternative text: 11 elements on the page fail this check, rated critical by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at fanniemay.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Enjoy Fannie May premium chocolates and gifts. Shop our array of gourmet chocolates for a custom gift tower or basket o…”.
Title: 57 characters
Your title is a healthy 57 characters: “Premium Gourmet Chocolates & Gift Baskets from Fannie May”.
Canonical URL set
The canonical URL is https://www.fanniemay.com/us/en/.
XML sitemap found
Your XML sitemap is reachable at https://www.fanniemay.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 319 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.fanniemay.com/us/en//medias/sys_master/images/hab/h40/8916058079262/FM_RedLogo_1500x450_NoSubhead/FM-RedLogo-1500x450-NoSubhead.svg.
15 small tap targets
15 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 319 words of copy
The homepage carries about 319 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign In / Register” and “Track My Order”.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google 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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (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 fanniemay.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Hosting
- AWS
Company
- Founded
- 1920
- Headquarters
- Chicago
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 fanniemay.com, including 28 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.