Website review, no card needed

beautyhaul.com logo

beautyhaul.com website review

Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 85 checks

This review found 34 issues worth fixing on beautyhaul.com, 9 of them high impact, across 85 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.7 s2.2 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.5 s
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.0 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
252 ms137 msMay 2Oct 17150 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026239 ms
May 9, 2026218 ms
May 16, 2026202 ms
May 23, 2026194 ms
May 30, 2026192 ms
Jun 6, 2026196 ms
Jun 13, 2026205 ms
Jun 20, 2026208 ms
Jun 27, 2026203 ms
Jul 4, 2026195 ms
Jul 11, 2026180 ms
Jul 18, 2026178 ms
Jul 25, 2026185 ms
Aug 1, 2026183 ms
Aug 8, 2026183 ms
Aug 15, 2026178 ms
Aug 22, 2026171 ms
Aug 29, 2026165 ms
Sep 5, 2026163 ms
Sep 12, 2026164 ms
Sep 19, 2026165 ms
Sep 26, 2026162 ms
Oct 3, 2026158 ms
Oct 10, 2026151 ms
Oct 17, 2026150 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 beautyhaul.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beautyhaul.com at 0.6 s0.6 s
  2. beautyhaul.com at 1.2 s1.2 s
  3. beautyhaul.com at 1.7 s1.7 s
  4. beautyhaul.com at 2.3 s2.3 s
  5. beautyhaul.com at 2.9 s2.9 s
  6. beautyhaul.com at 3.5 s3.5 s
  7. beautyhaul.com at 4.1 s4.1 s
  8. beautyhaul.com at 4.6 s4.6 s

Speed

8 to fix65
  • Improve image delivery

    600 ms · 911 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

  • Document request latency

    550 ms

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    549 ms

    Reduce initial server response time. Google estimates savings of 549 ms on a phone.

  • Reduce unused JavaScript

    519 KiB

    About 519 KiB of JavaScript is downloaded but never used on this page.

  • JSDelivr CDN adds 435 ms

    435 ms

    JSDelivr CDN costs a phone 435 ms of main-thread work and 44 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.

  • 2,952 HTML elements

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

  • Server response: 649 ms

    649 ms

    Your server takes 649 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 2 third-party services on the page

    2 third-party services load with your homepage (JSDelivr CDN and Google Fonts), adding 71 KiB and 435 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    20 KiB

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Use efficient cache lifetimes

    2 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).

1 checks passed
  • Main-thread work: 1.4 s

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

Core Web Vitals

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

  • Largest Contentful Paint: 6.0 s

    6.0 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 309 ms

    309 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Time to Interactive: 6.0 s

    6.0 s

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

  • 1 image without width and height

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

5 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 34% faster for real visitors

    -34%

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

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

    -28%

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

  • Total Blocking Time: 112 ms

    112 ms

    Scripts block the page for only 112 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix58
  • 4 images far larger than shown

    498 KiB

    4 images are downloaded at several times the size a phone draws them, for example Main_Banner_Payday_Promo_LEIVY_ALG.__2880.webp at 2,880 px wide, shown at 374 px. Resized copies would save about 498 KiB.

  • Page weight: 2.3 MB in 122 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 122 requests on a phone: images 2.0 MB (114), HTML 177 KiB (1) and scripts 44 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Main_Banner_Payday_Promo_LEIVY_ALG.__2880.webp 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 0.6 g of CO₂ per visit

    0.65 g

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

7 to fixGoogle 8589
  • 89 text elements with low contrast

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

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

  • 57 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 3 form fields without a label

    3 form fields have 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 (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 124 internal links, 9 external

    The homepage links to 124 pages on beautyhaul.com and 9 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Belanja beauties lebih hemat di Beautyhaul! 100% original & BPOM! Temukan solusi masalah kulitmu up to 50% OFF dari bra…”.

  • One H1 headline

    Your main headline reads: “BeautyHaul - Situs Jual Beli Skin Care, Make Up, Kosmetik Online”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Beautyhaul: Jual makeup, skincare, parfum #1 di Indonesia”.

  • Canonical URL set

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

  • 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.beautyhaul.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    27%

    A phone browser shows 1,127 words, but the HTML your server sends has only 300. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://www.beautyhaul.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
  • 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.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://www.beautyhaul.com/product/filter/col=0 and https://www.beautyhaul.com/product/filter/col=213 use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.beautyhaul.com/product/filter/col=0, https://www.beautyhaul.com/product/filter/col=sale, https://www.beautyhaul.com/blog, https://www.beautyhaul.com/product/filter/col=213, https://www.beautyhaul.com/product/detail/physical-sunscreen-spf-50-pa and https://www.beautyhaul.com/product/detail/miraculous-refining-toner-100ml and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://www.beautyhaul.com/product/filter/col=0, https://www.beautyhaul.com/product/filter/col=sale, https://www.beautyhaul.com/product/filter/col=213, https://www.beautyhaul.com/product/detail/physical-sunscreen-spf-50-pa, https://www.beautyhaul.com/product/detail/miraculous-refining-toner-100ml and https://www.beautyhaul.com/product/detail/cashmere-supreme-foundation and 7 others have 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.

  • 2 pages slow to respond

    https://www.beautyhaul.com/product/detail/stellar-dust-lip-stain and https://www.beautyhaul.com/product/detail/leo-blow-dryer took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 10093
  • 46 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,127 words of copy

    The homepage carries about 1,127 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “How to Order” and “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Subscribe Loading...”, “Contact Us” and “Join Our Team”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 18 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 beautyhaul.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on beautyhaul.com, including 18 speed issues and 1 SEO issue. 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