Website review, no card needed
spencerbarnesla.com website review
Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 80 checks
This review found 31 issues worth fixing on spencerbarnesla.com, 8 of them high impact, across 80 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
83B- #28,521 of 125,649 reviewed websitesbeats 72%
- #18,532 of 70,228 online storesbeats 67%
- #17,938 of 63,799 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 150 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 157 ms |
| Jul 25, 2026 | 158 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 174 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 156 ms |
| Oct 31, 2026 | 154 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
2.8 s · 971 KiBAbout 971 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 369 KiB21 files are served with short cache lifetimes, so returning visitors download them again (369 KiB).
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.0 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 (Shopify, rebuyengine.com and Klaviyo and others), adding 1.9 MB and 1.1 s of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused CSS
450 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
rebuyengine.com adds 219 ms
219 msrebuyengine.com costs a phone 219 ms of main-thread work and 695 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 243 ms
243 msShopify costs a phone 243 ms of main-thread work and 458 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.
Klaviyo adds 164 ms
164 msKlaviyo costs a phone 164 ms of main-thread work and 323 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Minify JavaScript
160 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
Legacy JavaScript
100 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
10 KiB2 images 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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EMAIL UNLOCK 10% OFF NOW”.
Time to Interactive: 22.5 s
22.5 sThe page becomes fully interactive after 22.5 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 314 ms
314 msScripts block taps and scrolling for 314 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.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 150 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.8 s
1.8 sReal visitors wait 1.8 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: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 774 ms
774 msReal visitors wait 774 ms for your server to start answering (75th percentile). Good is under 800 ms.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 354 requests
4.1 MBYour homepage downloads 4.1 MB in 354 requests on a phone: scripts 2.2 MB (108), other files 1.0 MB (185) and images 393 KiB (31). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.2 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 39 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
68 internal links, 1 external
The homepage links to 68 pages on spencerbarnesla.com and 1 external page.
7 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Experience SBLA's science-backed face and neck wands with collagen, peptides, and retinol for visible anti-aging result…”.
One H1 headline
Your main headline reads: “SBLA BEAUTY”.
Title: 65 characters
Your title is a healthy 65 characters: “Science-Led Skincare for Timeless Confidence | SBLA – SBLA BEAUTY”.
Canonical URL set
The canonical URL is https://sbla.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://sbla.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://sbla.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 (269 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 28 found) and read each the way a search engine does.
7 checks passed
Linked pages load
4 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.
Every page has a meta description
All 4 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 51 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 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
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
Only about 187 words
The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
9 calls to action
The homepage has 9 calls to action, for example “SHOP”, “SHOP ALL PRODUCTS” and “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 (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.
61 other companies contacted
Loading the homepage contacts 61 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 spencerbarnesla.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Instant Ai Page Builder · Ground · Gorgias Live Chat Helpdesk · Black Crow Ai That Delivers · Rebuy Personalization Engine · Okendo · Timesact Pre Order · Videowise Video Commerce · Quick Announcement Bar Prod · Loop Returns · Applovin Shop Integration · Freegifts · Appstle Bundles · powr.io · nfcube.com · shareasale.com · hextom.com · rechargecdn.com · rebuyengine.com · cloudfront.net · bogos.io · makeupar.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on spencerbarnesla.com, including 15 speed issues, 1 SEO issue and 5 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.