Website review, no card needed

duoboots.eu logo

duoboots.eu website review

Visit site (opens in a new tab)Reviewed 13 November 202629 issues · 70 checks

This review found 29 issues worth fixing on duoboots.eu, 11 of them high impact, across 70 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

Full-page screenshot of duoboots.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. duoboots.eu at 0.4 s0.4 s
  2. duoboots.eu at 0.8 s0.8 s
  3. duoboots.eu at 1.2 s1.2 s
  4. duoboots.eu at 1.6 s1.6 s
  5. duoboots.eu at 2.1 s2.1 s
  6. duoboots.eu at 2.5 s2.5 s
  7. duoboots.eu at 2.9 s2.9 s
  8. duoboots.eu at 3.3 s3.3 s

Speed

6 to fix59
  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.9 s · 372 KiB

    About 372 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Mobile performance score: 59

    59/100

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

  • Use efficient cache lifetimes

    550 ms · 138 KiB

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

  • Improve image delivery

    376 KiB

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

  • Google Tag Manager adds 229 ms

    229 ms

    Google Tag Manager costs a phone 229 ms of main-thread work and 332 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 (Google Tag Manager, Clarity and Hotjar and others), adding 752 KiB and 477 ms of main-thread time.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    30 ms · 31 KiB

    About 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 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.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix65
  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 12.2 s

    12.2 s

    The page becomes fully interactive after 12.2 s. Good is under 3.8 s.

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Speed Index: 6.6 s

    6.6 s

    Visually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.

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

2 checks passed
  • Total Blocking Time: 145 ms

    145 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.9 MB in 206 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 206 requests on a phone: other files 965 KiB (119), images 942 KiB (31) and scripts 921 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    250318_DUO_SHOES_SS25_Homepage_Moble_720_x_1280_17.jpg 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).

  • About 0.8 g of CO₂ per visit

    0.83 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10095
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (32 elements)

    All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 6953
  • Page is set to noindex

    The robots meta tag says “noindex,follow”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Wide Calf Knee High Boots | Eight Inclusive Calf Widths | Duoboots IE – DuoBoots EU”.

  • Meta description is long (163 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “WebPage: image is not an absolute URL ("//duoboots.eu/cdn/shop/files/favicon_806e05ef-8bc0-4561-846…”.

  • 107 internal links, 16 external

    The homepage links to 107 pages on duoboots.eu and 16 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “(Almost!) Custom-made women's boots”.

  • Canonical URL set

    The canonical URL is https://duoboots.eu/.

  • 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://duoboots.eu/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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 (633 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix88
  • 15 linked pages hidden from search

    https://duoboots.eu/collections/knee-high-boots, https://duoboots.eu/collections/flat-heel-boots, https://duoboots.eu/collections/heeled-boots, https://duoboots.eu/collections/lace-up-boots, https://duoboots.eu/products/duoboots-gift-card-us and https://duoboots.eu/collections/all-womens-boots-and-ankle-boots and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 8 pages without an H1

    https://duoboots.eu/collections/knee-high-boots, https://duoboots.eu/collections/heeled-boots, https://duoboots.eu/collections/all-womens-boots-and-ankle-boots, https://duoboots.eu/collections/wide-calf-boots, https://duoboots.eu/collections/narrow-calf-boots and https://duoboots.eu/collections/the-summer-edit 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 52 found) and read each the way a search engine does.

5 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 a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343035073&Ver=2&mid=dda19f9c-682a-49fb-aba6-151ba6464c38&bo=1&sid=fbf912c0defb11f1ba5a19b042936355&vid=fbf91ee0defb11f19312c3445b3c73ec&vids=1&msclkid=N&pi=918639831&l.

  • 43 small tap targets

    43 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'includes')”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 495 words of copy

    The homepage carries about 495 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop all” and “What’s hot Shop Knee High Boots”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop”, “Shop All” and “Shop all”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 duoboots.eu, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Easy Tag Gtm Data Layer · weglot.com · rakutenadvertising.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

E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on duoboots.eu, including 10 speed issues, 5 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

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