Website review, no card needed

beautytriangle.com logo

beautytriangle.com website review

Visit site (opens in a new tab)Reviewed 11 November 202637 issues · 83 checks

This review found 37 issues worth fixing on beautytriangle.com, 15 of them high impact, across 83 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.1 s1.8 sMay 23Nov 71.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
200 ms120 msMay 23Nov 7191 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026130 ms
May 30, 2026129 ms
Jun 6, 2026134 ms
Jun 13, 2026137 ms
Jun 20, 2026153 ms
Jun 27, 2026169 ms
Jul 4, 2026168 ms
Jul 11, 2026154 ms
Jul 18, 2026151 ms
Jul 25, 2026143 ms
Aug 1, 2026137 ms
Aug 8, 2026137 ms
Aug 15, 2026136 ms
Aug 22, 2026137 ms
Aug 29, 2026145 ms
Sep 5, 2026146 ms
Sep 12, 2026153 ms
Sep 19, 2026150 ms
Sep 26, 2026145 ms
Oct 17, 2026160 ms
Oct 24, 2026179 ms
Oct 31, 2026186 ms
Nov 7, 2026191 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 beautytriangle.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beautytriangle.com at 1.3 s1.3 s
  2. beautytriangle.com at 2.6 s2.6 s
  3. beautytriangle.com at 3.9 s3.9 s
  4. beautytriangle.com at 5.1 s5.1 s
  5. beautytriangle.com at 6.4 s6.4 s
  6. beautytriangle.com at 7.7 s7.7 s
  7. beautytriangle.com at 9.0 s9.0 s
  8. beautytriangle.com at 10.3 s10.3 s

Speed

13 to fix43
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 10.2 s

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

  • Mobile performance score: 43

    43/100

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

  • 5,783 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google CDN and Google Tag Manager and others), adding 4.6 MB and 2.6 s of main-thread time.

  • Reduce unused JavaScript

    1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page.

  • Shopify adds 750 ms

    750 ms

    Shopify costs a phone 750 ms of main-thread work and 1.3 MB 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.

  • Improve image delivery

    450 ms · 248 KiB

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

  • Google CDN adds 581 ms

    581 ms

    Google CDN costs a phone 581 ms of main-thread work and 1.1 MB 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.

  • Google Tag Manager adds 453 ms

    453 ms

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

    389 KiB

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

  • Klaviyo adds 266 ms

    266 ms

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

  • rebuyengine.com adds 153 ms

    153 ms

    rebuyengine.com costs a phone 153 ms of main-thread work and 705 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.

  • Reduce unused CSS

    150 ms · 121 KiB

    About 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    74 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    6 KiB

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

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 fix100
  • 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: 41.0 s

    41.0 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 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: 7.6 s

    7.6 s

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

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

    +46%

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

  • Real-user TTFB: 813 ms

    813 ms

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 193 ms

    193 ms

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

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

    1.6 s

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

  • 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

    0

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

Images and page weight

2 to fix60
  • Page weight: 8.4 MB in 482 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 482 requests on a phone: scripts 4.5 MB (221), other files 1.9 MB (175) and images 1.2 MB (42). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    11 KiB

    2 images are downloaded at several times the size a phone draws them, for example otto-retail-slide-1-mobile.png at 1,200 px wide, shown at 390 px. Resized copies would save about 11 KiB.

  • 5 images in older formats

    5 images (433 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 2.4 g of CO₂ per visit

    2.39 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.39 g of CO₂e: 287.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

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

Accessibility

8 to fixGoogle 8690
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 11 tap targets too small

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

  • 2 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (10 elements)

    Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 294 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Wholesale Beauty Products, Lycon Wax & Supercilium Distributors UK”.

  • Meta description is long (186 characters)

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

  • 535 internal links, 5 external

    The homepage links to 535 pages on beautytriangle.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Beauty Triangle International”.

  • Canonical URL set

    The canonical URL is https://beautytriangle.com/.

  • 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://beautytriangle.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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 172 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 9687
  • 5 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “searchQuery is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 706 words of copy

    The homepage carries about 706 words of visible text.

5 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Send request”, “Address Book” and “SHOP BY BRAND”.

  • 94 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 33 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

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.

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

  • 51 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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 37 issues on beautytriangle.com, including 21 speed issues, 2 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