Website review, no card needed

fierabeauty.com logo

fierabeauty.com website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 80 checks

This review found 31 issues worth fixing on fierabeauty.com, 10 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of fierabeauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fierabeauty.com at 0.4 s0.4 s
  2. fierabeauty.com at 0.8 s0.8 s
  3. fierabeauty.com at 1.1 s1.1 s
  4. fierabeauty.com at 1.5 s1.5 s
  5. fierabeauty.com at 1.9 s1.9 s
  6. fierabeauty.com at 2.3 s2.3 s
  7. fierabeauty.com at 2.7 s2.7 s
  8. fierabeauty.com at 3.0 s3.0 s

Speed

11 to fix51
  • Use efficient cache lifetimes

    6.0 s · 1.1 MB

    28 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Reduce unused JavaScript

    4.8 s · 1.5 MB

    About 1.5 MB 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.

  • 5,006 HTML elements

    The page has 5,006 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, Shopify and shippedsuite.com and others), adding 2.2 MB and 998 ms of main-thread time.

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 3.9 s

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

  • Legacy JavaScript

    300 ms · 46 KiB

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

  • Google Tag Manager adds 285 ms

    285 ms

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

  • Shopify adds 224 ms

    224 ms

    Shopify costs a phone 224 ms of main-thread work and 473 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.

  • shippedsuite.com adds 154 ms

    154 ms

    shippedsuite.com costs a phone 154 ms of main-thread work and 357 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.

  • poweredbyhue.app adds 105 ms

    105 ms

    poweredbyhue.app costs a phone 105 ms of main-thread work and 536 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.

  • Duplicated JavaScript

    200 ms · 24 KiB

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

  • Reduce unused CSS

    150 ms · 24 KiB

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

  • Render-blocking requests

    150 ms

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

  • 12 long tasks on the main thread

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

  • Improve image delivery

    54 KiB

    5 images could be 54 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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 16 ms

    16 ms

    Your server sent the HTML in 16 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix56
  • Largest Contentful Paint: 22.2 s

    22.2 s

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

  • Time to Interactive: 23.4 s

    23.4 s

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

  • Speed Index: 9.0 s

    9.0 s

    Visually, the page fills in at 9.0 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.

  • Total Blocking Time: 392 ms

    392 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 5.0 MB in 424 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 424 requests on a phone: scripts 2.3 MB (101), other files 1.5 MB (220) and images 563 KiB (53). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.41 g

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

1 to fixGoogle 10099
  • All page content should be contained by landmarks (22 elements)

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

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

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

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • Canonical points to another host

    Your canonical URL points to fieracosmetics.com, not fierabeauty.com, so Google may credit that host instead.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 92 internal links, 23 external

    The homepage links to 92 pages on fierabeauty.com and 23 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Discover Fiera's skincare & cosmetics tailored for mature skin, enhancing natural beauty & rejuvenating your complexion…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Skincare & Cosmetics for Mature Skin | Fièra Cosmetics”.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://fierabeauty.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: 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,063 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://fierabeauty.com/pages/skin-quiz is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://fierabeauty.com/pages/skin-quiz has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://fierabeauty.com/products/deck-the-glows-bundle, https://fierabeauty.com/collections/our-best-sellers, https://fierabeauty.com/pages/reviews, https://fierabeauty.com/pages/tracking-page, https://fierabeauty.com/pages/refer-a-friend and https://fierabeauty.com/pages/rewards and 7 others 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 43 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5076
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=149013614&tm=gtm002&Ver=2&mid=0e82e110-995d-4c7c-a1f8-09f07b1f089a&bo=1&sid=96cf3d70de2a11f1a3c46345d574d3e8&vid=96cf5e70de2a11f1a24633b1e5846452&vids=1&msclkid=N&pi=9.

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    25 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 623 words of visible text.

5 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Track my Order”, “Contact” and “Shop all”.

  • 8 short forms

    8 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 30 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: PostHog.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 11 trackers load before any consent

    11

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

  • 40 cookies set on arrival

    40

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

  • 63 other companies contacted

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

Apps your storefront loads

Geo Pro Geolocation · Consentmo Gdpr · Klickly Connector · Elevar Conversion Tracking · Impact Com · Okendo · Triplewhale · Postscript Sms Marketing · Klaviyo Email Marketing Sms · Easylocation · Product Ads By Criteo · Pushowl · Gdpr Backpack · Test Sms · Upcart · sharethis.com · web.app

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
Analytics
PostHog
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on fierabeauty.com, including 16 speed issues, 3 SEO issues and 3 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