Website review, no card needed
sackclothandashes.com website review
Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 79 checks
This review found 29 issues worth fixing on sackclothandashes.com, 9 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
87B- #7,648 of 109,350 reviewed websitesbeats 90%
- #4,460 of 61,859 online storesbeats 89%
- #4,330 of 56,401 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 996 ms |
| Aug 29, 2026 | 994 ms |
| Sep 5, 2026 | 984 ms |
| Sep 12, 2026 | 996 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 978 ms |
| Oct 10, 2026 | 937 ms |
| Oct 17, 2026 | 936 ms |
| Oct 24, 2026 | 903 ms |
| Oct 31, 2026 | 900 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 99 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 99 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 101 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 81 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 79 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
Improve image delivery
2.0 s · 1.7 MB18 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Reduce unused JavaScript
1.9 s · 469 KiBAbout 469 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 276 KiB16 files are served with short cache lifetimes, so returning visitors download them again (276 KiB).
3,059 HTML elements
The page has 3,059 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 66
66/100Your mobile performance score is 66. 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 (Klaviyo, pop-convert.com and Hubspot and others), adding 1.3 MB and 395 ms of main-thread time.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 900 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 191 ms
191 msKlaviyo costs a phone 191 ms of main-thread work and 449 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 22 ms
22 msShopify costs a phone 22 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.
Reduce unused CSS
110 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Render-blocking requests
100 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
Legacy JavaScript
50 ms · 41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.1 s
16.1 sYour largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Legacy Collection”.
Time to Interactive: 16.1 s
16.1 sThe page becomes fully interactive after 16.1 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
10 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 102 ms
102 msReal visitors wait 102 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 438 ms
438 msReal visitors wait 438 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 99 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.5 MB in 234 requests
14.5 MBYour homepage downloads 14.5 MB in 234 requests on a phone: media 9.7 MB (6), images 2.6 MB (30) and scripts 1.2 MB (96). Under 2 MB keeps phones on slow connections fast.
About 4.1 g of CO₂ per visit
4.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.12 g of CO₂e: 494.6 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 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Sackcloth & Ashes”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Sackcloth & Ashes” and “”). One clear main headline is easier for people and search engines.
59 internal links, 8 external
The homepage links to 59 pages on sackclothandashes.com and 8 external pages.
6 checks passed
Meta description: 81 characters
Your meta description is 81 characters: “For every blanket you purchase, we give a blanket to your local homeless shelter.”.
Canonical URL set
The canonical URL is https://sackclothandashes.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://sackclothandashes.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
36%The HTML your server sends has 2,768 of the 7,780 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
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.
llms.txt published
The site publishes https://sackclothandashes.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://sackclothandashes.com/collections/shop-all, https://sackclothandashes.com/pages/sackcloth-originals, https://sackclothandashes.com/pages/collaborations, https://sackclothandashes.com/collections/sale, https://sackclothandashes.com/pages/about and https://sackclothandashes.com/pages/manufacturing and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://sackclothandashes.com/products/camp-coast and https://sackclothandashes.com/products/camp-desert use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://sackclothandashes.com/collections/shop-all, https://sackclothandashes.com/pages/sackcloth-originals, https://sackclothandashes.com/pages/collaborations, https://sackclothandashes.com/collections, https://sackclothandashes.com/collections/sale and https://sackclothandashes.com/pages/about and 1 other have 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 28 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
14 small tap targets
14 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 7,780 words of copy
The homepage carries about 7,780 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 Collection” and “Shop All”.
11 calls to action
The homepage has 11 calls to action, for example “Shop All”, “Shop” and “Shop Collection”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 91 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo 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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
39 other companies contacted
Loading the homepage contacts 39 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 sackclothandashes.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Forms · pop-convert.com · hubapi.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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Salem
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on sackclothandashes.com, including 14 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.