Website review, no card needed
sacredweaves.com website review
Visit site (opens in a new tab)Reviewed 6 November 202623 issues · 81 checks
This review found 23 issues worth fixing on sacredweaves.com, 3 of them high impact, across 81 checks. The most urgent: 4 tap targets too small. 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
90A- #2,275 of 111,958 reviewed websitesbeats 97%
- #1,130 of 64,112 online storesbeats 97%
- #1,094 of 58,571 Shopify storesbeats 97%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 162 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 167 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 214 ms |
| Aug 8, 2026 | 214 ms |
| Aug 15, 2026 | 221 ms |
| Aug 22, 2026 | 224 ms |
| Aug 29, 2026 | 230 ms |
| Sep 5, 2026 | 238 ms |
| Sep 12, 2026 | 248 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 251 ms |
| Oct 3, 2026 | 253 ms |
| Oct 10, 2026 | 251 ms |
| Oct 17, 2026 | 251 ms |
| Oct 24, 2026 | 248 ms |
| Oct 31, 2026 | 240 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
1.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,661 HTML elements
The page has 1,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
azurefd.net adds 28 ms
28 msazurefd.net costs a phone 28 ms of main-thread work and 322 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.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Shopify and growave.io and others), adding 928 KiB and 426 ms of main-thread time.
Reduce unused JavaScript
223 KiBAbout 223 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
140 ms · 44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
70 KiB6 files are served with short cache lifetimes, so returning visitors download them again (70 KiB).
Improve image delivery
47 KiB4 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 162 ms to 240 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 168 ms
168 msReal visitors wait 168 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: 422 ms
422 msReal visitors wait 422 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 57% faster for real visitors
-57%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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).
Total Blocking Time: 43 ms
43 msScripts block the page for only 43 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.7 MB in 369 requests
3.7 MBYour homepage downloads 3.7 MB in 369 requests on a phone: other files 1.3 MB (242), images 1.2 MB (20) and scripts 1,013 KiB (99). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Real-Jari.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).
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 125.0 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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 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.
19 links without text
19 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 27 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
132 internal links, 16 external
The homepage links to 132 pages on sacredweaves.com and 16 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Shop Silk Mark certified Banarasi sarees online. Pure silk, handwoven in Varanasi using traditional techniques. Perfect…”.
Title: 53 characters
Your title is a healthy 53 characters: “Shop Handwoven Banarasi Sarees Online - Sacred Weaves”.
Canonical URL set
The canonical URL is https://www.sacredweaves.com/.
Structured data in place
Structured data found: ClothingStore, FAQPage and Organization.
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.sacredweaves.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,584 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.sacredweaves.com/llms.txt (17 KiB, 65 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.sacredweaves.com/pages/wishlist has 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 74 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 27 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 “(css || "").replace is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,056 words of copy
The homepage carries about 1,056 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book A Live Video Call” and “AN HEIRLOOM Real Zari SHOP NOW”.
14 calls to action
The homepage has 14 calls to action, for example “Book A Live Video Call”, “Shop” and “Shop by products”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
29 other companies contacted
Loading the homepage contacts 29 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 sacredweaves.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
Bucks · Webrex Ai Seo Schema · Microsoft Clarity · Avada Seo Suite · Simprosys Google Shopping Feed · Powerful Form Builder · Globo Product Options · Whatsapp Abandoned Cart · Nova Multi Currency Converter · Smart Tabs · Genlook · Growave Loyalty Wishlist · Oc Openai Ads Chatgpt Pixel · carthike.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
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Company
- Founded
- 2017
- Headquarters
- Varanasi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on sacredweaves.com, including 9 speed issues, 1 SEO issue 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.