Website review, no card needed
yellowshop.es website review
Visit site (opens in a new tab)Reviewed 19 November 202637 issues · 85 checks
This review found 37 issues worth fixing on yellowshop.es, 12 of them high impact, across 85 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
79C- #55,753 of 125,068 reviewed websitesbeats 50%
- #36,562 of 70,104 online storesbeats 42%
- #35,015 of 63,708 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| 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.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 174 ms |
| Jul 11, 2026 | 173 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 175 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 188 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 199 ms |
| Sep 19, 2026 | 204 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 203 ms |
| Oct 31, 2026 | 197 ms |
| Nov 7, 2026 | 195 ms |
| Nov 14, 2026 | 193 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.7 s
3.3 s
5.0 s
6.6 s
8.3 s
9.9 s
11.6 s
13.2 s
Speed
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,249 HTML elements
The page has 4,249 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, pop-convert.com and Shopify and others), adding 2.0 MB and 1.1 s of main-thread time.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 229 KiB7 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Reduce unused JavaScript
676 KiBAbout 676 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
650 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Shopify adds 213 ms
213 msShopify costs a phone 213 ms of main-thread work and 1.2 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.
Clarity adds 326 ms
326 msClarity costs a phone 326 ms of main-thread work and 30 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.
Use efficient cache lifetimes
280 KiB31 files are served with short cache lifetimes, so returning visitors download them again (280 KiB).
Google Tag Manager adds 180 ms
180 msGoogle Tag Manager costs a phone 180 ms of main-thread work and 322 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 · 29 KiBAbout 29 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
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 CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 78 ms
78 msYour server sent the HTML in 78 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: 15.2 s
15.2 sThe page becomes fully interactive after 15.2 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 206 ms
206 msReal visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 157 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 541 ms
541 msReal visitors wait 541 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 80 ms
80 msScripts block the page for only 80 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 496 requests
7.5 MBYour homepage downloads 7.5 MB in 496 requests on a phone: media 2.5 MB (2), other files 1.7 MB (304) and scripts 1.7 MB (112). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
1ro_1_movil.png 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).
3 images far larger than shown
80 KiB3 images are downloaded at several times the size a phone draws them, for example 2ndo_3.png at 1,200 px wide, shown at 300 px. Resized copies would save about 80 KiB.
2 images below the first screen load straight away
2 images further down the page (43 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (1 element)
[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 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
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
435 internal links, 7 external
The homepage links to 435 pages on yellowshop.es and 7 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Envío 24/48h y devoluciones hasta 1 año. | Compra moda y calzado multimarca online para mujer y hombre con las últimas …”.
One H1 headline
Your main headline reads: “Yellowshop”.
Title: 34 characters
Your title is a healthy 34 characters: “YELLOWSHOP | Moda y calzado online”.
Canonical URL set
The canonical URL is https://www.yellowshop.es/.
Structured data in place
Structured data found: BreadcrumbList, Organization, VideoObject and WebSite.
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.yellowshop.es/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
No llms.txt
There is no https://www.yellowshop.es/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.
Text is in the HTML
Your server sends the page's text in the HTML (1,582 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.yellowshop.es/collections/ver-todo-mujer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.yellowshop.es/collections/novedades-mujer has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 162 found) and read each the way a search engine does.
5 checks passed
Linked pages load
4 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343175827&Ver=2&mid=5fdd64dc-c9ce-435b-8f41-66a857d4ec1e&bo=1&sid=8b42b690e45a11f186b74f19af84d849&vid=8b430060e45a11f19edbf768997e6e6d&vids=1&msclkid=N&pi=918639831&l.
15 small tap targets
15 of 63 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 “Access to fetch at 'https://api.zacaris.com/storefront/prices/lowest?variant=57662941954372&site=yellowshopbrand&market…”.
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 416 words of copy
The homepage carries about 416 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
10 short forms
10 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
46 other companies contacted
Loading the homepage contacts 46 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 yellowshop.es, 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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Selecty · Frequently Bought · Judge Me Reviews · Auto Login · Eg Auto Add To Cart · Tms Prod V 3c482b6 · Event Promotion Bar · Outsell Cross Sell Upsell · Ecomsend · Free Contact Form · pop-convert.com · outsellapp.com · hextom.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
- 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 37 issues on yellowshop.es, including 18 speed issues, 1 SEO issue 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.