Website review, no card needed
bareminerals.com website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 90 checks
This review found 38 issues worth fixing on bareminerals.com, 18 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #39,685 of 117,615 reviewed websitesbeats 61%
- #26,539 of 66,923 online storesbeats 54%
- #25,602 of 61,018 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 212 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 204 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 207 ms |
| Jun 27, 2026 | 209 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 205 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 202 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 204 ms |
| Aug 29, 2026 | 201 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 2026 | 195 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
How it loaded on a phone
2.5 s
5.1 s
7.6 s
10.1 s
12.7 s
15.2 s
17.8 s
20.3 s
Speed
Reduce unused JavaScript
7.1 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.
Use efficient cache lifetimes
7.1 s · 1.5 MB60 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Main-thread work: 23.8 s
A phone's processor spends 23.8 s on main-thread work while loading, 13.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
2.3 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
gotolstoy.com adds 1.1 s
1.1 sgotolstoy.com costs a phone 1.1 s of main-thread work and 808 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,531 HTML elements
The page has 4,531 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 (gotolstoy.com, onelink-edge.com and Klaviyo and others), adding 43.6 MB and 3.8 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
onelink-edge.com adds 922 ms
922 msonelink-edge.com costs a phone 922 ms of main-thread work and 74 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.
Minify JavaScript
450 ms · 87 KiB87 KiB could be saved by minifying JavaScript.
Klaviyo adds 407 ms
407 msKlaviyo costs a phone 407 ms of main-thread work and 390 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.
Yotpo adds 374 ms
374 msYotpo costs a phone 374 ms of main-thread work and 289 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.
Improve image delivery
371 KiB14 images could be 371 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
customerfields.com adds 305 ms
305 mscustomerfields.com costs a phone 305 ms of main-thread work and 233 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.
Legacy JavaScript
250 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
225 KiBAbout 225 KiB of CSS is downloaded but never applied on this page.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 35.6 s
35.6 sYour largest element takes 35.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies and similar technologies (“Cookie…”. Most of its time is element render delay (14.3 s).
Speed Index: 23.5 s
23.5 sVisually, the page fills in at 23.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 7.8 s
7.8 sScripts block taps and scrolling for 7.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 51.0 s
51.0 sThe page becomes fully interactive after 51.0 s. Good is under 3.8 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 212 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user TTFB: 617 ms
617 msReal visitors wait 617 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 50.0 MB in 633 requests
50.0 MBYour homepage downloads 50.0 MB in 633 requests on a phone: media 41.3 MB (7), scripts 4.7 MB (231) and images 1.7 MB (46). Under 2 MB keeps phones on slow connections fast.
About 14.2 g of CO₂ per visit
14.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.16 g of CO₂e: 1699.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
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
51 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: 51 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
164 internal links, 12 external
The homepage links to 164 pages on bareminerals.com and 12 external pages.
8 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Shop bareMinerals clean beauty collection. Award winning mineral makeup and skincare products you trust. Free samples w…”.
One H1 headline
Your main headline reads: “Bare Minerals”.
Title: 62 characters
Your title is a healthy 62 characters: “bareMinerals | Mineral Makeup & Clean Skincare for Better Skin”.
Canonical URL set
The canonical URL is https://www.bareminerals.com/.
Structured data in place
Structured data found: 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://www.bareminerals.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,914 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bareminerals.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.bareminerals.com/collections/new-arrivals-9975a1 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://www.bareminerals.com/pages/give-the-gift-of-glow-quiz has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.bareminerals.com/pages/accessibility, https://www.bareminerals.com/collections/best-sellers, https://www.bareminerals.com/products/original-mineral-veil-daily-dose-loose-setting-powder, https://www.bareminerals.com/products/complexion-rescue-eye-brightener-mineral-spf-30, https://www.bareminerals.com/products/gen-nude-liquid-mineral-eyeshadow and https://www.bareminerals.com/collections/new-arrivals-9975a1 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.bareminerals.com/products/original-mineral-veil-daily-dose-loose-setting-powder has 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.
8 pages slow to respond
https://www.bareminerals.com/collections/best-sellers, https://www.bareminerals.com/products/original-mineral-veil-daily-dose-loose-setting-powder, https://www.bareminerals.com/collections/new-arrivals-9975a1, https://www.bareminerals.com/collections/foundation, https://www.bareminerals.com/collections/setting-powder-spray and https://www.bareminerals.com/collections/cheek and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 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
20 small tap targets
20 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “condition rejected ()=>E(()=>qi().analyticsProcessingAllowed)”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 561 words of copy
The homepage carries about 561 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP HOLIDAY”.
24 calls to action
The homepage has 24 calls to action, for example “Shop”, “Shop All New Arrivals” and “Shop All Complexion”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies (measured from a US location before any click).
69 other companies contacted
Loading the homepage contacts 69 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 bareminerals.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Onetrust Consent Management · Awin Affiliate Marketing · Tolstoy · Hreflang Manager · Yotpo Loyalty Rewards · Wyllo Formerly Nofraud · Helium Customer Fields · Okendo · Klaviyo Email Marketing Sms · Nosto · Orbe Geolocation · Swish Wishlist King · provenpixel.com · gethumankind.com · bareminerals.com · dyn-rev.app · global-e.com · botnot.io · cloudfront.net · rebuyengine.com
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
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bareminerals.com, including 22 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.