Website review, no card needed
supercutedresses.com website review
Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 77 checks
This review found 31 issues worth fixing on supercutedresses.com, 9 of them high impact, across 77 checks. The most urgent: avoid multiple page redirects. 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
80B- #38,600 of 97,390 reviewed websitesbeats 55%
- #24,704 of 52,991 online storesbeats 47%
- #23,707 of 48,041 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 963 ms |
| Jun 13, 2026 | 937 ms |
| Jun 20, 2026 | 927 ms |
| Jun 27, 2026 | 927 ms |
| Jul 4, 2026 | 917 ms |
| Jul 11, 2026 | 919 ms |
| Jul 18, 2026 | 918 ms |
| Jul 25, 2026 | 911 ms |
| Aug 1, 2026 | 912 ms |
| Aug 8, 2026 | 904 ms |
| Aug 15, 2026 | 905 ms |
| Aug 22, 2026 | 916 ms |
| Aug 29, 2026 | 921 ms |
| Sep 5, 2026 | 939 ms |
| Sep 12, 2026 | 919 ms |
| Sep 19, 2026 | 898 ms |
| Sep 26, 2026 | 889 ms |
| Oct 3, 2026 | 847 ms |
| Oct 10, 2026 | 841 ms |
| Oct 17, 2026 | 838 ms |
| Oct 24, 2026 | 830 ms |
| Oct 31, 2026 | 839 ms |
| Nov 7, 2026 | 825 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 82 ms |
| May 30, 2026 | 85 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 88 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 87 ms |
| Nov 7, 2026 | 88 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.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.8 s
Speed
Avoid multiple page redirects
4.8 sThe page goes through 1 redirect before it starts loading, costing about 4.8 s. Link and advertise the final URL directly.
6,053 HTML elements
The page has 6,053 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
890 ms · 151 KiBAbout 151 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 890 ms 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.
Improve image delivery
276 KiB13 images could be 276 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 95 ms
95 msShopify costs a phone 95 ms of main-thread work and 333 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Amazon Web Services and JSDelivr CDN and others), adding 708 KiB and 169 ms of main-thread time.
Legacy JavaScript
200 ms · 6 KiBPolyfills for old browsers add 6 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 40 KiB6 files are served with short cache lifetimes, so returning visitors download them again (40 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
12 KiBAbout 12 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
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 401 ms of it running JavaScript. That is comfortably low.
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Secret Garden ~ Hadassah Midi”.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 82 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 147 ms
147 msReal visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 505 ms
505 msReal visitors wait 505 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 346 requests
2.8 MBYour homepage downloads 2.8 MB in 346 requests on a phone: scripts 895 KiB (148), other files 811 KiB (118) and images 589 KiB (16). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Maria-SecretGarden_7.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 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 94.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Super Cute Dresses | Nursing, Modest, Maternity, Floral, Linen Dresses”.
Meta description is long (261 characters)
Your meta description is 261 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
52 internal links, 5 external
The homepage links to 52 pages on supercutedresses.com and 5 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.supercutedresses.com/.
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.supercutedresses.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,235 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.supercutedresses.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.supercutedresses.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.supercutedresses.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://www.supercutedresses.com/collections/formals, https://www.supercutedresses.com/collections/wraps, https://www.supercutedresses.com/collections/sale, https://www.supercutedresses.com/apps/loyalty and https://www.supercutedresses.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.supercutedresses.com/collections/formals, https://www.supercutedresses.com/collections/all-inventory-manual-add-for-tax-rate, https://www.supercutedresses.com/collections/nursing-dresses, https://www.supercutedresses.com/collections/linen-dresses, https://www.supercutedresses.com/collections/gift-card and https://www.supercutedresses.com/collections/wraps and 9 others have 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 23 found) and read each the way a search engine does.
3 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.
Titles are unique
Every page we checked has its own title.
Best practices
6 small tap targets
6 of 17 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 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 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 181 words
The homepage has only about 181 words of visible text; thin pages give Google and first-time buyers little to go on.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Contact” and “Join Now”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (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.
23 other companies contacted
Loading the homepage contacts 23 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 supercutedresses.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Aftersell · Appstle Loyalty · hextom.com · amazonaws.com
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
- Framework
- Bootstrap
- 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 31 issues on supercutedresses.com, including 10 speed issues, 4 SEO issues and 5 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.