functionofbeauty.com website review

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

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

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

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Shopify costs a phone 622 ms of main-thread work and 2.8 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 costs a phone 548 ms of main-thread work and 546 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.

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

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

7 images could be 298 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Osano CMP costs a phone 273 ms of main-thread work and 75 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.

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

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

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

7 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

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

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

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

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

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

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

Your homepage downloads 7.7 MB in 399 requests on a phone: scripts 3.0 MB (115), media 2.0 MB (1) and other files 1.2 MB (209). Under 2 MB keeps phones on slow connections fast.

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

1 dropdown has no label.

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“Your cart” and “Function of Beauty”). One clear main headline is easier for people and search engines.

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

The homepage links to 31 pages on functionofbeauty.com and 15 external pages.

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.

/pages/shop-all, /pages/shop-by-hair-type, /pages/code-of-conduct, /blogs/blog and /pages/reviews use the same meta description. A description written for each page earns more clicks.

/pages/hair-quiz, /pages/shop-all, /pages/store-locator, /pages/about, /pages/shop-all-custom-sets-and-routines and /pages/shop-by-hair-type and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/shop-all-custom-sets-and-routines took over 3 s to send its HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “catched”.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://functionofbeauty.faire.com/ (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

functionofbeauty.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

functionofbeauty.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 528 words of visible text.

DMARC is set to p=none, so mail pretending to be functionofbeauty.com is still delivered. Add a report address, check the reports, then move to quarantine.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 ip4:52.35.242.183 include:_spf.google.com”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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