Website review, no card needed
livwell.com website review
Visit site (opens in a new tab)Reviewed 29 October 202636 issues · 91 checks
This review found 36 issues worth fixing on livwell.com, 7 of them high impact, across 91 checks. The most urgent: render-blocking 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 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.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 193 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 198 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 207 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 228 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 226 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 219 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 212 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
Render-blocking requests
3.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, iheartjane.com and website-files.com and others), adding 5.9 MB and 626 ms of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 564 KiBAbout 564 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
iheartjane.com adds 178 ms
178 msiheartjane.com costs a phone 178 ms of main-thread work and 3.0 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.
Use efficient cache lifetimes
50 ms · 372 KiB13 files are served with short cache lifetimes, so returning visitors download them again (372 KiB).
Google Tag Manager adds 237 ms
237 msGoogle Tag Manager costs a phone 237 ms of main-thread work and 406 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.
website-files.com adds 111 ms
111 mswebsite-files.com costs a phone 111 ms of main-thread work and 1.5 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,790 HTML elements
The page has 1,790 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Amazon Web Services adds 23 ms
23 msAmazon Web Services costs a phone 23 ms of main-thread work and 901 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
221 KiBAbout 221 KiB of CSS is downloaded but never applied on this page.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 129 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
25 KiB1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
Minify CSS
10 KiB10 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: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Largest Contentful Paint: 7.0 s
7.0 sYour largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 204 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 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 INP: 153 ms
153 msReal visitors wait 153 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: 263 ms
263 msReal visitors wait 263 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.086
0.086The layout barely moves while loading (CLS 0.086, good is under 0.1).
Total Blocking Time: 151 ms
151 msScripts block the page for only 151 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.6 MB in 130 requests
6.6 MBYour homepage downloads 6.6 MB in 130 requests on a phone: images 3.4 MB (54), scripts 1.8 MB (28) and media 823 KiB (2). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
215 KiB5 images are downloaded at several times the size a phone draws them, for example 69baf09d480362e0c197cc43_live weigh.svg at 123 px wide, shown at 24 px. Resized copies would save about 215 KiB.
6 images in older formats
6 images (325 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 1.9 g of CO₂ per visit
1.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.86 g of CO₂e: 223.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 53 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Are you 21 or older?” and “Feel Everything Better”). One clear main headline is easier for people and search engines.
Meta description is long (191 characters)
Your meta description is 191 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.
149 internal links, 3 external
The homepage links to 149 pages on livwell.com and 3 external pages.
5 checks passed
Title: 57 characters
Your title is a healthy 57 characters: “Colorado Dispensaries | LivWell Cannabis — Find Your Feel”.
Canonical URL set
The canonical URL is https://livwell.com/.
Structured data in place
Structured data found: FAQPage and Organization.
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://livwell.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://livwell.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 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 (2,102 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
https://livwell.com/shop/flower, https://livwell.com/shop/pre-roll, https://livwell.com/shop/vape, https://livwell.com/shop/edible, https://livwell.com/shop/extract and https://livwell.com/shop/topical all use the title “Shop Cannabis Undefined Products | LivWell Berthoud Med Dispensary Be…”. 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://livwell.com/shop/deals has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://livwell.com/shop/featured, https://livwell.com/shop/flower, https://livwell.com/shop/pre-roll, https://livwell.com/shop/vape, https://livwell.com/shop/edible and https://livwell.com/shop/extract and 1 other use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 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.
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
2 broken images
2 images failed to load on a phone, for example https://action.dstillery.com/orbserv/nsjs?adv=cl172365597545365&ns=8779&nc=generic&ncv=76.
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”.
2 checks passed
Tap targets are thumb-sized
17 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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,807 words of copy
The homepage carries about 1,807 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “Shop all deals”.
26 calls to action
The homepage has 26 calls to action, for example “Shop Now”, “Shop All Products” and “Browse Shop Now”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Vercel Analytics.
Direct contact links
Visitors can reach you directly: 8 phone links and 0 email links.
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.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
28 other companies contacted
Loading the homepage contacts 28 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 livwell.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
- Webflow
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on livwell.com, including 16 speed issues, 3 SEO issues 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.