Website review, no card needed
camerareadycosmetics.com website review
Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 84 checks
This review found 32 issues worth fixing on camerareadycosmetics.com, 8 of them high impact, across 84 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
88B- #5,962 of 125,435 reviewed websitesbeats 93%
- #3,194 of 70,182 online storesbeats 93%
- #3,094 of 63,766 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 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.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 164 ms |
| May 23, 2026 | 175 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 175 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 243 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 253 ms |
| Aug 15, 2026 | 261 ms |
| Aug 22, 2026 | 252 ms |
| Aug 29, 2026 | 254 ms |
| Sep 5, 2026 | 257 ms |
| Sep 12, 2026 | 247 ms |
| Sep 19, 2026 | 254 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 239 ms |
| Oct 10, 2026 | 240 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 225 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
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Render-blocking requests
1.6 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused CSS
1.2 s · 247 KiBAbout 247 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
6,447 HTML elements
The page has 6,447 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (amaicdn.com, Shopify and minmaxify.com and others), adding 1.0 MB and 683 ms of main-thread time.
Reduce unused JavaScript
150 ms · 460 KiBAbout 460 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 358 KiB14 files are served with short cache lifetimes, so returning visitors download them again (358 KiB).
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
amaicdn.com adds 271 ms
271 msamaicdn.com costs a phone 271 ms of main-thread work and 403 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 253 ms
253 msShopify costs a phone 253 ms of main-thread work and 577 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 273 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 18 KiB18 KiB could be saved by minifying CSS.
Legacy JavaScript
71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need.
Improve image delivery
10 KiB1 image could be 10 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.
1 checks passed
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blend Bunny's latest collab with Ellis Atlantis - Dark Arti…”.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 253 ms
253 msScripts block taps and scrolling for 253 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 572 ms
572 msReal visitors wait 572 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 260 requests
3.6 MBYour homepage downloads 3.6 MB in 260 requests on a phone: other files 1.2 MB (127), scripts 1.1 MB (60) and images 584 KiB (44). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.3 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
24 tap targets too small
24 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
28 links without text
28 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 (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 155 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 3 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.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
664 internal links, 0 external
The homepage links to 664 pages on camerareadycosmetics.com and 0 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Professional makeup supplies for Print, TV, SFX, Halloween, Stage, Cosplay and Film Makeup Artists. Ben Nye, RCMA, Mehr…”.
One H1 headline
Your main headline reads: “Camera Ready Cosmetics”.
Title: 60 characters
Your title is a healthy 60 characters: “Camera Ready Cosmetics | Professional Makeup Supplies Online”.
Canonical URL set
The canonical URL is https://camerareadycosmetics.com/.
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://camerareadycosmetics.com/sitemap.xml.
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.
Some text only appears after JavaScript runs
49%The HTML your server sends has 2,269 of the 4,601 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://camerareadycosmetics.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://camerareadycosmetics.com/pages/a-new-chapter, https://camerareadycosmetics.com/pages/all-brands, https://camerareadycosmetics.com/collections/ben-nye, https://camerareadycosmetics.com/collections/blend-bunny-cosmetics, https://camerareadycosmetics.com/collections/camera-ready-cosmetics and https://camerareadycosmetics.com/collections/danessa-myricks-beauty and 9 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 193 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://camerareadycosmetics.com/.
11 small tap targets
11 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Identifier 'shop' has already been declared”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
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 4,601 words of copy
The homepage carries about 4,601 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: “Learn more”.
11 calls to action
The homepage has 11 calls to action, for example “Learn more”, “Shop All Sales” and “Subscribe & Save”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 105 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (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.
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 camerareadycosmetics.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
Pandectes Gdpr · Seowill Redirects · Judge Me Reviews · Anviara Eu Widerruf · Minmaxify Order Limits · Gdpr Cookie Consent · Self Serve Order Edit · Omnisend · Now In Stock · Freegifts · Utterbond Subscriptions · Iwish · signifyd.com · orderdeadline.com · bogos.io · b-cdn.net · personalizer.io
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Employees
- 10
- Headquarters
- Farmers Branch
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on camerareadycosmetics.com, including 17 speed issues, 2 SEO issues 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.