Website review, no card needed
equivalenza.com website review
Visit site (opens in a new tab)Reviewed 31 October 202640 issues · 88 checks
This review found 40 issues worth fixing on equivalenza.com, 13 of them high impact, across 88 checks. The most urgent: mobile performance score: 46. 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- #73,962 of 121,527 reviewed websitesbeats 34%
- #47,601 of 68,759 online storesbeats 26%
- #45,139 of 62,655 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 175 ms |
| May 16, 2026 | 178 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 183 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 216 ms |
| Jul 18, 2026 | 217 ms |
| Jul 25, 2026 | 219 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 243 ms |
| Aug 15, 2026 | 250 ms |
| Aug 22, 2026 | 252 ms |
| Aug 29, 2026 | 248 ms |
| Sep 5, 2026 | 248 ms |
| Sep 12, 2026 | 252 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 251 ms |
| Oct 3, 2026 | 248 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 249 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.2 s
2.4 s
3.5 s
4.7 s
5.9 s
7.1 s
8.3 s
9.5 s
Speed
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,527 HTML elements
The page has 4,527 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 (Shopify, Google Tag Manager and YouTube and others), adding 2.7 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Improve image delivery
737 KiB24 images could be 737 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 668 ms
668 msShopify costs a phone 668 ms of main-thread work and 508 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.
Google Tag Manager adds 494 ms
494 msGoogle Tag Manager costs a phone 494 ms of main-thread work and 928 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.
YouTube adds 435 ms
435 msYouTube costs a phone 435 ms of main-thread work and 1,014 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.
Render-blocking requests
450 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
270 ms · 129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
Use efficient cache lifetimes
114 KiB16 files are served with short cache lifetimes, so returning visitors download them again (114 KiB).
Duplicated JavaScript
22 KiB22 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
22 KiB22 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: 10 ms
10 msYour server sent the HTML in 10 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: 25.2 s
25.2 sThe page becomes fully interactive after 25.2 s. Good is under 3.8 s.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 375 ms
375 msReal visitors wait 375 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 175 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.155
0.155The layout shifts by 0.155 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Descubre todos tus nuevos perfumes "must"”. Most of its time is element render delay (3.6 s).
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 584 ms
584 msReal visitors wait 584 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.0 MB in 300 requests
6.0 MBYour homepage downloads 6.0 MB in 300 requests on a phone: scripts 2.8 MB (103), images 1,002 KiB (40) and media 861 KiB (2). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
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 (13 elements)
Scrollable region must have keyboard access: 13 elements on the page fail this check, rated serious by axe-core.
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.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
34 links crawlers can't follow
34 links have no real href, so search engines can't follow them.
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.
409 internal links, 16 external
The homepage links to 409 pages on equivalenza.com and 16 external pages.
8 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Perfumes de calidad creados por expertos. Personaliza tu esencia y reutiliza tu frasco. Más sostenible, más ahorro, más…”.
One H1 headline
Your main headline reads: “Equivalenza | Perfumes, aromas y cosméticos”.
Title: 56 characters
Your title is a healthy 56 characters: “Equivalenza | Perfumes Únicos y Recargables | Fragancias”.
Canonical URL set
The canonical URL is https://equivalenza.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://equivalenza.com/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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (1,538 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://equivalenza.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a title
https://equivalenza.com/pages/equilovers, https://equivalenza.com/pages/encuentra-tu-tienda and https://equivalenza.com/pages/wishlist all use the title “Apple Pay”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://equivalenza.com/pages/equilovers, https://equivalenza.com/pages/encuentra-tu-tienda and https://equivalenza.com/pages/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://equivalenza.com/pages/equilovers 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 132 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 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=97213560&tm=gtm002&Ver=2&mid=332b0c2f-8ec6-441b-9f24-bc563f03c734&bo=1&sid=75a2c000d4d011f18976313330050571&vid=75a2c230d4d011f1affb29af56a2e5ec&vids=1&msclkid=N>m_t.
10 small tap targets
10 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “No se encontró el formulario de producto o el botón de wishlist.”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 702 words of copy
The homepage carries about 702 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Wood Reserve”.
14 short forms
14 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 23 testimonial or review blocks, 2 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 4 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
42 other companies contacted
Loading the homepage contacts 42 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 equivalenza.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- 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 40 issues on equivalenza.com, including 21 speed issues, 2 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.