Website review, no card needed
mamashelter.com website review
Visit site (opens in a new tab)Reviewed 18 November 202643 issues · 86 checks
This review found 43 issues worth fixing on mamashelter.com, 18 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
65D- #109,174 of 117,615 reviewed websitesbeats 6%
- #64,565 of 66,923 online storesbeats 3%
- #59,250 of 61,018 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 210 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 223 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 228 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 255 ms |
| Aug 22, 2026 | 269 ms |
| Aug 29, 2026 | 283 ms |
| Sep 5, 2026 | 281 ms |
| Sep 12, 2026 | 284 ms |
| Sep 19, 2026 | 286 ms |
| Sep 26, 2026 | 288 ms |
| Oct 3, 2026 | 293 ms |
| Oct 10, 2026 | 295 ms |
| Oct 17, 2026 | 299 ms |
| Oct 24, 2026 | 305 ms |
| Oct 31, 2026 | 301 ms |
| Nov 7, 2026 | 303 ms |
| Nov 14, 2026 | 312 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
1.5 s
2.9 s
4.4 s
5.9 s
7.3 s
8.8 s
10.3 s
11.7 s
Speed
Reduce unused JavaScript
5.0 s · 2.3 MBAbout 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Google Tag Manager adds 3.8 s
3.8 sGoogle Tag Manager costs a phone 3.8 s of main-thread work and 3.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
1.6 s · 405 KiB10 files are served with short cache lifetimes, so returning visitors download them again (405 KiB).
Render-blocking requests
1.0 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,550 HTML elements
The page has 3,550 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Stripe and others), adding 4.8 MB and 4.8 s of main-thread time.
Improve image delivery
525 KiB1 image could be 525 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 451 ms
451 msGoogle CDN costs a phone 451 ms of main-thread work and 739 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 393 ms. During a long task the page ignores taps.
Stripe adds 203 ms
203 msStripe costs a phone 203 ms of main-thread work and 304 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.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
75 KiBAbout 75 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 31 ms
31 msYour server sent the HTML in 31 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.
Largest Contentful Paint: 14.5 s
14.5 sYour largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies that are essential for the proper functionin…”. Most of its time is element render delay (7.6 s).
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.5 s
36.5 sThe page becomes fully interactive after 36.5 s. Good is under 3.8 s.
Total Blocking Time: 4.0 s
4.0 sScripts block taps and scrolling for 4.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 206 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 24.1 MB in 145 requests
24.1 MBYour homepage downloads 24.1 MB in 145 requests on a phone: images 9.4 MB (36), media 8.7 MB (1) and scripts 5.1 MB (52). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
ROLLER-e1764601680758.png weighs 527 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
518 KiB1 image is downloaded at several times the size a phone draws it, for example ROLLER-e1764601680758.png at 880 px wide, shown at 39 px. Resized copies would save about 518 KiB.
About 6.8 g of CO₂ per visit
6.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.83 g of CO₂e: 819.1 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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
[aria-*] attributes are not valid or misspelled
[aria-*] attributes are not valid or misspelled (8 elements).
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Mama Shelter - Design bedrooms, unique Restaurants, Bars & Rooftops”.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “WebPage: keywords is an empty list”.
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.
112 internal links, 69 external
The homepage links to 112 pages on mamashelter.com and 69 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Discover Mama Shelter, design, unique and cosy places in vibrant cities: Lyon, Paris, Dubai, Prague, Bordeaux... Come t…”.
One H1 headline
Your main headline reads: “Mama’s got it all going on!”.
Canonical URL set
The canonical URL is https://mamashelter.com/.
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://mamashelter.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://mamashelter.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,318 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://mamashelter.com/nice, https://mamashelter.com/paris-west and https://mamashelter.com/paris-east all use the title “Design Bedrooms, Restaurant, Rooftop - Welcome to Mama!”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages slow to respond
https://mamashelter.com/stay, https://mamashelter.com/eat-drink, https://mamashelter.com/about-us and https://mamashelter.com/nice took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
6 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 pages that loaded have a meta description.
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 9 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://mamashelter.com/.
2 JavaScript errors while loading
2 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 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
88 of 93 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: 22 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 8-field form
Your longest form asks for 8 fields (6 required). Every extra field lowers completion.
About 1,120 words of copy
The homepage carries about 1,120 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “BOOK”.
19 calls to action
The homepage has 19 calls to action, for example “Shop”, “BOOK” and “Go to our shop”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
29 other companies contacted
Loading the homepage contacts 29 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 mamashelter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- CMS
- WordPress
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- WordPress.com
Company
- Founded
- 2008
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on mamashelter.com, including 25 speed issues, 3 SEO issues 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.