Website review, no card needed
brickellmensproducts.com website review
Visit site (opens in a new tab)Reviewed 5 November 202641 issues · 93 checks
This review found 41 issues worth fixing on brickellmensproducts.com, 13 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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
79C- #56,307 of 126,442 reviewed websitesbeats 50%
- #36,709 of 70,471 online storesbeats 42%
- #35,141 of 63,972 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 138 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 145 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
1.3 s
2.7 s
4.0 s
5.3 s
6.6 s
8.0 s
9.3 s
10.6 s
Speed
Render-blocking requests
1.9 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Main-thread work: 11.7 s
A phone's processor spends 11.7 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Sentry, Hotjar and Shopify and others), adding 1.9 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 827 KiB60 files are served with short cache lifetimes, so returning visitors download them again (827 KiB).
Sentry adds 857 ms
857 msSentry costs a phone 857 ms of main-thread work and 91 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
555 KiB22 images could be 555 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Hotjar adds 525 ms
525 msHotjar costs a phone 525 ms of main-thread work and 261 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 299 ms
299 msShopify costs a phone 299 ms of main-thread work and 646 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 on the main thread
20 long tasks block the main thread while loading, the longest for 340 ms. During a long task the page ignores taps.
Klaviyo adds 188 ms
188 msKlaviyo costs a phone 188 ms of main-thread work and 327 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.
2,153 HTML elements
The page has 2,153 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Attentive adds 111 ms
111 msAttentive costs a phone 111 ms of main-thread work and 466 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
200 ms · 82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 95 KiBAbout 95 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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.
Speed Index: 16.4 s
16.4 sVisually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 31.6 s
31.6 sThe page becomes fully interactive after 31.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 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.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 138 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 585 ms
585 msReal visitors wait 585 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 523 requests
6.0 MBYour homepage downloads 6.0 MB in 523 requests on a phone: scripts 2.8 MB (185), images 1.4 MB (84) and other files 1.1 MB (181). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Banner_Holiday-Shop_Home_Desktop_Mobile.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images in older formats
4 images (146 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.
8 images below the first screen load straight away
8 images further down the page (197 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 203.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “The Best Men’s Skin Care & Best Mens Grooming Products – Brickell Men’s Products®”.
200 internal links, 26 external
The homepage links to 200 pages on brickellmensproducts.com and 26 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Luxury men's skin care & mens grooming products with natural ingredients - face wash for men, face moisturizer for men,…”.
One H1 headline
Your main headline reads: “Brickell Men's Skin Care”.
Canonical URL set
The canonical URL is https://brickellmensproducts.com/.
Structured data in place
Structured data found: Brand, 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://brickellmensproducts.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,508 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://brickellmensproducts.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 linked pages hidden from search
https://brickellmensproducts.com/collections/best-natural-hair-care-for-men/cat_shampoo, https://brickellmensproducts.com/collections/best-natural-mens-body-care/cat_cleansers, https://brickellmensproducts.com/collections/shop-all/cat_sun_protection, https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_cleansers, https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_moisturizers and https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_treatments and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://brickellmensproducts.com/collections/shop-all/cat_sun_protection and https://brickellmensproducts.com/collections/shop-all have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://brickellmensproducts.com/collections/anti-aging-products-for-men, https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_cleansers, https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_moisturizers, https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_treatments and https://brickellmensproducts.com/collections/anti-aging-products-for-men/cat_routines use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 88 found) and read each the way a search engine does.
5 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 an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 broken images
8 images failed to load on a phone, for example https://d.adroll.com/cm/experian/out?af0=0fe6f973&adroll_fpc=ca160d6b36c8d300f80da0be270fa529-1793912842021&pv=70382476812.31105&arrfrr=https%3A%2F%2Fbrickellmensproducts.com%2F&ats1=shopify&advertisa.
9 small tap targets
9 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “value.startsWith is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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.
About 699 words of copy
The homepage carries about 699 words of visible text.
5 checks passed
18 calls to action
The homepage has 18 calls to action, for example “Shop >”, “Shop All” and “Shop By Concern”.
15 short forms
15 short forms (5 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 48 testimonial or review blocks, 2 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Meta Pixel.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
45 cookies set on arrival
45Opening the homepage sets 45 cookies (measured from a US location before any click).
82 other companies contacted
Loading the homepage contacts 82 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) 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 brickellmensproducts.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 26 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Ketch Consent Management · Loyalty Rewards And Referrals · Triplewhale · Klaviyo Email Marketing Sms · Userway Website Accessibility · Checkmate · Gorgias Live Chat Helpdesk · Persistent Cart · Cart Persistify · Applovin Shop Integration · Pushowl · Discount In Cart · ywxi.net · adroll.com · snapchat.com · shareasale.com · rechargecdn.com · trafficmanager.net · cloudfront.net · avada.io · stamped.io · bogos.io · b-cdn.net · attn.tv · 9gtb.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
- Hosting
- Shopify
Company
- Headquarters
- Portland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on brickellmensproducts.com, including 23 speed issues, 1 SEO issue and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.