Website review, no card needed

voucler.com logo

voucler.com website review

Visit site (opens in a new tab)Reviewed 17 November 202626 issues · 79 checks

This review found 26 issues worth fixing on voucler.com, 7 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s691 msMay 30Nov 14925 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.5 s
Jun 13, 20262.2 s
Jun 20, 20262.0 s
Jun 27, 20261.8 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Nov 7, 2026999 ms
Nov 14, 2026925 ms
Real-visitor tap response (INP)75th percentile, phones
306 ms208 msMay 30Nov 14259 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026219 ms
Jun 6, 2026244 ms
Jun 13, 2026239 ms
Jun 20, 2026248 ms
Jun 27, 2026250 ms
Jul 4, 2026249 ms
Jul 11, 2026254 ms
Jul 18, 2026249 ms
Jul 25, 2026250 ms
Aug 1, 2026253 ms
Aug 8, 2026251 ms
Aug 15, 2026248 ms
Aug 22, 2026247 ms
Aug 29, 2026252 ms
Sep 5, 2026257 ms
Sep 12, 2026272 ms
Sep 19, 2026284 ms
Sep 26, 2026290 ms
Oct 3, 2026289 ms
Oct 10, 2026295 ms
Oct 17, 2026294 ms
Oct 24, 2026287 ms
Oct 31, 2026290 ms
Nov 7, 2026273 ms
Nov 14, 2026259 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

Full-page screenshot of voucler.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. voucler.com at 0.4 s0.4 s
  2. voucler.com at 0.8 s0.8 s
  3. voucler.com at 1.1 s1.1 s
  4. voucler.com at 1.5 s1.5 s
  5. voucler.com at 1.9 s1.9 s
  6. voucler.com at 2.3 s2.3 s
  7. voucler.com at 2.6 s2.6 s
  8. voucler.com at 3.0 s3.0 s

Speed

5 to fix74
  • Render-blocking requests

    1.1 s

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    570 KiB

    15 images could be 570 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2,808 HTML elements

    The page has 2,808 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 5 ms

    5 ms

    Shopify costs a phone 5 ms of main-thread work and 510 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Fonts and JSDelivr CDN and others), adding 774 KiB and 5 ms of main-thread time.

  • Reduce unused CSS

    38 KiB

    About 38 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    37 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).

  • 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 55 ms of it running JavaScript. That is comfortably low.

  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix33
  • 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.

  • Cumulative Layout Shift: 0.622

    0.622

    The layout shifts by 0.622 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user INP: 259 ms

    259 ms

    Real visitors wait 259 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.13

    0.13

    For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • Tap response (INP) got 15% slower for real visitors

    +15%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 219 ms to 259 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Real-user LCP: 0.9 s

    0.9 s

    Real visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 731 ms

    731 ms

    Real visitors wait 731 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 60% faster for real visitors

    -60%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.3 s

    2.3 s

    The page is fully interactive after 2.3 s.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 8.9 MB in 129 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 129 requests on a phone: media 5.7 MB (1), images 2.0 MB (34) and scripts 665 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    MantaWARMESSENCEgris_dormitorio.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).

  • 2 images far larger than shown

    122 KiB

    2 images are downloaded at several times the size a phone draws them, for example STONE_ESSENCE_PACK_2_5900e08c-182f-4b23-a8bb-e0939dfa7c53_10 at 1,024 px wide, shown at 81 px. Resized copies would save about 122 KiB.

  • About 2.5 g of CO₂ per visit

    2.51 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.51 g of CO₂e: 301.5 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

5 to fixGoogle 9193
  • Elements must only use permitted ARIA attributes (5 elements)

    Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

  • 68 images without alt text

    68 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.

  • 18 links without text

    18 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.

1 checks passed
  • 48 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: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (161 characters)

    Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 181 internal links, 12 external

    The homepage links to 181 pages on voucler.com and 12 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Get a head start on Christmas gifting”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Voucler | The ritual of home: bed linen, bath and fragrances”.

  • Canonical URL set

    The canonical URL is https://voucler.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, OnlineStore, Organization, WebPage 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://voucler.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,391 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://voucler.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 1 page slow to respond

    https://voucler.com/products/pure-bamboo-fabric-fitted-sheet took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 106 found) and read each the way a search engine does.

7 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    20 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • 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 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.

  • About 889 words of copy

    The homepage carries about 889 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Shop now”.

  • 29 short forms

    29 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 voucler.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

Consentmo Gdpr · Addingwell · Klaviyo Email Marketing Sms · Judge Me Reviews · Gorgias Live Chat Helpdesk · Microsoft Clarity · Gdpr Backpack · Orbe Geolocation · Forms · Revenuehunt · Freegifts · Discos Smart Bogo Cart Upsell · cloudfront.net · bogos.io

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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Founded
2024
Headquarters
Madrid

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on voucler.com, including 10 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25