Website review, no card needed
sweet-life-events.com website review
Visit site (opens in a new tab)Reviewed 19 November 202630 issues · 76 checks
This review found 30 issues worth fixing on sweet-life-events.com, 9 of them high impact, across 76 checks. The most urgent: mobile performance score: 40. 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
68DClosest 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
150 ms · 999 KiB9 files are served with short cache lifetimes, so returning visitors download them again (999 KiB).
Reduce unused JavaScript
750 ms · 301 KiBAbout 301 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, elfsight.com and tarteaucitron.io and others), adding 1.5 MB and 688 ms of main-thread time.
Improve image delivery
775 KiB6 images could be 775 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 522 ms
522 msGoogle Tag Manager costs a phone 522 ms of main-thread work and 376 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.
Render-blocking requests
550 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 456 ms. During a long task the page ignores taps.
elfsightcdn.com adds 0 ms
0 mselfsightcdn.com costs a phone 0 ms of main-thread work and 840 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
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 663 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.547
0.547The layout shifts by 0.547 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 9.1 s
9.1 sThe page becomes fully interactive after 9.1 s. Good is under 3.8 s.
Total Blocking Time: 506 ms
506 msScripts block taps and scrolling for 506 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.5 MB in 59 requests
6.5 MBYour homepage downloads 6.5 MB in 59 requests on a phone: images 5.6 MB (28), scripts 705 KiB (12) and fonts 93 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.8 g of CO₂ per visit
1.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.83 g of CO₂e: 219.9 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
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 2 problems
Structured data found (corporation) but with 2 problems, for example “corporation: logo is not an absolute URL ("https://www.sweet-life-events.com/img/elementgraphique/element_graphique_3.webp")”.
No social preview image
No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
22 internal links, 10 external
The homepage links to 22 pages on sweet-life-events.com and 10 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Sweet Life Events, votre mariage clé en main ! Wedding Planner à Marseille (13) : organisation, coordination, recherche…”.
One H1 headline
Your main headline reads: “Wedding planner et organisatrice d'événements Marseille | Sweet Life Events”.
Title: 65 characters
Your title is a healthy 65 characters: “Wedding Planner Marseille (13) | Organisatrice Mariage Sur-Mesure”.
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.sweet-life-events.com/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.sweet-life-events.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.
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 (640 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
7 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
11 small tap targets
11 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
7 low-resolution images
7 images are served at too low a resolution for sharp phone screens.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 634 words of copy
The homepage carries about 634 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
2 short forms
2 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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
5Opening 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.
11 other companies contacted
Loading the homepage contacts 11 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 sweet-life-events.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
- Hosting
- SAS Nexylan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on sweet-life-events.com, including 15 speed issues, 4 SEO issues and 3 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.