Website review, no card needed
jessbeauty.com website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 93 checks
This review found 37 issues worth fixing on jessbeauty.com, 12 of them high impact, across 93 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
84B- #22,435 of 125,870 reviewed websitesbeats 77%
- #14,323 of 70,289 online storesbeats 74%
- #13,886 of 63,843 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 136 ms |
| May 30, 2026 | 133 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 133 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 139 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 137 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
1.1 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
2.1 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 62
62/100Your mobile performance score is 62. 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 (route.com, Klaviyo and Google Tag Manager and others), adding 2.0 MB and 705 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 681 KiB35 files are served with short cache lifetimes, so returning visitors download them again (681 KiB).
Improve image delivery
268 KiB2 images could be 268 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
route.com adds 182 ms
182 msroute.com costs a phone 182 ms of main-thread work and 542 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.
1,722 HTML elements
The page has 1,722 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 117 ms
117 msKlaviyo costs a phone 117 ms of main-thread work and 326 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.
Google Tag Manager adds 112 ms
112 msGoogle Tag Manager costs a phone 112 ms of main-thread work and 373 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 217 ms. During a long task the page ignores taps.
Minify JavaScript
56 KiB56 KiB could be saved by minifying JavaScript.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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
4 KiB4 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 27.9 s
27.9 sThe page becomes fully interactive after 27.9 s. Good is under 3.8 s.
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 227 ms
227 msScripts block taps and scrolling for 227 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 136 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 483 ms
483 msReal visitors wait 483 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 411 requests
5.2 MBYour homepage downloads 5.2 MB in 411 requests on a phone: scripts 2.6 MB (128), images 1.2 MB (68) and other files 1,018 KiB (155). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
73 KiB1 image is downloaded at several times the size a phone draws it, for example Steps_sleepingKit.jpg at 1,200 px wide, shown at 90 px. Resized copies would save about 73 KiB.
1 image in older formats
1 image (77 KiB) is 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.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Hidden but focusable
20 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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
29 links without text
29 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 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: 44 passed and 9 failed. 4 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.
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.
100 internal links, 9 external
The homepage links to 100 pages on jessbeauty.com and 9 external pages.
7 checks passed
Meta description: 74 characters
Your meta description is 74 characters: “Welcome to Jess Beauty. Explore our range of skincare and beauty products.”.
One H1 headline
Your main headline reads: “jessbeautyproducts”.
Title: 51 characters
Your title is a healthy 51 characters: “Welcome to Jess Beauty | Skincare & Beauty Products”.
Canonical URL set
The canonical URL is https://jessbeauty.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://jessbeauty.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.
3 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 (718 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://jessbeauty.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://jessbeauty.com/tools/bundle-subscriptions/bundle/8450585460887 and https://jessbeauty.com/tools/bundle-subscriptions all use the title “jessbeautyproducts”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://jessbeauty.com/pages/where-to-find-us, https://jessbeauty.com/collections/all-products, https://jessbeauty.com/tools/bundle-subscriptions/bundle/8450585460887, https://jessbeauty.com/pages/about-us and https://jessbeauty.com/tools/bundle-subscriptions use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://jessbeauty.com/pages/where-to-find-us, https://jessbeauty.com/tools/bundle-subscriptions/bundle/8450585460887, https://jessbeauty.com/blogs/news, https://jessbeauty.com/pages/about-us and https://jessbeauty.com/tools/bundle-subscriptions have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://jessbeauty.com/tools/bundle-subscriptions/bundle/8450585460887 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
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 “Cannot read properties of null (reading 'textContent')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
73 of 80 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.
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 484 words of copy
The homepage carries about 484 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 ALL”.
25 calls to action
The homepage has 25 calls to action, for example “Shop”, “Shop Now” and “SHOP NOW”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
65 other companies contacted
Loading the homepage contacts 65 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 jessbeauty.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
Geo Pro Geolocation · Gorgias Live Chat Helpdesk · Ecomposer Builder · Seolab · Klaviyo Email Marketing Sms · Sami Product Labels · Uppromote Affiliate · Yotpo Product Reviews · Easylocation · Aftersell · Affliate By Secomapp · Ordersify Bis · Mailchimp · Ctx Whatsapp Chat Marketing · Free Gift · peerboard.com · shopiapps.in · appspot.com · route.com · cloudfront.net
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 | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on jessbeauty.com, including 15 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.