Website review, no card needed

whipl.de logo

whipl.de website review

Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 76 checks

This review found 26 issues worth fixing on whipl.de, 8 of them high impact, across 76 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.3 s1.8 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
236 ms160 msMay 16Oct 31180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026169 ms
May 23, 2026171 ms
May 30, 2026183 ms
Jun 6, 2026198 ms
Jun 13, 2026214 ms
Jun 20, 2026224 ms
Jun 27, 2026227 ms
Jul 4, 2026227 ms
Jul 11, 2026225 ms
Jul 18, 2026217 ms
Jul 25, 2026207 ms
Aug 1, 2026198 ms
Aug 8, 2026191 ms
Aug 15, 2026188 ms
Aug 22, 2026179 ms
Aug 29, 2026178 ms
Sep 5, 2026175 ms
Sep 12, 2026171 ms
Sep 19, 2026172 ms
Sep 26, 2026172 ms
Oct 3, 2026174 ms
Oct 10, 2026179 ms
Oct 17, 2026183 ms
Oct 24, 2026182 ms
Oct 31, 2026180 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 whipl.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. whipl.de at 0.6 s0.6 s
  2. whipl.de at 1.2 s1.2 s
  3. whipl.de at 1.9 s1.9 s
  4. whipl.de at 2.5 s2.5 s
  5. whipl.de at 3.1 s3.1 s
  6. whipl.de at 3.7 s3.7 s
  7. whipl.de at 4.4 s4.4 s
  8. whipl.de at 5.0 s5.0 s

Speed

3 to fix87
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 87

    87/100

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

  • 1,888 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 93 KiB

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

  • Reduce unused CSS

    51 KiB

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

  • Improve image delivery

    50 KiB

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

  • 8 third-party services on the page

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

  • Minify CSS

    8 KiB

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

  • 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: 1.3 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

3 to fix100
  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dein Haar. Deine Ausstrahlung. Dein Whipl.”. Most of its time is element render delay (2.6 s).

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.00

    0.00

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

  • 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: 269 ms

    269 ms

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

  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • Cumulative Layout Shift: 0

    0

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

  • 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

1 to fix70
  • Page weight: 7.9 MB in 95 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 95 requests on a phone: media 6.7 MB (1), scripts 654 KiB (38) and images 251 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.25 g

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

6 to fixGoogle 8691
  • Orphan list items

    Some list items are not inside a list.

  • 5 tap targets too small

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

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • 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
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Whipl Airstyler - Der Revolutionäre All-in-One Haarstyler für Perfekte”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Whipl” and “Whipl”). One clear main headline is easier for people and search engines.

  • Meta description is long (318 characters)

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

  • 144 internal links, 1 external

    The homepage links to 144 pages on whipl.de and 1 external page.

5 checks passed
  • Canonical URL set

    The canonical URL is https://whipl.de/.

  • 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://whipl.de/sitemap.xml.

AI search readiness

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

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

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

  • llms.txt published

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://whipl.de/products/straithair-pro-special declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://whipl.de/products/straithair-pro-special all use the title “Whipl Airstyler - Der Revolutionäre All-in-One Haarstyler für Perfekte”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://whipl.de/pages/kundenerfahrungen, https://whipl.de/collections/alle-produkte, https://whipl.de/collections/styling-tools, https://whipl.de/collections/whipl-care-haarpflege, https://whipl.de/collections/zubehor and https://whipl.de/products/whipl-care-liquid-gel and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://whipl.de/pages/kundenerfahrungen has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://whipl.de/products/whipl%E2%84%A2-airstyler-pro-gratis-ebook-kopie, https://whipl.de/products/whipl-care-liquid-gel, https://whipl.de/products/whipl-care-pflege-haarmaske, https://whipl.de/products/whipl%E2%84%A2-lederbox and https://whipl.de/products/whipl%E2%84%A2-blowoutburste-kopie took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10087
  • 5 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 582 words of copy

    The homepage carries about 582 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 500 testimonial or review blocks, 40 customer or partner logos, a star rating and 12 trust badges.

  • Analytics in place

    Analytics detected: 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.

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 whipl.de, 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 20 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Epa Easy Product Addons · Zigpoll Customer Surveys · Langshop · Kaching Bundles · Bundler Bundles App · Kip Payment Methods · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Ez Product Translate · Pagefly Ai Page Builder · Multifeeds · Gdpr Cookie Consent · Page Speed Optimizer · Sternify · Restockrocket · loox.io · goaffpro.com · oceanpayment.com · nice-team.net

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 26 issues on whipl.de, including 6 speed issues, 3 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