Website review, no card needed
questionbeauty.com website review
Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 90 checks
This review found 38 issues worth fixing on questionbeauty.com, 11 of them high impact, across 90 checks. The most urgent: main-thread work: 14.3 s. 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
75C- #79,412 of 120,981 reviewed websitesbeats 30%
- #50,648 of 68,471 online storesbeats 22%
- #47,854 of 62,394 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 746 ms |
| May 23, 2026 | 724 ms |
| May 30, 2026 | 700 ms |
| Jun 6, 2026 | 690 ms |
| Jun 13, 2026 | 707 ms |
| Jun 20, 2026 | 725 ms |
| Jun 27, 2026 | 740 ms |
| Jul 4, 2026 | 742 ms |
| Jul 11, 2026 | 737 ms |
| Jul 18, 2026 | 745 ms |
| Jul 25, 2026 | 745 ms |
| Aug 1, 2026 | 756 ms |
| Aug 8, 2026 | 778 ms |
| Aug 15, 2026 | 823 ms |
| Aug 22, 2026 | 892 ms |
| Aug 29, 2026 | 901 ms |
| Sep 5, 2026 | 897 ms |
| Sep 12, 2026 | 910 ms |
| Sep 19, 2026 | 896 ms |
| Sep 26, 2026 | 899 ms |
| Oct 3, 2026 | 878 ms |
| Oct 10, 2026 | 815 ms |
| Oct 17, 2026 | 771 ms |
| Oct 24, 2026 | 715 ms |
| Oct 31, 2026 | 672 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 166 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 182 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 190 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 195 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 2026 | 196 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.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.7 s
7.8 s
8.9 s
Speed
Main-thread work: 14.3 s
A phone's processor spends 14.3 s on main-thread work while loading, 6.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,467 HTML elements
The page has 6,467 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, Yotpo and Shopify and others), adding 2.4 MB and 2.9 s of main-thread time.
Google Tag Manager adds 997 ms
997 msGoogle Tag Manager costs a phone 997 ms of main-thread work and 680 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.
Reduce unused JavaScript
1,005 KiBAbout 1,005 KiB of JavaScript is downloaded but never used on this page.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
815 KiB15 images could be 815 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
750 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Yotpo adds 661 ms
661 msYotpo costs a phone 661 ms of main-thread work and 513 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.
Use efficient cache lifetimes
250 ms · 380 KiB22 files are served with short cache lifetimes, so returning visitors download them again (380 KiB).
Shopify adds 397 ms
397 msShopify costs a phone 397 ms of main-thread work and 696 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 410 ms. During a long task the page ignores taps.
TikTok adds 335 ms
335 msTikTok costs a phone 335 ms of main-thread work and 157 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.
Reduce unused CSS
150 ms · 58 KiBAbout 58 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.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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 CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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.
Time to Interactive: 34.4 s
34.4 sThe page becomes fully interactive after 34.4 s. Good is under 3.8 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 304 ms
304 msReal visitors wait 304 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “🔄”.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 166 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 601 ms
601 msReal visitors wait 601 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 397 requests
7.4 MBYour homepage downloads 7.4 MB in 397 requests on a phone: images 3.4 MB (54), scripts 2.5 MB (125) and other files 970 KiB (176). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.09 g of CO₂e: 250.7 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
192 tap targets too small
192 tap targets are too small or too close together to hit reliably with a finger.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (42 elements)
Alternative text of images should not be repeated as text: 42 elements on the page fail this check, rated minor by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“”, “UP TO 40% OFF THIS BLACK FRIDAY!” and “CREATIVITY LOOKS GREAT ON YOU”). One clear main headline is easier for people and search engines.
Meta description is long (313 characters)
Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
610 internal links, 10 external
The homepage links to 610 pages on questionbeauty.com and 10 external pages.
6 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “Question Beauty – questionbeauty”.
Canonical URL set
The canonical URL is https://questionbeauty.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://questionbeauty.com/sitemap.xml.
AI search readiness
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,256 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://questionbeauty.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://questionbeauty.com/collections/frontpage, https://questionbeauty.com/collections/mascara, https://questionbeauty.com/collections/eyeshadow-palette-chapters, https://questionbeauty.com/collections/all-pigments, https://questionbeauty.com/collections/multichrome-eyeliners and https://questionbeauty.com/collections/gems and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://questionbeauty.com/collections/frontpage, https://questionbeauty.com/products/chapter-5-wings-of-fire-and-gold, https://questionbeauty.com/products/new-lipgloss-ultraviolet-bouquet, https://questionbeauty.com/products/lipgloss-true-holo and https://questionbeauty.com/products/rose-holo have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://questionbeauty.com/collections/all-pigments, https://questionbeauty.com/collections/brushes and https://questionbeauty.com/products/chapter-5-wings-of-fire-and-gold took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 137 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://questionbeauty.com/cdn/shop/t/31/assets/https://cdn.shopify.com/s/files/1/0742/6008/7098/files/btn-black-arrow.svg?v=1781178678&v=21179.
114 small tap targets
114 of 268 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.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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 2,061 words of copy
The homepage carries about 2,061 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BEST SELLERS” and “SHOP MASCARA”.
30 calls to action
The homepage has 30 calls to action, for example “Shop”, “SHOP BEST SELLERS” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
33 cookies set on arrival
33Opening the homepage sets 33 cookies, 1 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.
54 other companies contacted
Loading the homepage contacts 54 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 questionbeauty.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Zigpoll Customer Surveys · Videowise Connect · Gempages Builder · Microsoft Clarity · Gorgias Live Chat Helpdesk · Abconvert · Yotpo Subscriptions · Yotpo Loyalty Rewards · Triplewhale · Pagefly Ai Page Builder · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Forms · Free Gift · Gift Box Builder · Navidium Shipping Protection · pop-convert.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Cloudflare
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 questionbeauty.com, including 19 speed issues, 3 SEO issues and 2 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.