Website review, no card needed
sapuralife.com website review
Visit site (opens in a new tab)Reviewed 1 November 202621 issues · 76 checks
This review found 21 issues worth fixing on sapuralife.com, 6 of them high impact, across 76 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
78C- #55,067 of 108,313 reviewed websitesbeats 44%
- #36,061 of 61,424 online storesbeats 36%
- #798 of 2,493 WooCommerce storesbeats 62%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 422 ms |
| May 16, 2026 | 389 ms |
| May 23, 2026 | 368 ms |
| May 30, 2026 | 343 ms |
| Jun 6, 2026 | 320 ms |
| Jun 13, 2026 | 372 ms |
| Jun 20, 2026 | 389 ms |
| Jun 27, 2026 | 382 ms |
| Jul 4, 2026 | 386 ms |
| Jul 11, 2026 | 386 ms |
| Jul 18, 2026 | 354 ms |
| Jul 25, 2026 | 361 ms |
| Aug 1, 2026 | 354 ms |
| Aug 8, 2026 | 363 ms |
| Aug 15, 2026 | 387 ms |
| Aug 22, 2026 | 379 ms |
| Aug 29, 2026 | 396 ms |
| Sep 5, 2026 | 353 ms |
| Sep 12, 2026 | 345 ms |
| Sep 19, 2026 | 336 ms |
| Sep 26, 2026 | 320 ms |
| Oct 3, 2026 | 349 ms |
| Oct 10, 2026 | 354 ms |
| Oct 17, 2026 | 363 ms |
| Oct 24, 2026 | 330 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
Reduce unused JavaScript
2.3 s · 418 KiBAbout 418 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Google Tag Manager adds 347 ms
347 msGoogle Tag Manager costs a phone 347 ms of main-thread work and 667 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.
Use efficient cache lifetimes
300 ms · 56 KiB3 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and surfside.io and others), adding 744 KiB and 429 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.
Improve image delivery
13 KiB1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 467 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 308 ms
308 msReal visitors wait 308 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Real-user TTFB: 982 ms
982 msReal visitors wait 982 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 422 ms to 330 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 74 ms
74 msScripts block the page for only 74 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image far larger than shown
40 KiB1 image is downloaded at several times the size a phone draws it, for example cc26-coldwater-winner.webp at 1,200 px wide, shown at 240 px. Resized copies would save about 40 KiB.
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.5 MB in 64 requests
1.5 MBYour homepage downloads 1.5 MB in 64 requests on a phone: scripts 925 KiB (10), images 431 KiB (29) and fonts 186 KiB (5). That is a lean page.
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.
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.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
44 internal links, 3 external
The homepage links to 44 pages on sapuralife.com and 3 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “We aim to be your go-to cannabis store – a place of color and wonder and connect you to nature through cannabis. Visit …”.
One H1 headline
Your main headline reads: “Cannabis. Down to an Art.”.
Title: 59 characters
Your title is a healthy 59 characters: “Sapura Weed Dispensary | Near You in Lansing & Coldwater MI”.
Canonical URL set
The canonical URL is https://sapuralife.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://sapuralife.com/sitemap_index.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, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (302 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://sapuralife.com/llms.txt (1 KiB, 6 links), a plain-text guide to the site for AI tools.
Other pages
2 pages with very little text
https://sapuralife.com/adult-use and https://sapuralife.com/news have 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.
4 pages slow to respond
https://sapuralife.com/ethos, https://sapuralife.com/partners, https://sapuralife.com/dispensary-locations and https://sapuralife.com/our-artists took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'innerHTML')”.
Missing source maps
Large scripts ship without source maps.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 257 words of copy
The homepage carries about 257 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”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Shop Now” and “Sign Up”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks, 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and The Trade Desk (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
15 other companies contacted
Loading the homepage contacts 15 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 sapuralife.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on sapuralife.com, including 14 speed issues and 3 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.