Website review, no card needed

lashbabe-shop.com logo

lashbabe-shop.com website review

Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 73 checks

This review found 31 issues worth fixing on lashbabe-shop.com, 6 of them high impact, across 73 checks. The most urgent: page weight: 4.9 MB in 353 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
1.5 s1.1 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
182 ms131 msMay 16Oct 31176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026138 ms
May 23, 2026138 ms
May 30, 2026138 ms
Jun 6, 2026137 ms
Jun 13, 2026144 ms
Jun 20, 2026147 ms
Jun 27, 2026154 ms
Jul 4, 2026162 ms
Jul 11, 2026171 ms
Jul 18, 2026172 ms
Jul 25, 2026169 ms
Aug 1, 2026163 ms
Aug 8, 2026161 ms
Aug 15, 2026161 ms
Aug 22, 2026161 ms
Aug 29, 2026156 ms
Sep 5, 2026154 ms
Sep 12, 2026157 ms
Sep 19, 2026161 ms
Sep 26, 2026167 ms
Oct 3, 2026166 ms
Oct 10, 2026162 ms
Oct 17, 2026157 ms
Oct 24, 2026160 ms
Oct 31, 2026176 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 lashbabe-shop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lashbabe-shop.com at 1.0 s1.0 s
  2. lashbabe-shop.com at 2.0 s2.0 s
  3. lashbabe-shop.com at 3.0 s3.0 s
  4. lashbabe-shop.com at 4.0 s4.0 s
  5. lashbabe-shop.com at 5.0 s5.0 s
  6. lashbabe-shop.com at 6.0 s6.0 s
  7. lashbabe-shop.com at 7.0 s7.0 s
  8. lashbabe-shop.com at 8.0 s8.0 s

Speed

9 to fix69
  • Reduce unused JavaScript

    300 ms · 920 KiB

    About 920 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Improve image delivery

    500 ms · 607 KiB

    15 images could be 607 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 69

    69/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, trengo.eu and Shopify and others), adding 2.0 MB and 774 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Google Tag Manager adds 322 ms

    322 ms

    Google Tag Manager costs a phone 322 ms of main-thread work and 653 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.1 s

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

  • trengo.eu adds 173 ms

    173 ms

    trengo.eu costs a phone 173 ms of main-thread work and 415 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.

  • 1,540 HTML elements

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

  • Use efficient cache lifetimes

    175 KiB

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

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    58 KiB

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

  • Reduce unused CSS

    41 KiB

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

  • Minify CSS

    22 KiB

    22 KiB could be saved by minifying CSS.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 69 ms

    69 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 21.1 s

    21.1 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Try our Studio look”.

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

    +22%

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Total Blocking Time: 285 ms

    285 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

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

    1.1 s

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

  • Real-user INP: 178 ms

    178 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 369 ms

    369 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

2 to fix64
  • Page weight: 4.9 MB in 353 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 353 requests on a phone: scripts 2.1 MB (94), images 1.5 MB (51) and other files 1.2 MB (187). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    EN_-_MOBILE_AQUA.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 1.4 g of CO₂ per visit

    1.40 g

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

5 to fixGoogle 8993
  • Unlabelled dropdowns

    3 dropdowns have no label.

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

  • 6 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 22 links without text

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

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

5 to fixGoogle 8579
  • Title is short (10 characters)

    Your title is only 10 characters: “bylashbabe”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No XML sitemap

    No XML sitemap at https://bylashbabe.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at bylashbabe.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 143 internal links, 16 external

    The homepage links to 143 pages on lashbabe-shop.com and 16 external pages.

3 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Pre-glued lashes, Lash Vitamins and clusters you apply at home in minutes. Plus lips and brows. Order before 22:00 for …”.

  • One H1 headline

    Your main headline reads: “Lashbabe – pre-glued lashes, Lash Vitamins and clusters to apply yourself”.

  • Canonical URL set

    The canonical URL is https://bylashbabe.com/en.

AI search readiness

1 to fix81
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://bylashbabe.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.

1 checks passed
  • Text is in the HTML

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

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 859 words of copy

    The homepage carries about 859 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE TREATMENTS” and “TRY THE STUDIO”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop”, “Starter Kits start here” and “Try the Studio”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

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.

  • 26 cookies set on arrival

    26

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

  • 44 other companies contacted

    Loading the homepage contacts 44 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 lashbabe-shop.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Eu Widerruf Button

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 31 issues on lashbabe-shop.com, including 15 speed issues, 5 SEO issues and 1 conversion gap. 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