Website review, no card needed
grungemama.com website review
Visit site (opens in a new tab)Reviewed 19 November 202628 issues · 83 checks
This review found 28 issues worth fixing on grungemama.com, 9 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81B- #41,381 of 123,879 reviewed websitesbeats 61%
- #27,425 of 69,702 online storesbeats 54%
- #26,427 of 63,406 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 990 ms |
| Oct 31, 2026 | 944 ms |
| Nov 7, 2026 | 919 ms |
| Nov 14, 2026 | 898 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 163 ms |
| Jul 11, 2026 | 165 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 174 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 159 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 151 ms |
| Nov 7, 2026 | 151 ms |
| Nov 14, 2026 | 151 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 431 KiBAbout 431 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Klaviyo and Yotpo and others), adding 1.3 MB and 696 ms of main-thread time.
Render-blocking requests
750 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Klaviyo adds 151 ms
151 msKlaviyo costs a phone 151 ms of main-thread work and 317 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.
1,685 HTML elements
The page has 1,685 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 65 ms
65 msazurefd.net costs a phone 65 ms of main-thread work and 334 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
130 ms · 36 KiB36 KiB could be saved by minifying JavaScript.
Reduce unused CSS
130 ms · 30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.
Improve image delivery
62 KiB4 images could be 62 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
56 KiB7 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Duplicated JavaScript
20 KiB20 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
1 checks passed
Server response: 38 ms
38 msYour server sent the HTML in 38 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.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NEW IN”.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Real-user INP: 232 ms
232 msReal visitors wait 232 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 149 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 475 ms
475 msReal visitors wait 475 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 115 ms
115 msScripts block the page for only 115 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 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).
Images and page weight
Page weight: 5.0 MB in 442 requests
5.0 MBYour homepage downloads 5.0 MB in 442 requests on a phone: media 1.7 MB (1), other files 1.4 MB (260) and scripts 1.3 MB (120). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
VIDEO_1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.6 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
ARIA attributes must conform to valid names (1 element)
ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Grungemama | Women's Rock and Bohemian Chic Fashion Boutique – GRUNGEMAMA”.
124 internal links, 6 external
The homepage links to 124 pages on grungemama.com and 6 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Grungemama: rebellious & confident women's fashion. Clothing, accessories, shoes: 20 new arrivals per week in limited s…”.
One H1 headline
Your main headline reads: “Grungemama | Women's Rock and Bohemian Chic Fashion Boutique”.
Canonical URL set
The canonical URL is https://www.grungemama.com/en.
Structured data in place
Structured data found: Organization and WebSite.
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.grungemama.com/sitemap.xml.
AI search readiness
4 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 (794 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.grungemama.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.grungemama.com/en/pages/rewards and https://www.grungemama.com/en/collections/black-week have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.grungemama.com/en/pages/rewards has 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 57 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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.
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 14 pages that loaded have a <title>.
Best practices
21 small tap targets
21 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 472 words of copy
The homepage carries about 472 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “GET MY 10% OFF”.
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Subscribe” and “100% WORRY-FREE ORDER”.
9 short forms
9 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
26 other companies contacted
Loading the homepage contacts 26 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 grungemama.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Loyalty Rewards · Microsoft Clarity · Klaviyo Email Marketing Sms · Wrapped · Addingwell · Axeptio · Wishlist Power · Fokkio Gift With Purchase · redirectify.app
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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on grungemama.com, including 13 speed issues, 1 SEO issue 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.