Website review, no card needed
cadbury.com website review
Visit site (opens in a new tab)Reviewed 29 October 202629 issues · 75 checks
This review found 29 issues worth fixing on cadbury.com, 12 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 587 ms |
| May 16, 2026 | 584 ms |
| May 23, 2026 | 597 ms |
| May 30, 2026 | 615 ms |
| Jun 6, 2026 | 620 ms |
| Jun 13, 2026 | 628 ms |
| Jun 20, 2026 | 623 ms |
| Jun 27, 2026 | 612 ms |
| Jul 4, 2026 | 599 ms |
| Jul 11, 2026 | 586 ms |
| Jul 18, 2026 | 575 ms |
| Jul 25, 2026 | 573 ms |
| Aug 1, 2026 | 568 ms |
| Aug 8, 2026 | 568 ms |
| Aug 15, 2026 | 570 ms |
| Aug 22, 2026 | 564 ms |
| Aug 29, 2026 | 557 ms |
| Sep 5, 2026 | 551 ms |
| Sep 12, 2026 | 545 ms |
| Sep 19, 2026 | 539 ms |
| Sep 26, 2026 | 540 ms |
| Oct 3, 2026 | 548 ms |
| Oct 10, 2026 | 559 ms |
| Oct 17, 2026 | 574 ms |
| Oct 24, 2026 | 583 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.4 s · 196 KiB6 images could be 196 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.
Reduce unused JavaScript
1.5 s · 451 KiBAbout 451 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Google CDN and others), adding 1.1 MB and 387 ms of main-thread time.
Google Tag Manager adds 265 ms
265 msGoogle Tag Manager costs a phone 265 ms of main-thread work and 321 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.
Reduce unused CSS
232 KiBAbout 232 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
150 ms · 72 KiB5 files are served with short cache lifetimes, so returning visitors download them again (72 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 817 ms of it running JavaScript. That is comfortably low.
Server response: 19 ms
19 msYour server sent the HTML in 19 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 INP: 549 ms
549 msReal visitors wait 549 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 8.1 s
8.1 sThe first text or image appears after 8.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “man eating Ritz crackers”.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 587 ms to 583 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.052
0.052The layout barely moves while loading (CLS 0.052, good is under 0.1).
Total Blocking Time: 90 ms
90 msScripts block the page for only 90 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 59 requests
2.8 MBYour homepage downloads 2.8 MB in 59 requests on a phone: fonts 1,021 KiB (9), scripts 939 KiB (16) and other files 422 KiB (18). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
228 internal links, 28 external
The homepage links to 228 pages on cadbury.com and 28 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Mondelēz International, Inc. (NASDAQ: MDLZ) is one of the world’s largest snacks companies, empowering people to snack …”.
One H1 headline
Your main headline reads: “Welcome to Mondelēz International, Inc”.
Title: 35 characters
Your title is a healthy 35 characters: “Home | Mondelēz International, Inc.”.
Canonical URL set
The canonical URL is https://www.mondelezinternational.com/.
Structured data in place
Structured data found: Organization.
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://www.mondelezinternational.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.mondelezinternational.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (560 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.mondelezinternational.com/about-us, https://www.mondelezinternational.com/about-us/who-we-are, https://www.mondelezinternational.com/about-us/who-we-are/leading-the-future-of-snacking, https://www.mondelezinternational.com/about-us/who-we-are/our-strategy, https://www.mondelezinternational.com/about-us/who-we-are/our-values and https://www.mondelezinternational.com/about-us/who-we-are/our-history and 9 others have no <title>, so Google invents the link text in results.
3 pages share a meta description
https://www.mondelezinternational.com/about-us/our-way-of-doing-business/code-of-conduct, https://www.mondelezinternational.com/about-us/our-way-of-doing-business/corporate-responsibilities-guidelines and https://www.mondelezinternational.com/about-us/our-way-of-doing-business/supply-chain-expectations use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.mondelezinternational.com/about-us, https://www.mondelezinternational.com/about-us/who-we-are, https://www.mondelezinternational.com/about-us/who-we-are/leading-the-future-of-snacking, https://www.mondelezinternational.com/about-us/who-we-are/our-strategy, https://www.mondelezinternational.com/about-us/who-we-are/our-values and https://www.mondelezinternational.com/about-us/who-we-are/our-history and 9 others have 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 171 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
243 of 262 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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 546 words of copy
The homepage carries about 546 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Tate's Bake Shop” and “Historic Stock Quote”.
6 calls to action
The homepage has 6 calls to action, for example “Tate's Bake Shop”, “Historic Stock Quote” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 cadbury.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
- Gatsby
- Analytics
- Google Tag Manager
- Hosting
- CSC
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 cadbury.com, including 16 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.