Website review, no card needed
siennanaturals.com website review
Visit site (opens in a new tab)Reviewed 8 November 202640 issues · 89 checks
This review found 40 issues worth fixing on siennanaturals.com, 13 of them high impact, across 89 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,695 of 126,442 reviewed websitesbeats 72%
- #18,578 of 70,471 online storesbeats 67%
- #17,979 of 63,972 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 148 ms |
| Aug 8, 2026 | 153 ms |
| Aug 15, 2026 | 155 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 148 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.2 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.3 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,294 HTML elements
The page has 3,294 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 1.4 MB22 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, route.com and Yotpo and others), adding 2.0 MB and 1.2 s of main-thread time.
Use efficient cache lifetimes
200 ms · 1.0 MB22 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 382 ms
382 msGoogle Tag Manager costs a phone 382 ms of main-thread work and 496 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.
route.com adds 196 ms
196 msroute.com costs a phone 196 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.
Yotpo adds 159 ms
159 msYotpo costs a phone 159 ms of main-thread work and 338 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 231 ms. During a long task the page ignores taps.
Reduce unused CSS
69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Minify JavaScript
31 KiB31 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.7 s
28.7 sThe page becomes fully interactive after 28.7 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 324 ms
324 msScripts block taps and scrolling for 324 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 154 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: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 613 ms
613 msReal visitors wait 613 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 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: 5.8 MB in 401 requests
5.8 MBYour homepage downloads 5.8 MB in 401 requests on a phone: scripts 2.5 MB (108), images 2.1 MB (59) and other files 897 KiB (198). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.4 MB5 images are downloaded at several times the size a phone draws them, for example Issa_0f6dad17-f93b-48e7-8985-252157ce09e8.png at 1,500 px wide, shown at 350 px. Resized copies would save about 1.4 MB.
13 images in older formats
13 images (1.6 MB) 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.
4 images below the first screen load straight away
4 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.65 g of CO₂e: 198.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
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.
9 links without text
9 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 should not be empty (1 element)
Headings should not be empty: 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.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (215 characters)
Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
148 internal links, 6 external
The homepage links to 148 pages on siennanaturals.com and 6 external pages.
5 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Sienna Naturals | Clean Textured Hair & Scalp Care”.
Canonical URL set
The canonical URL is https://www.siennanaturals.com/.
Structured data in place
Structured data found: BreadcrumbList.
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://www.siennanaturals.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 (1,292 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.siennanaturals.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://www.siennanaturals.com/pages/quiz-ai, https://www.siennanaturals.com/collections/dryness, https://www.siennanaturals.com/collections/hair-loss, https://www.siennanaturals.com/collections/definition, https://www.siennanaturals.com/collections/damage and https://www.siennanaturals.com/collections/accessories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.siennanaturals.com/pages/quiz-ai has 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 48 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.
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
19 small tap targets
19 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 “Invalid or unexpected token”.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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.
About 780 words of copy
The homepage carries about 780 words of visible text.
5 checks passed
20 calls to action
The homepage has 20 calls to action, for example “Shop”, “Shop By Need” and “Shop Best Sellers >”.
24 short forms
24 short forms (4 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks and 8 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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.
38 cookies set on arrival
38Opening the homepage sets 38 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.
62 other companies contacted
Loading the homepage contacts 62 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 siennanaturals.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Consentmo Gdpr · Yotpo Loyalty Rewards · T Lab Ai Translate · Uppromote Affiliate · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Region Restrictions · Content Translation · Affliate By Secomapp · Gdpr Backpack · amazonaws.com · rechargecdn.com · b-cdn.net · zegsu.com · nfcube.com · electricsms.com · route.com · rakutenadvertising.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on siennanaturals.com, including 16 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.