Website review, no card needed

frendsbeauty.com logo

frendsbeauty.com website review

Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 88 checks

This review found 29 issues worth fixing on frendsbeauty.com, 14 of them high impact, across 88 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.0 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
130 ms110 msMay 16Oct 31113 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026117 ms
May 23, 2026117 ms
May 30, 2026116 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026121 ms
Aug 8, 2026121 ms
Aug 15, 2026121 ms
Aug 22, 2026125 ms
Aug 29, 2026128 ms
Sep 5, 2026125 ms
Sep 12, 2026121 ms
Sep 19, 2026120 ms
Sep 26, 2026115 ms
Oct 3, 2026113 ms
Oct 10, 2026112 ms
Oct 17, 2026112 ms
Oct 24, 2026112 ms
Oct 31, 2026113 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 frendsbeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frendsbeauty.com at 0.4 s0.4 s
  2. frendsbeauty.com at 0.9 s0.9 s
  3. frendsbeauty.com at 1.3 s1.3 s
  4. frendsbeauty.com at 1.7 s1.7 s
  5. frendsbeauty.com at 2.1 s2.1 s
  6. frendsbeauty.com at 2.6 s2.6 s
  7. frendsbeauty.com at 3.0 s3.0 s
  8. frendsbeauty.com at 3.4 s3.4 s

Speed

10 to fix24
  • Reduce unused JavaScript

    2.3 s · 432 KiB

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

  • Mobile performance score: 24

    24/100

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

  • Main-thread work: 5.7 s

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

  • 3,491 HTML elements

    The page has 3,491 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 (Google Tag Manager, POWr and Clarity and others), adding 1.0 MB and 1.0 s of main-thread time.

  • 7 long tasks on the main thread

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

  • Render-blocking requests

    650 ms

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

  • Reduce unused CSS

    450 ms · 83 KiB

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

  • Google Tag Manager adds 354 ms

    354 ms

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

  • POWr adds 311 ms

    311 ms

    POWr costs a phone 311 ms of main-thread work and 13 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

    150 ms · 68 KiB

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    19 KiB

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

  • Improve image delivery

    12 KiB

    1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 12 ms

    12 ms

    Your server sent the HTML in 12 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.

  • Real-user CLS: 0.65

    0.65

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

  • Largest Contentful Paint: 11.4 s

    11.4 s

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

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Cumulative Layout Shift: 0.521

    0.521

    The layout shifts by 0.521 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 840 ms

    840 ms

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

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

    2.6 s

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

  • 14 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 380 ms

    380 ms

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

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

    -19%

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

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 329 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 329 requests on a phone: other files 2.0 MB (150), scripts 1.2 MB (71) and images 294 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.07 g

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

5 to fixGoogle 8692
  • 7 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

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

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

  • 1 link without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

2 checks passed
  • Every image has alt text

    All 49 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10093
  • Title is long (206 characters)

    Your title is 206 characters, so Google will cut it off around 60: “Beauty Supply Store For Makeup Artists | Special FX For the Entertainment Industry | Save…”.

  • 425 internal links, 18 external

    The homepage links to 425 pages on frendsbeauty.com and 18 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “We’ve been the go-to beauty supply store for SFX, hair & makeup artist supplies since 1940. Shop prosthetic & theatrica…”.

  • One H1 headline

    Your main headline reads: “Your Pro Beauty Supply Store Since 1940”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, 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://frendsbeauty.com/sitemap.xml.

AI search readiness

100
  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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: 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 (2,261 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://frendsbeauty.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 197 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “missing ) after argument list”.

2 checks passed
  • Tap targets are thumb-sized

    53 of 57 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • A 27-field form

    Your longest form asks for 27 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 849 words of visible text.

  • Urgency cues

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “SHOP PRODUCTS”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Book | Magazine”, “Shop Supplies” and “Shop Products”.

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 6 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (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.

  • 6 cookies set on arrival

    6

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

  • 27 other companies contacted

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

Apps your storefront loads

Pandectes Gdpr · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Avada Seo Suite · Gdpr Cookie Consent · stamped.io · chimpstatic.com · gorgias.chat · hikeorders.com · powr.io · 9gtb.com · Swym Wishlist Plus

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

  • The footer still says © 2025.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Employees
26
Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on frendsbeauty.com, including 19 speed issues, 1 SEO issue 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