Website review, no card needed

trybeautylux.com logo

trybeautylux.com website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 85 checks

This review found 38 issues worth fixing on trybeautylux.com, 9 of them high impact, across 85 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.6 s2.1 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
228 ms143 msMay 16Oct 31179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026159 ms
May 30, 2026153 ms
Jun 6, 2026176 ms
Jun 13, 2026174 ms
Jun 20, 2026171 ms
Jun 27, 2026184 ms
Jul 4, 2026171 ms
Jul 11, 2026175 ms
Jul 18, 2026177 ms
Jul 25, 2026162 ms
Aug 1, 2026169 ms
Aug 8, 2026171 ms
Aug 15, 2026171 ms
Aug 22, 2026195 ms
Aug 29, 2026195 ms
Sep 5, 2026186 ms
Sep 12, 2026194 ms
Sep 19, 2026185 ms
Sep 26, 2026189 ms
Oct 3, 2026198 ms
Oct 10, 2026218 ms
Oct 17, 2026218 ms
Oct 24, 2026193 ms
Oct 31, 2026179 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 trybeautylux.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. trybeautylux.com at 0.8 s0.8 s
  2. trybeautylux.com at 1.5 s1.5 s
  3. trybeautylux.com at 2.3 s2.3 s
  4. trybeautylux.com at 3.0 s3.0 s
  5. trybeautylux.com at 3.8 s3.8 s
  6. trybeautylux.com at 4.5 s4.5 s
  7. trybeautylux.com at 5.3 s5.3 s
  8. trybeautylux.com at 6.1 s6.1 s

Speed

10 to fix53
  • Reduce unused JavaScript

    4.8 s · 949 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and OptiMonk and others), adding 1.7 MB and 1.1 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.

  • Use efficient cache lifetimes

    700 ms · 293 KiB

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

  • Google Tag Manager adds 495 ms

    495 ms

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

  • Render-blocking requests

    500 ms

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

  • Main-thread work: 3.8 s

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

  • Duplicated JavaScript

    300 ms · 17 KiB

    17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

  • 1,677 HTML elements

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

  • Klaviyo adds 119 ms

    119 ms

    Klaviyo costs a phone 119 ms of main-thread work and 315 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.

  • Legacy JavaScript

    150 ms · 64 KiB

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    46 KiB

    46 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    45 KiB

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

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

    7 ms

    Your server sent the HTML in 7 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: 21.1 s

    21.1 s

    Your largest element takes 21.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make time for your skin Because self-care is a necessity Sh…”.

  • Time to Interactive: 23.7 s

    23.7 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Total Blocking Time: 363 ms

    363 ms

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

  • 2 images without width and height

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 171 ms

    171 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • 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: 3.5 MB in 294 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 294 requests on a phone: scripts 2.3 MB (108), other files 852 KiB (152) and fonts 143 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    11 KiB

    1 image is downloaded at several times the size a phone draws it, for example d89a1bfa-bddd-4ab5-b2ab-01e3b6394b61 at 1,084 px wide, shown at 330 px. Resized copies would save about 11 KiB.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9297
  • 14 text elements with low contrast

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

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (9 characters)

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“Make time for your skin”, “Shop Skin Care” and “Shop Hair & Body Care”). One clear main headline is easier for people and search engines.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 53 internal links, 5 external

    The homepage links to 53 pages on trybeautylux.com and 5 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Beautylux works naturally to help replenish your skin’s moisture, firming its appearance and restoring your natural glo…”.

  • Canonical URL set

    The canonical URL is https://www.trybeautylux.com/.

  • Structured data in place

    Structured data found: 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://www.trybeautylux.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

7 to fix50
  • 1 page without a title

    https://www.trybeautylux.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 2 pages point its canonical at the homepage

    https://www.trybeautylux.com/products/detoxifying-charcoal-mask and https://www.trybeautylux.com/products/cc-serum declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 4 linked pages hidden from search

    https://www.trybeautylux.com/pages/subscriptionpage, https://www.trybeautylux.com/customer_authentication/redirect, https://www.trybeautylux.com/collections/face and https://www.trybeautylux.com/collections/hair-body are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages share 2 titles

    /, https://www.trybeautylux.com/products/detoxifying-charcoal-mask and https://www.trybeautylux.com/products/cc-serum all use the title “BeautyLux”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.trybeautylux.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.trybeautylux.com/pages/all-products, https://www.trybeautylux.com/blogs/news, https://www.trybeautylux.com/products/detoxifying-charcoal-mask, https://www.trybeautylux.com/products/cc-serum, https://www.trybeautylux.com/collections/face and https://www.trybeautylux.com/collections/hair-body use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.trybeautylux.com/pages/subscriptionpage and https://www.trybeautylux.com/customer_authentication/redirect 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 23 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.trybeautylux.com/.

  • 6 JavaScript errors while loading

    6 errors were 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

    10 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 427 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop all products”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop all products”, “Learn more” and “Shop Skin Care”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies, 2 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.

  • 48 other companies contacted

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

Apps your storefront loads

Sitemap Noindex Pro Seo · Optimonk Popup Cro A B Test · Klaviyo Email Marketing Sms · Onepixel · nice-team.net · wickedreports.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 Tag Manager
Hosting
Shopify

Company

Headquarters
Yogyakarta

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on trybeautylux.com, including 19 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