Website review, no card needed
mehron.com website review
Visit site (opens in a new tab)Reviewed 22 November 202643 issues · 84 checks
This review found 43 issues worth fixing on mehron.com, 18 of them high impact, across 84 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
63D- #120,189 of 126,588 reviewed websitesbeats 4%
- #68,952 of 70,522 online storesbeats 2%
- #876 of 925 BigCommerce storesbeats 4%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 125 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 126 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 121 ms |
| Oct 24, 2026 | 120 ms |
| Oct 31, 2026 | 119 ms |
| Nov 7, 2026 | 119 ms |
| Nov 14, 2026 | 120 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
Speed
Reduce unused JavaScript
6.8 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.
Use efficient cache lifetimes
2.8 s · 645 KiB37 files are served with short cache lifetimes, so returning visitors download them again (645 KiB).
Render-blocking requests
1.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 18
18/100Your mobile performance score is 18. 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.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and shgcdn2.com and others), adding 3.8 MB and 2.0 s of main-thread time.
Improve image delivery
754 KiB5 images could be 754 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
YouTube adds 550 ms
550 msYouTube costs a phone 550 ms of main-thread work and 1.1 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.
Reduce unused CSS
420 ms · 176 KiBAbout 176 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 420 ms faster on a phone.
Google Tag Manager adds 452 ms
452 msGoogle Tag Manager costs a phone 452 ms of main-thread work and 662 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.
Bigcommerce adds 163 ms
163 msBigcommerce costs a phone 163 ms of main-thread work and 1.1 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.
Klaviyo adds 169 ms
169 msKlaviyo costs a phone 169 ms of main-thread work and 356 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 · 49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 238 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
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: 20 ms
20 msYour server sent the HTML in 20 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.
Real-user CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 28.2 s
28.2 sYour largest element takes 28.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 34.9 s
34.9 sThe page becomes fully interactive after 34.9 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
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.
Cumulative Layout Shift: 0.406
0.406The layout shifts by 0.406 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 121 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 555 ms
555 msReal visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.6 MB in 273 requests
5.6 MBYour homepage downloads 5.6 MB in 273 requests on a phone: scripts 3.7 MB (122), images 1.1 MB (42) and fonts 234 KiB (7). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
661 KiB4 images are downloaded at several times the size a phone draws them, for example 801-PAL-30C-1__76183.1688649859.1280.1280.jpg at 1,280 px wide, shown at 185 px. Resized copies would save about 661 KiB.
An image on the first screen is lazy-loaded
720x 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 (785 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.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
50 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: 50 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“WELCOME TO PARADISE! ENJOY FREE SHIPPING ON ORDER…”, “WELCOME TO PARADISE! ENJOY FREE SHIPPING ON ORDER…” and “WELCOME TO PARADISE! ENJOY FREE SHIPPING ON ORDER…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.mehron.com/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
150 internal links, 6 external
The homepage links to 150 pages on mehron.com and 6 external pages.
4 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Mehron Makeup is the global leader in professional Stage and Screen, Special FX, Cosplay, Pro Beauty and Halloween make…”.
Title: 57 characters
Your title is a healthy 57 characters: “Best Professional Makeup Brand In The USA | Mehron Makeup”.
Canonical URL set
The canonical URL is https://www.mehron.com/.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.mehron.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (364 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 108 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
3 broken images
3 images failed to load on a phone, for example https://d.adroll.com/cm/experian/out?af0=0fe6f973&adroll_fpc=fa373531e4288e0a08753dfadea57608-1795368636545&pv=11680445683.22094&arrfrr=https%3A%2F%2Fwww.mehron.com%2F&advertisable=XHFDOMUX2FDLPHAWXNN.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
29 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 157 words
The homepage has only about 157 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REGISTER”.
6 calls to action
The homepage has 6 calls to action, for example “Register”, “Shop Mehron Blood” and “Subscribe”.
7 short forms
7 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
53 other companies contacted
Loading the homepage contacts 53 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 mehron.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- BigCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Bigcommerce Inc.
Company
- Headquarters
- Spring Valley
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on mehron.com, including 22 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.