Website review, no card needed
sakroots.com website review
Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 91 checks
This review found 39 issues worth fixing on sakroots.com, 14 of them high impact, across 91 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
83B- #27,684 of 121,333 reviewed websitesbeats 72%
- #18,217 of 68,649 online storesbeats 67%
- #17,657 of 62,562 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 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.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 338 ms |
| Jun 6, 2026 | 338 ms |
| Jun 13, 2026 | 328 ms |
| Jun 20, 2026 | 321 ms |
| Jun 27, 2026 | 338 ms |
| Jul 4, 2026 | 378 ms |
| Jul 11, 2026 | 430 ms |
| Jul 18, 2026 | 443 ms |
| Jul 25, 2026 | 429 ms |
| Aug 1, 2026 | 397 ms |
| Aug 8, 2026 | 354 ms |
| Aug 15, 2026 | 353 ms |
| Aug 22, 2026 | 370 ms |
| Aug 29, 2026 | 394 ms |
| Sep 5, 2026 | 412 ms |
| Sep 12, 2026 | 419 ms |
| Sep 19, 2026 | 421 ms |
| Sep 26, 2026 | 395 ms |
| Oct 3, 2026 | 354 ms |
| Oct 10, 2026 | 304 ms |
| Oct 17, 2026 | 271 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 212 ms |
| Nov 7, 2026 | 196 ms |
| Nov 14, 2026 | 179 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
Improve image delivery
4.0 s · 1.3 MB27 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 1.1 MB40 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Reduce unused JavaScript
1.1 s · 1.1 MBAbout 1.1 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.
Main-thread work: 16.6 s
A phone's processor spends 16.6 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
getpurpledot.com adds 1.2 s
1.2 sgetpurpledot.com costs a phone 1.2 s of main-thread work and 159 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
8 third-party services on the page
8 third-party services load with your homepage (getpurpledot.com, Shopify and alia-prod.com and others), adding 1.9 MB and 2.8 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 100 KiBAbout 100 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.
Shopify adds 314 ms
314 msShopify costs a phone 314 ms of main-thread work and 657 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.
alia-prod.com adds 306 ms
306 msalia-prod.com costs a phone 306 ms of main-thread work and 259 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 316 ms. During a long task the page ignores taps.
zma.gs adds 287 ms
287 mszma.gs costs a phone 287 ms of main-thread work and 127 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.
2,740 HTML elements
The page has 2,740 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Yotpo adds 226 ms
226 msYotpo costs a phone 226 ms of main-thread work and 332 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.
Minify JavaScript
150 ms · 81 KiB81 KiB could be saved by minifying JavaScript.
Legacy JavaScript
72 KiBPolyfills for old browsers add 72 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).
Duplicated JavaScript
23 KiB23 KiB JavaScript is shipped twice across bundles.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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: 24.4 s
24.4 sYour largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 37.8 s
37.8 sThe page becomes fully interactive after 37.8 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 804 ms
804 msReal visitors wait 804 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 431 ms
431 msScripts block taps and scrolling for 431 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 45% faster for real visitors
-45%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 338 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 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).
Images and page weight
Page weight: 8.8 MB in 522 requests
8.8 MBYour homepage downloads 8.8 MB in 522 requests on a phone: images 3.8 MB (62), scripts 2.5 MB (129) and other files 1.8 MB (304). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
gg-shoes.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
6 images below the first screen load straight away
6 images further down the page (143 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.49 g of CO₂e: 298.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
201 internal links, 19 external
The homepage links to 201 pages on sakroots.com and 19 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Consciously Crafted, Sustainable Crochet Bags, Clogs, Charms & Accessories also available in leather. Up to 20% off whe…”.
Title: 63 characters
Your title is a healthy 63 characters: “Sustainable Crochet Bags, Crochet Clogs & Accessories | The Sak”.
Canonical URL set
The canonical URL is https://www.thesak.com/.
Structured data in place
Structured data found: 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://www.thesak.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (972 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.thesak.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.thesak.com/discount/SAKFRIDAY declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.thesak.com/discount/SAKFRIDAY all use the title “Sustainable Crochet Bags, Crochet Clogs & Accessories | The Sak”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.thesak.com/a/mobile-app has no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://www.thesak.com/discount/SAKFRIDAY, https://www.thesak.com/collections/woven-leather, https://www.thesak.com/collections/sak-black-cherry and https://www.thesak.com/collections/studded-bags use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://www.thesak.com/discount/SAKFRIDAY, https://www.thesak.com/a/mobile-app, https://www.thesak.com/collections/gift-guide, https://www.thesak.com/collections/gift-guide/best-seller, https://www.thesak.com/collections/woven-leather and https://www.thesak.com/collections/fall-edit and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.thesak.com/a/mobile-app 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 87 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
23 small tap targets
23 of 84 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
11 low-resolution images
11 images are served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 480 words of copy
The homepage carries about 480 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”.
25 calls to action
The homepage has 25 calls to action, for example “Holiday Gift Shop”, “Pre-Order Picks” and “Shop By Shape”.
44 short forms
44 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 1 trust badge.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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 sakroots.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Redo · Yotpo Product Reviews · Fuego Mobile App · Fondue Cashback Promotions · Yotpo Loyalty Rewards · Triplewhale · Unveild The Sak · Klaviyo Email Marketing Sms · Swym Wishlist Plus · Gift Box Builder · azureedge.net · govx.com · postscript.io · amazonaws.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on sakroots.com, including 23 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.