Website review, no card needed

laifen.eu logo

laifen.eu website review

Visit site (opens in a new tab)Reviewed 17 November 202637 issues · 92 checks

This review found 37 issues worth fixing on laifen.eu, 16 of them high impact, across 92 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
5.2 s1.5 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.8 s
Jun 6, 20264.2 s
Jun 13, 20264.5 s
Jun 20, 20264.8 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.5 s
Jul 25, 20264.1 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20262.9 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.0 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.4 s
Nov 7, 20262.2 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
352 ms220 msMay 30Nov 14237 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026267 ms
Jun 6, 2026269 ms
Jun 13, 2026289 ms
Jun 20, 2026303 ms
Jun 27, 2026309 ms
Jul 4, 2026312 ms
Jul 11, 2026311 ms
Jul 18, 2026303 ms
Jul 25, 2026291 ms
Aug 1, 2026274 ms
Aug 8, 2026264 ms
Aug 15, 2026245 ms
Aug 22, 2026238 ms
Aug 29, 2026235 ms
Sep 5, 2026320 ms
Sep 12, 2026319 ms
Sep 19, 2026325 ms
Sep 26, 2026337 ms
Oct 3, 2026276 ms
Oct 10, 2026311 ms
Oct 17, 2026312 ms
Oct 24, 2026307 ms
Oct 31, 2026294 ms
Nov 7, 2026249 ms
Nov 14, 2026237 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 laifen.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. laifen.eu at 0.5 s0.5 s
  2. laifen.eu at 0.9 s0.9 s
  3. laifen.eu at 1.4 s1.4 s
  4. laifen.eu at 1.9 s1.9 s
  5. laifen.eu at 2.4 s2.4 s
  6. laifen.eu at 2.8 s2.8 s
  7. laifen.eu at 3.3 s3.3 s
  8. laifen.eu at 3.8 s3.8 s

Speed

10 to fix45
  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and loox.io and others), adding 2.1 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Google Tag Manager adds 870 ms

    870 ms

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

  • 18 long tasks on the main thread

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

  • Shopify adds 323 ms

    323 ms

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

  • Use efficient cache lifetimes

    378 KiB

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

  • 2,284 HTML elements

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

  • Improve image delivery

    66 KiB

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

  • Reduce unused CSS

    47 KiB

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

  • Legacy JavaScript

    36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

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

  • Time to Interactive: 29.0 s

    29.0 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user INP: 231 ms

    231 ms

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

  • Real-user CLS: 0.21

    0.21

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

6 checks passed
  • 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 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: 724 ms

    724 ms

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

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

    -48%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 332 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 332 requests on a phone: scripts 2.7 MB (110), other files 921 KiB (112) and images 687 KiB (71). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.38 g

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

9 to fixGoogle 7788
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 13 text elements with low contrast

    13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 10 tap targets too small

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

  • Elements must only use permitted ARIA attributes (4 elements)

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

  • Orphan list items

    Some list items are not inside a list.

  • 11 images without alt text

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

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h4 → h6), 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. (2 elements).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

Google 92100
  • 190 internal links, 15 external

    The homepage links to 190 pages on laifen.eu and 15 external pages.

8 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Upgrade your daily routine with Laifen Europe. Discover our high-speed hair dryers, powerful shavers, and smart electri…”.

  • One H1 headline

    Your main headline reads: “Black Friday. Early Bird Access”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Laifen® Official Europe | Hair Dryers, Shavers & Toothbrushes”.

  • Canonical URL set

    The canonical URL is https://eu.laifentech.com/.

  • Structured data in place

    Structured data found: Brand, OnlineStore, 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://eu.laifentech.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://eu.laifentech.com/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: 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,795 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix68
  • 2 pages without a title

    https://eu.laifentech.com/products/air-hair-dryer and https://eu.laifentech.com/products/laifen-wave-pro-electric-toothbrush have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://eu.laifentech.com/products/laifen-neo-high-speed-hair-dryer and https://eu.laifentech.com/products/laifen-neo-special-high-speed-hair-dryer all use the title “American Express”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://eu.laifentech.com/products/air-hair-dryer, https://eu.laifentech.com/products/laifen-neo-high-speed-hair-dryer, https://eu.laifentech.com/products/laifen-neo-special-high-speed-hair-dryer and https://eu.laifentech.com/products/laifen-wave-pro-electric-toothbrush have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://eu.laifentech.com/products/laifen-wave-pro-electric-toothbrush has 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 53 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    8 pages of 15 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

4 to fixGoogle 4686
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 7 low-resolution images

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 777 words of copy

    The homepage carries about 777 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Black Friday. Early Bird Access Shop Now”.

  • 30 calls to action

    The homepage has 30 calls to action, for example “Buy”, “Bulk Order Inquiry” and “Track Your Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 28 testimonial or review blocks, 4 customer or partner logos and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 29 cookies set on arrival

    29

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

  • 57 other companies contacted

    Loading the homepage contacts 57 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 laifen.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 26 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Geo Pro Geolocation · Reelfy Videos · Uppromote Affiliate · Impact Com · Mida Replay Heatmaps · Simprosys Google Shopping Feed · Weglot Translate Your Store · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Seowill Ai Seo · Gdpr Cookie Consent · Easylocation · Affliate By Secomapp · Event Promotion Bar · Price Comparison Funnel · Sea Survey · Appstle Bundles · Ecomsend · Restockrocket · Mbcbundlesapp · Simple Social Login · loox.io · seel.com · hextom.com · amazonaws.com

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on laifen.eu, including 18 speed issues. 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