Website review, no card needed
rusticstrength.com website review
Visit site (opens in a new tab)Reviewed 6 November 202637 issues · 82 checks
This review found 37 issues worth fixing on rusticstrength.com, 10 of them high impact, across 82 checks. The most urgent: page weight: 17.3 MB in 444 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
69D- #86,697 of 100,582 reviewed websitesbeats 12%
- #50,913 of 55,437 online storesbeats 7%
- #46,913 of 50,353 Shopify storesbeats 6%
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.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 211 ms |
| May 23, 2026 | 213 ms |
| May 30, 2026 | 217 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 220 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 221 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 226 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 234 ms |
| Aug 22, 2026 | 231 ms |
| Aug 29, 2026 | 237 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 263 ms |
| Sep 19, 2026 | 272 ms |
| Sep 26, 2026 | 278 ms |
| Oct 3, 2026 | 271 ms |
| Oct 10, 2026 | 269 ms |
| Oct 17, 2026 | 270 ms |
| Oct 24, 2026 | 263 ms |
| Oct 31, 2026 | 262 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Main-thread work: 10.2 s
A phone's processor spends 10.2 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,170 HTML elements
The page has 7,170 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
500 ms · 1.1 MB39 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (rebuyengine.com, Shopify and elfsight.com and others), adding 2.3 MB and 799 ms of main-thread time.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
467 KiBAbout 467 KiB of JavaScript is downloaded but never used on this page.
rebuyengine.com adds 300 ms
300 msrebuyengine.com costs a phone 300 ms of main-thread work and 673 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 107 ms
107 msShopify costs a phone 107 ms of main-thread work and 1.3 MB 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 · 53 KiBAbout 53 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
55 KiB11 files are served with short cache lifetimes, so returning visitors download them again (55 KiB).
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
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: 13 ms
13 msYour server sent the HTML in 13 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.
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Poster”.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 278 ms
278 msReal visitors wait 278 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
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 211 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
69 images without width and height
69 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 530 ms
530 msScripts block taps and scrolling for 530 ms in total while the page loads. Good is under 200 ms.
5 checks passed
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: 703 ms
703 msReal visitors wait 703 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.098
0.098The layout barely moves while loading (CLS 0.098, good is under 0.1).
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.
Images and page weight
Page weight: 17.3 MB in 444 requests
17.3 MBYour homepage downloads 17.3 MB in 444 requests on a phone: images 7.3 MB (151), media 7.3 MB (1) and scripts 1.3 MB (114). Under 2 MB keeps phones on slow connections fast.
8 images below the first screen load straight away
8 images further down the page (461 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
128 KiB1 image is downloaded at several times the size a phone draws it, for example HerbalMama.png at 400 px wide, shown at 30 px. Resized copies would save about 128 KiB.
6 images in older formats
6 images (328 KiB) 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.
About 4.9 g of CO₂ per visit
4.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.90 g of CO₂e: 587.4 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.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
26 form fields without a label
26 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
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. 5 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 (269 characters)
Your meta description is 269 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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
376 internal links, 9 external
The homepage links to 376 pages on rusticstrength.com and 9 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Rustic Strength”.
Title: 59 characters
Your title is a healthy 59 characters: “Rustic Strength: Non-Toxic, Refillable Cleaning & Body Care”.
Canonical URL set
The canonical URL is https://rusticstrength.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://rusticstrength.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,599 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://rusticstrength.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://rusticstrength.com/pages/learn, https://rusticstrength.com/blogs/sustainability, https://rusticstrength.com/blogs/toxic-truths, https://rusticstrength.com/blogs/tips-tricks, https://rusticstrength.com/pages/testimonials and https://rusticstrength.com/pages/by-scent-landing have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 found) and read each the way a search engine does.
6 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.
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 14 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'play') LazyVideo.play (https://rusticstrength.com/cdn/shop/t/153/assets/g…”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
104 of 114 tappable elements near the top are at least 24 px.
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 1,298 words of copy
The homepage carries about 1,298 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 now” and “Shop the Winter Scents”.
37 calls to action
The homepage has 37 calls to action, for example “Shop now”, “Buy Local” and “Start Here”.
29 short forms
29 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 94 testimonial or review blocks, 69 customer or partner logos and 11 trust badges.
Analytics in place
Analytics detected: Hotjar.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 6 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.
31 cookies set on arrival
31Opening the homepage sets 31 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.
53 other companies contacted
Loading the homepage contacts 53 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 rusticstrength.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Paywhirl Subscriptions · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Triplewhale · Gorgias Live Chat Helpdesk · Attribution Guru · Hotjar Install · Globo Product Options · Aspire App · govx.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
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 rusticstrength.com, including 19 speed issues, 3 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.