Website review, no card needed
hemp-flower.com website review
Visit site (opens in a new tab)Reviewed 9 November 202653 issues · 92 checks
This review found 53 issues worth fixing on hemp-flower.com, 22 of them high impact, across 92 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
60D- #117,617 of 120,899 reviewed websitesbeats 2%
- #67,794 of 68,441 online storesbeats 1%
- #61,918 of 62,367 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 310 ms |
| May 30, 2026 | 317 ms |
| Jun 6, 2026 | 316 ms |
| Jun 13, 2026 | 313 ms |
| Jun 20, 2026 | 311 ms |
| Jun 27, 2026 | 305 ms |
| Jul 4, 2026 | 314 ms |
| Jul 11, 2026 | 333 ms |
| Jul 18, 2026 | 338 ms |
| Jul 25, 2026 | 345 ms |
| Aug 1, 2026 | 352 ms |
| Aug 8, 2026 | 347 ms |
| Aug 15, 2026 | 349 ms |
| Aug 22, 2026 | 350 ms |
| Aug 29, 2026 | 339 ms |
| Sep 5, 2026 | 341 ms |
| Sep 12, 2026 | 346 ms |
| Sep 19, 2026 | 348 ms |
| Sep 26, 2026 | 347 ms |
| Oct 3, 2026 | 336 ms |
| Oct 10, 2026 | 328 ms |
| Oct 17, 2026 | 327 ms |
| Oct 24, 2026 | 332 ms |
| Oct 31, 2026 | 331 ms |
| Nov 7, 2026 | 327 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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.3 s
9.5 s
Speed
Render-blocking requests
1.6 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,391 HTML elements
The page has 5,391 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and one.store and others), adding 1.1 MB and 644 ms of main-thread time.
Reduce unused JavaScript
150 ms · 474 KiBAbout 474 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.
Improve image delivery
300 ms · 140 KiB6 images could be 140 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 287 ms
287 msShopify costs a phone 287 ms of main-thread work and 659 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
50 ms · 244 KiB24 files are served with short cache lifetimes, so returning visitors download them again (244 KiB).
Reduce unused CSS
150 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 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: 22 ms
22 msYour server sent the HTML in 22 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.
Real-user CLS: 0.38
0.38For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black circular containers with white labels displaying ’pre…”.
Cumulative Layout Shift: 0.31
0.31The layout shifts by 0.31 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 318 ms
318 msReal visitors wait 318 ms for the page to respond to a tap (75th percentile). Good is under 200 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: 364 ms
364 msScripts block taps and scrolling for 364 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 310 ms to 327 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 682 ms
682 msReal visitors wait 682 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.2 MB in 445 requests
3.2 MBYour homepage downloads 3.2 MB in 445 requests on a phone: scripts 1.2 MB (180), other files 987 KiB (181) and images 475 KiB (29). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
candy-pave-thca-hemp-flower-greenhouse-smalls-plants-greenho 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).
4 images far larger than shown
436 KiB4 images are downloaded at several times the size a phone draws them, for example wholesale-sale-advertisement-thc-flower-bold-pink-white-text at 1,400 px wide, shown at 180 px. Resized copies would save about 436 KiB.
6 images in older formats
6 images (589 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.
1 image below the first screen load straight away
1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
60 form fields without a label
60 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 69 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 13 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Hemp Flower Co. THCa Hemp Flower Deals: THCa, CBD, D8 - THCA Wholesale”.
Meta description is long (199 characters)
Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
340 internal links, 8 external
The homepage links to 340 pages on hemp-flower.com and 8 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://hemp-flower.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://hemp-flower.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 (3,218 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hemp-flower.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://hemp-flower.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://hemp-flower.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://hemp-flower.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://hemp-flower.com/collections/thca-indoor-flower, https://hemp-flower.com/collections/greenhouse-thca-flower, https://hemp-flower.com/products/candy-pave-thca-hemp-flower-greenhouse-smalls, https://hemp-flower.com/products/blue-sugar-thca-hemp-flower-greenhouse-smalls, https://hemp-flower.com/products/rozay-cake-thca-hemp-flower-greenhouse and https://hemp-flower.com/customer_authentication/redirect and 9 others 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 111 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.
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.
Best practices
8 broken images
8 images failed to load on a phone, for example https://hemp-flower.com/cdn/shop/files/new-releases.png?v=9576.
28 small tap targets
28 of 77 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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 33 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 29-field form
Your longest form asks for 29 fields (0 required). Every extra field lowers completion.
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 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 863 words of copy
The homepage carries about 863 words of visible text.
2 checks passed
15 calls to action
The homepage has 15 calls to action, for example “SHOP THC FLOWER”, “SHOP ALL PRODUCTS” and “SHOP DELTA 8 FLOWER”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
37 other companies contacted
Loading the homepage contacts 37 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 hemp-flower.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Seo King · One Ai Email Sms Marketing · Blockx Country Blocker · Inbox · Powerful Form Builder · Bm Country Blocker Ip Blocker · Boostymark Regionblock · Social Widget · Trustshop · av-northern-apps.com · one.store
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on hemp-flower.com, including 19 speed issues, 4 SEO issues and 4 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.