Website review, no card needed
reginaromeroshoes.com website review
Visit site (opens in a new tab)Reviewed 12 November 202631 issues · 77 checks
This review found 31 issues worth fixing on reginaromeroshoes.com, 9 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
76C- #67,002 of 109,350 reviewed websitesbeats 34%
- #42,978 of 61,859 online storesbeats 26%
- #40,774 of 56,401 Shopify storesbeats 23%
Closest competitors among Shopify stores
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
Improve image delivery
2.8 s · 2.0 MB55 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
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
300 ms · 66 KiBAbout 66 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,977 HTML elements
The page has 1,977 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
200 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and shop.app), adding 62 KiB and 18 ms of main-thread time.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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.
Use efficient cache lifetimes
4 KiB2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 200 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Regina Romero International”.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
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.
1 image without width and height
1 image 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.
2 checks passed
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: 3.2 MB in 105 requests
3.2 MBYour homepage downloads 3.2 MB in 105 requests on a phone: images 2.7 MB (62), fonts 207 KiB (3) and scripts 181 KiB (27). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
239 KiB6 images are downloaded at several times the size a phone draws them, for example Regina_Romero_Bota_Botin_Maddie_Piel_Mango_1_40b941c0-125f-4 at 780 px wide, shown at 162 px. Resized copies would save about 239 KiB.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.0 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
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.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 91 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is short (60 characters)
Your meta description is only 60 characters: “Real Fashion for Real Women Est. 1984 Handmade Leather Shoes”. 70 to 160 characters is enough to sell the click.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
378 internal links, 9 external
The homepage links to 378 pages on reginaromeroshoes.com and 9 external pages.
6 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Handmade leather shoes | Regina Romero”.
Canonical URL set
The canonical URL is https://reginaromeroshoes.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://reginaromeroshoes.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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 (621 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://reginaromeroshoes.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://reginaromeroshoes.com/collections/sale and https://reginaromeroshoes.com/pages/wishlist, which answer with an error. Visitors hit a dead end and search engines drop them.
3 pages without a meta description
https://reginaromeroshoes.com/collections/all, https://reginaromeroshoes.com/collections/new-arrivals and https://reginaromeroshoes.com/collections/collections have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://reginaromeroshoes.com/collections/all, https://reginaromeroshoes.com/collections/limited-edition, https://reginaromeroshoes.com/collections/regina-collection, https://reginaromeroshoes.com/collections/shoes, https://reginaromeroshoes.com/collections/boots and https://reginaromeroshoes.com/collections/booties and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://reginaromeroshoes.com/collections/all, https://reginaromeroshoes.com/collections/limited-edition, https://reginaromeroshoes.com/collections/regina-collection, https://reginaromeroshoes.com/collections/boots, https://reginaromeroshoes.com/collections/booties and https://reginaromeroshoes.com/collections/new-arrivals and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 76 found) and read each the way a search engine does.
4 checks passed
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 12 pages that loaded have a <title>.
Best practices
157 small tap targets
157 of 264 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map 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: 11 customer or partner logos. 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 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 517 words of copy
The homepage carries about 517 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
10 calls to action
The homepage has 10 calls to action, for example “BUY NOW”, “SHOP NOW” and “SHOP”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 reginaromeroshoes.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
nfcube.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- 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 reginaromeroshoes.com, including 9 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.