Website review, no card needed
sweetcakes.re website review
Visit site (opens in a new tab)Reviewed 19 November 202623 issues · 62 checks
This review found 23 issues worth fixing on sweetcakes.re, 12 of them high impact, across 62 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
75CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Improve image delivery
37.5 s · 31.3 MB13 images could be 31.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 37.5 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Reduce unused JavaScript
150 ms · 49 KiBAbout 49 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.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.
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: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 255 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 97.3 s
97.3 sYour largest element takes 97.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cake design Sweet Cakes La Réunion”.
Time to Interactive: 103.0 s
103.0 sThe page becomes fully interactive after 103.0 s. Good is under 3.8 s.
Speed Index: 15.2 s
15.2 sVisually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 32.0 MB in 40 requests
32.0 MBYour homepage downloads 32.0 MB in 40 requests on a phone: images 31.7 MB (14), scripts 231 KiB (13) and fonts 101 KiB (4). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
6.1 MB2 images are downloaded at several times the size a phone draws them, for example yasmine.jpeg at 3,024 px wide, shown at 342 px. Resized copies would save about 6.1 MB.
2 images in older formats
2 images (7.1 MB) 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 9.1 g of CO₂ per visit
9.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.08 g of CO₂e: 1089.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
17 text elements with low contrast
17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
39 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: 39 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
18 internal links, 3 external
The homepage links to 18 pages on sweetcakes.re and 3 external pages.
5 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Yasmine crée des gâteaux sur-mesure 100% fait maison pour vos événements à La Réunion. Wedding cakes, créations personn…”.
One H1 headline
Your main headline reads: “Des créations sucréesqui marquent vos moments… à vie.”.
Title: 41 characters
Your title is a healthy 41 characters: “Sweetcakes 974 — Cake Design à La Réunion”.
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.sweetcakes.re/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.sweetcakes.re/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (820 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.sweetcakes.re/devis has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.sweetcakes.re/galerie has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 5 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 5 pages that loaded have a meta description.
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 5 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 8-field form
Your longest form asks for 8 fields (4 required). Every extra field lowers completion.
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 638 words of copy
The homepage carries about 638 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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 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 sweetcakes.re, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on sweetcakes.re, including 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.