Website review, no card needed
somos-reyes.com website review
Visit site (opens in a new tab)Reviewed 5 November 202653 issues · 92 checks
This review found 53 issues worth fixing on somos-reyes.com, 15 of them high impact, across 92 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
72C- #95,452 of 123,225 reviewed websitesbeats 19%
- #58,984 of 69,459 online storesbeats 12%
- #54,975 of 63,234 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 228 ms |
| May 23, 2026 | 214 ms |
| May 30, 2026 | 205 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 198 ms |
| Jun 20, 2026 | 198 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 195 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 200 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 192 ms |
| Oct 3, 2026 | 207 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 221 ms |
| Oct 24, 2026 | 220 ms |
| Oct 31, 2026 | 209 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
4.3 s
8.6 s
13.0 s
17.3 s
21.6 s
25.9 s
30.2 s
34.5 s
Speed
Main-thread work: 8.3 s
A phone's processor spends 8.3 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,621 HTML elements
The page has 4,621 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
250 ms · 4.1 MB80 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (ecomposer.app, pop-convert.com and Jivochat and others), adding 1.4 MB and 1.2 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 541 KiBAbout 541 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.
Render-blocking requests
400 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 380 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 58 KiBAbout 58 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.
Use efficient cache lifetimes
315 KiB18 files are served with short cache lifetimes, so returning visitors download them again (315 KiB).
ecomposer.app adds 262 ms
262 msecomposer.app costs a phone 262 ms of main-thread work and 154 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.
Jivochat adds 189 ms
189 msJivochat costs a phone 189 ms of main-thread work and 375 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 139 ms
139 msShopify costs a phone 139 ms of main-thread work and 364 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
150 ms · 43 KiB43 KiB could be saved by minifying JavaScript.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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.
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: 22 ms
22 msYour server sent the HTML in 22 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: 20.2 s
20.2 sThe page becomes fully interactive after 20.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.4 s
6.4 sYour largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 368 ms
368 msReal visitors wait 368 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 483 ms
483 msScripts block taps and scrolling for 483 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.111
0.111The layout shifts by 0.111 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 228 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 8.7 MB in 523 requests
8.7 MBYour homepage downloads 8.7 MB in 523 requests on a phone: images 5.1 MB (93), scripts 1.5 MB (95) and other files 1.5 MB (281). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
118 KiB4 images are downloaded at several times the size a phone draws them, for example WebSR-Categorias_Banner_Hero_mobile_Maletas-2.jpg at 1,333 px wide, shown at 390 px. Resized copies would save about 118 KiB.
6 images in older formats
6 images (271 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 2.5 g of CO₂ per visit
2.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.46 g of CO₂e: 294.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
57 tap targets too small
57 tap targets are too small or too close together to hit reliably with a finger.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (5 elements)
Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
Meta description is long (183 characters)
Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (BreadcrumbList, HomeGoodsStore and WebSite) but with 2 problems, for example “WebSite: sameAs is not an absolute URL ("pinterest.com/somosreyescom")”.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
515 internal links, 14 external
The homepage links to 515 pages on somos-reyes.com and 14 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Somos Reyes es la tienda online mexicana de hogar, deportes y herramientas. Calidad a precios imbatibles. Ofertas seman…”.
Title: 35 characters
Your title is a healthy 35 characters: “Todo en un solo Lugar | Somos Reyes”.
Canonical URL set
The canonical URL is https://www.somos-reyes.com/.
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.somos-reyes.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (2,156 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.somos-reyes.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.somos-reyes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.somos-reyes.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
https://www.somos-reyes.com/collections/colchones/Colchones-y-accesorios+Colchones-Queen and https://www.somos-reyes.com/collections/colchones/Colchones-y-accesorios+Colchones-King all use the title “Colchones - Somos Reyes – tagged "Colchones y Accesorios"”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.somos-reyes.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
11 pages share a meta description
https://www.somos-reyes.com/collections/colchones-y-domitorio, https://www.somos-reyes.com/collections/colchones-y-domitorio/Colchones and https://www.somos-reyes.com/collections/colchones-y-domitorio/Colchones-y-accesorios+Bases-de-cama-y-colchon use the same meta description. A description written for each page earns more clicks.
9 links to non-canonical URLs
Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.somos-reyes.com/collections/colchones/Colchones-y-accesorios+Colchones-Individuales, whose canonical is https://www.somos-reyes.com/collections/colchones/colchones-individuales+colchones-y-accesorios. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.somos-reyes.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.somos-reyes.com/collections/hogar/Colchones-y-accesorios+Bases-de-cama-y-colchon+base-individual-y-colchon and https://www.somos-reyes.com/collections/hogar/Colchones-y-accesorios+Bases-de-cama-y-colchon+base-matrimonial-y-colchon took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 158 found) and read each the way a search engine does.
1 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
45 small tap targets
45 of 167 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Boost > [ERROR] Failed to load themeCSS Error: Timeout loading asset themeCSS”.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 939 words of copy
The homepage carries about 939 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 3 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.
49 other companies contacted
Loading the homepage contacts 49 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 somos-reyes.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Variant Image Wizard Swatch · Trusted Faq · Tinyseo Seo Speed · Klaviyo Email Marketing Sms · Bss B2b Solution · Ecomposer Builder · Boost Ai Search Filter · Microsoft Clarity · Mercado Pago Antifraud Plus · Region Restrictions · Mercadopago Pf App · pop-convert.com · good-apps.co
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 53 issues on somos-reyes.com, including 24 speed issues, 2 SEO issues 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.