Website review, no card needed

wohla.shop logo

wohla.shop website review

Visit site (opens in a new tab)Reviewed 8 November 202648 issues · 88 checks

This review found 48 issues worth fixing on wohla.shop, 19 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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.5 s1.6 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
112 ms93 msMay 16Oct 31104 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026102 ms
May 23, 202696 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 2026101 ms
Jun 27, 2026102 ms
Jul 4, 2026100 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202697 ms
Aug 15, 202696 ms
Aug 22, 202697 ms
Aug 29, 2026102 ms
Sep 5, 2026103 ms
Sep 12, 2026108 ms
Sep 19, 2026110 ms
Sep 26, 2026106 ms
Oct 3, 2026101 ms
Oct 10, 202696 ms
Oct 17, 202696 ms
Oct 24, 2026101 ms
Oct 31, 2026104 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 wohla.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wohla.shop at 0.7 s0.7 s
  2. wohla.shop at 1.4 s1.4 s
  3. wohla.shop at 2.1 s2.1 s
  4. wohla.shop at 2.9 s2.9 s
  5. wohla.shop at 3.6 s3.6 s
  6. wohla.shop at 4.3 s4.3 s
  7. wohla.shop at 5.0 s5.0 s
  8. wohla.shop at 5.7 s5.7 s

Speed

10 to fix53
  • Reduce unused JavaScript

    2.2 s · 511 KiB

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

  • Improve image delivery

    1.3 s · 226 KiB

    4 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 158 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vitals.app and Klaviyo and others), adding 1.3 MB and 1.0 s of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Render-blocking requests

    450 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 415 ms

    415 ms

    Google Tag Manager costs a phone 415 ms of main-thread work and 323 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.

  • Main-thread work: 3.2 s

    A phone's processor spends 3.2 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6 long tasks on the main thread

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

  • vitals.app adds 175 ms

    175 ms

    vitals.app costs a phone 175 ms of main-thread work and 425 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

    280 ms · 43 KiB

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

  • Legacy JavaScript

    150 ms · 40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 15.7 s

    15.7 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Time to Interactive: 17.1 s

    17.1 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Largest content (LCP) got 35% slower for real visitors

    +35%

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

  • Total Blocking Time: 235 ms

    235 ms

    Scripts block taps and scrolling for 235 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 751 ms

    751 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 237 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 237 requests on a phone: scripts 1.5 MB (90), other files 747 KiB (100) and images 396 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    180 KiB

    2 images are downloaded at several times the size a phone draws them, for example Website_icon_581c3c69-0aad-428f-ac4e-33880e3169e6.png at 2,160 px wide, shown at 47 px. Resized copies would save about 180 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (214 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

11 to fixGoogle 7785
  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • [role="img"] and [role="image"] elements must have alternative text (15 elements)

    [role="img"] and [role="image"] elements must have alternative text: 15 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 7558
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 35 internal links, 3 external

    The homepage links to 35 pages on wohla.shop and 3 external pages.

3 checks passed
  • Structured data in place

    Structured data found: Organization 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.wohla.shop/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.wohla.shop/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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix71
  • 6 pages without a title

    https://www.wohla.shop/collections/incontinentieondergoed-vrouwen, https://www.wohla.shop/collections/incontinentie-ondergoed-mannen, https://www.wohla.shop/collections/incontinentie-zwemkledij, https://www.wohla.shop/pages/veelgestelde-vragen, https://www.wohla.shop/pages/contact and https://www.wohla.shop/policies/privacy-policy have no <title>, so Google invents the link text in results.

  • 6 pages without a meta description

    https://www.wohla.shop/collections/incontinentieondergoed-vrouwen, https://www.wohla.shop/collections/incontinentie-ondergoed-mannen, https://www.wohla.shop/collections/incontinentie-zwemkledij, https://www.wohla.shop/pages/veelgestelde-vragen, https://www.wohla.shop/pages/contact and https://www.wohla.shop/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.wohla.shop/pages/veelgestelde-vragen and https://www.wohla.shop/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.wohla.shop/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    6 pages of 13 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9289
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 347 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

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, Klaviyo, Meta Pixel 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.

  • 17 cookies set on arrival

    17

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 wohla.shop, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Vitals · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Gdpr Backpack · provesrc.com · loox.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on wohla.shop, including 19 speed issues, 6 SEO issues 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