Website review, no card needed
hotelcollection.es website review
Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 89 checks
This review found 47 issues worth fixing on hotelcollection.es, 17 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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
64D- #116,448 of 123,940 reviewed websitesbeats 5%
- #67,787 of 69,726 online storesbeats 2%
- #62,000 of 63,424 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 10.5 s |
| Jul 4, 2026 | 10.5 s |
| Jul 11, 2026 | 11.6 s |
| Jul 18, 2026 | 10.7 s |
| Jul 25, 2026 | 6.6 s |
| Aug 1, 2026 | 6.7 s |
| Sep 12, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 426 ms |
| Jun 20, 2026 | 453 ms |
| Jun 27, 2026 | 960 ms |
| Sep 12, 2026 | 429 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.4 s
8.7 s
13.1 s
17.5 s
21.8 s
26.2 s
30.6 s
35.0 s
Speed
Render-blocking requests
3.8 s34 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,633 HTML elements
The page has 5,633 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 (Google Tag Manager, Klaviyo and Clarity and others), adding 4.3 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
180 ms · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 180 ms faster on a phone.
Use efficient cache lifetimes
750 ms · 657 KiB40 files are served with short cache lifetimes, so returning visitors download them again (657 KiB).
Improve image delivery
1.1 MB7 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 755 ms
755 msGoogle Tag Manager costs a phone 755 ms of main-thread work and 1.7 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.
Klaviyo adds 357 ms
357 msKlaviyo costs a phone 357 ms of main-thread work and 725 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 162 ms
162 msShopify costs a phone 162 ms of main-thread work and 1.3 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.
rebuyengine.com adds 130 ms
130 msrebuyengine.com costs a phone 130 ms of main-thread work and 601 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.
Legacy JavaScript
150 ms · 82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Reduce unused CSS
76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
33 KiB33 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 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.
1 checks passed
Server response: 68 ms
68 msYour server sent the HTML in 68 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 46.9 s
46.9 sThe page becomes fully interactive after 46.9 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 779 ms
779 msScripts block taps and scrolling for 779 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.297
0.297The layout shifts by 0.297 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “20% de descuento adicional con el código: EXTRA20”. Most of its time is element render delay (1.9 s).
Tap response (INP) got 58% slower for real visitors
+58%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 426 ms to 429 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.9 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 images without width and height
5 images 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.
Images and page weight
Page weight: 8.2 MB in 459 requests
8.2 MBYour homepage downloads 8.2 MB in 459 requests on a phone: scripts 4.5 MB (184), images 2.4 MB (46) and other files 676 KiB (155). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.6 MB3 images are downloaded at several times the size a phone draws them, for example Bedding-pijamas_a268fe81-8e6e-4f6a-856f-9bc214a2dc0b.jpg at 4,160 px wide, shown at 32 px. Resized copies would save about 1.6 MB.
3 images in older formats
3 images (3.4 MB) 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.3 g of CO₂ per visit
2.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.33 g of CO₂e: 280.0 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
2 images without alt text
2 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 (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
43 tap targets too small
43 tap targets are too small or too close together to hit reliably with a finger.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (3 elements).
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
Meta description is long (202 characters)
Your meta description is 202 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
262 internal links, 12 external
The homepage links to 262 pages on hotelcollection.es and 12 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Difusores y fragancias inspiradas en hoteles icónicos | Hotel Collection”.
Title: 58 characters
Your title is a healthy 58 characters: “Esencias de Hotel & Productos Lifestyle | Hotel Collection”.
Canonical URL set
The canonical URL is https://www.hotelcollection.es/.
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://www.hotelcollection.es/sitemap.xml.
AI search readiness
4 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, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,485 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hotelcollection.es/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.hotelcollection.es/products/free-diffuser, which answers with an error. Visitors hit a dead end and search engines drop it.
7 pages without a meta description
https://www.hotelcollection.es/collections/exclusive-sale, https://www.hotelcollection.es/collections/studio-pro-scent-diffuser-collection, https://www.hotelcollection.es/collections/large-diffusers, https://www.hotelcollection.es/collections/fragrance-oil-best-sellers, https://www.hotelcollection.es/collections/fragrance-oil-new-arrivals and https://www.hotelcollection.es/collections/sample-packs and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.hotelcollection.es/collections/studio-pro-scent-diffuser-collection, whose canonical is https://www.hotelcollection.es/collections/studio-scent-diffuser-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.hotelcollection.es/collections/exclusive-sale, https://www.hotelcollection.es/collections/scent-diffusers, https://www.hotelcollection.es/collections/reed-diffusers, https://www.hotelcollection.es/collections/fragrance-oil, https://www.hotelcollection.es/collections/fragrance-oil-best-sellers and https://www.hotelcollection.es/collections/fragrance-oil-new-arrivals and 2 others have 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 126 found) and read each the way a search engine does.
3 checks passed
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 14 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://d2tcgmnynuc7pr.cloudfront.net/hotelcollection/graphics/hotelcollection_top_logo.jpg?t=1733154039.
39 small tap targets
39 of 68 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “❌ [WAIT-FOR-UTILS] Growi cookie utilities not loaded after 5 retries (500ms total)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 1,196 words of copy
The homepage carries about 1,196 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Log in or sign up”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 270 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 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.
42 cookies set on arrival
42Opening the homepage sets 42 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.
95 other companies contacted
Loading the homepage contacts 95 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 hotelcollection.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on hotelcollection.es, including 21 speed issues, 3 SEO issues and 1 conversion gap. 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.