Website review, no card needed
alegriashoes.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 81 checks
This review found 34 issues worth fixing on alegriashoes.com, 10 of them high impact, across 81 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
77C- #61,430 of 109,350 reviewed websitesbeats 39%
- #39,793 of 61,859 online storesbeats 31%
- #37,892 of 56,401 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 187 ms |
| May 30, 2026 | 202 ms |
| Jun 6, 2026 | 229 ms |
| Jun 13, 2026 | 261 ms |
| Jun 20, 2026 | 293 ms |
| Jun 27, 2026 | 321 ms |
| Jul 4, 2026 | 338 ms |
| Jul 11, 2026 | 351 ms |
| Jul 18, 2026 | 355 ms |
| Jul 25, 2026 | 357 ms |
| Aug 1, 2026 | 369 ms |
| Aug 8, 2026 | 370 ms |
| Aug 15, 2026 | 369 ms |
| Aug 22, 2026 | 369 ms |
| Aug 29, 2026 | 368 ms |
| Sep 5, 2026 | 368 ms |
| Sep 12, 2026 | 348 ms |
| Sep 19, 2026 | 320 ms |
| Sep 26, 2026 | 262 ms |
| Oct 3, 2026 | 211 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 152 ms |
| Oct 31, 2026 | 153 ms |
| Nov 7, 2026 | 152 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.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
1.1 s · 2.1 MB7 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Shopify and others), adding 1.4 MB and 585 ms of main-thread time.
Reduce unused CSS
300 ms · 97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,962 HTML elements
The page has 2,962 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 954 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
257 KiBAbout 257 KiB of JavaScript is downloaded but never used on this page.
Klaviyo adds 163 ms
163 msKlaviyo costs a phone 163 ms of main-thread work and 449 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.
Shopify adds 118 ms
118 msShopify costs a phone 118 ms of main-thread work and 404 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
48 KiB9 files are served with short cache lifetimes, so returning visitors download them again (48 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 482 ms
482 msReal visitors wait 482 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
8 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 534 ms
534 msReal visitors wait 534 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 187 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 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.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 10.2 MB in 392 requests
10.2 MBYour homepage downloads 10.2 MB in 392 requests on a phone: images 7.3 MB (39), scripts 1.4 MB (187) and other files 882 KiB (141). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.89 g of CO₂e: 346.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Alegria™ Shoes - Official Brand Site - Women's Comfort Shoes – Alegria Shoes”.
Meta description is long (281 characters)
Your meta description is 281 characters; Google truncates after about 160, so the end of your pitch is cut.
195 internal links, 7 external
The homepage links to 195 pages on alegriashoes.com and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Alegria Shoes”.
Canonical URL set
The canonical URL is https://alegriashoes.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://alegriashoes.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://alegriashoes.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.
2 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, sameAs (social profiles), description and contact details; logo would complete it.
Other pages
1 page without a meta description
https://alegriashoes.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://alegriashoes.com/products/keli-feel-good-white-shoe and https://alegriashoes.com/products/keli-feel-good-chocolate-shoe use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://alegriashoes.com/collections/peanuts 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 84 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 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 5 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: the server responded with a status of 429 ()”.
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.
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.
Thin social proof
Social proof on the homepage: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 10 words
The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
16 calls to action
The homepage has 16 calls to action, for example “SHOP NOW”, “Shop” and “Shop Collection”.
18 short forms
18 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
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 alegriashoes.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Simprosys Google Shopping Feed · Accessibility Spark · Judge Me Reviews · Smart Seo · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Easy Tabs Product Tabs · Bixgrow Affiliate · Back In Stock · faq-king.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Ontario
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on alegriashoes.com, including 16 speed issues, 2 SEO issues and 6 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.