Website review, no card needed
shimmermolly.com website review
Visit site (opens in a new tab)Reviewed 9 November 202629 issues · 77 checks
This review found 29 issues worth fixing on shimmermolly.com, 11 of them high impact, across 77 checks. The most urgent: page weight: 242.9 MB in 487 requests. 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- #40,291 of 119,792 reviewed websitesbeats 61%
- #26,860 of 67,919 online storesbeats 54%
- #25,902 of 61,905 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 171 ms |
| May 30, 2026 | 172 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 182 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 183 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 188 ms |
| Nov 7, 2026 | 167 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.0 s
2.1 s
3.1 s
4.1 s
5.2 s
6.2 s
7.2 s
8.3 s
Speed
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,270 HTML elements
The page has 3,270 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, xcottons.com and shop.app and others), adding 238.8 MB and 707 ms of main-thread time.
Shopify adds 547 ms
547 msShopify costs a phone 547 ms of main-thread work and 238.4 MB 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.
Improve image delivery
750 ms · 1.3 MB19 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
572 KiBAbout 572 KiB of JavaScript is downloaded but never used on this page.
xcottons.com adds 147 ms
147 msxcottons.com costs a phone 147 ms of main-thread work and 341 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
150 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB5 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Magenta Satin Trim Sequin Mini Dress”.
Time to Interactive: 18.2 s
18.2 sThe page becomes fully interactive after 18.2 s. Good is under 3.8 s.
Real-user INP: 306 ms
306 msReal visitors wait 306 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 171 ms to 167 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 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: 522 ms
522 msReal visitors wait 522 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 87 ms
87 msScripts block the page for only 87 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 242.9 MB in 487 requests
242.9 MBYour homepage downloads 242.9 MB in 487 requests on a phone: media 236.8 MB (34), images 2.8 MB (51) and scripts 1.8 MB (175). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
828 KiB7 images are downloaded at several times the size a phone draws them, for example 111.jpg at 960 px wide, shown at 56 px. Resized copies would save about 828 KiB.
29 images below the first screen load straight away
29 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images in older formats
3 images (495 KiB) 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 68.8 g of CO₂ per visit
68.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 68.84 g of CO₂e: 8260.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
29 elements hidden from screen readers can still receive keyboard focus.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“ShimmerMolly” and “BORN TO SPARKLE”). One clear main headline is easier for people and search engines.
214 internal links, 6 external
The homepage links to 214 pages on shimmermolly.com and 6 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Discover ShimmerMolly’s collection of trendy women’s dresses, tops, skirts and occasion-ready styles. Shop fashionable …”.
Title: 47 characters
Your title is a healthy 47 characters: “ShimmerMolly | Trendy Women’s Dresses & Fashion”.
Canonical URL set
The canonical URL is https://shimmermolly.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://shimmermolly.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,002 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://shimmermolly.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 102 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
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”.
2 checks passed
Tap targets are thumb-sized
86 of 90 tappable elements near the top are at least 24 px.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 167 words
The homepage has only about 167 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP DRESSES”.
5 calls to action
The homepage has 5 calls to action, for example “SHOP DRESSES”, “Shop now” and “Contact ShimmerMolly”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
20 other companies contacted
Loading the homepage contacts 20 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 shimmermolly.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Snap Product Badges Labels · Xcotton Guard · Tec Growth Geo Optimizer · Parkour Tiktok Pixel · Snap Price Design Icon · Glo Color Swatch
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
- Hosting
- Shopify
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 shimmermolly.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.