Website review, no card needed
502hemp.com website review
Visit site (opens in a new tab)Reviewed 3 November 202636 issues · 82 checks
This review found 36 issues worth fixing on 502hemp.com, 12 of them high impact, across 82 checks. The most urgent: page weight: 15.0 MB in 172 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
76C- #70,691 of 115,210 reviewed websitesbeats 34%
- #46,180 of 66,425 online storesbeats 26%
- #1,119 of 2,628 WooCommerce storesbeats 52%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 15, 2026 | 4.9 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 5.2 s |
| Oct 10, 2026 | 5.5 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 6.2 s |
| Oct 31, 2026 | 6.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 83 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 78 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 78 ms |
| Aug 15, 2026 | 82 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 84 ms |
| Sep 26, 2026 | 82 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 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
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
3.2 MB5 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and marsello.app and others), adding 2.1 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 525 ms
525 msGoogle Tag Manager costs a phone 525 ms of main-thread work and 504 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.
Render-blocking requests
400 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
marsello.app adds 163 ms
163 msmarsello.app costs a phone 163 ms of main-thread work and 707 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,093 HTML elements
The page has 2,093 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
tidio.co adds 114 ms
114 mstidio.co costs a phone 114 ms of main-thread work and 515 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
Reduce unused CSS
170 KiBAbout 170 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
76 KiB6 files are served with short cache lifetimes, so returning visitors download them again (76 KiB).
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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 LCP: 6.4 s
6.4 sReal visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.7 s
5.7 sReal visitors see the first content after 5.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.5 s
5.5 sReal visitors wait 5.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 18.3 s
18.3 sVisually, the page fills in at 18.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 47.0 s
47.0 sThe page becomes fully interactive after 47.0 s. Good is under 3.8 s.
Total Blocking Time: 862 ms
862 msScripts block taps and scrolling for 862 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 6.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 83 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.089
0.089The layout barely moves while loading (CLS 0.089, good is under 0.1).
Largest Contentful Paint: 2.2 s
2.2 sYour largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Stand with us and the Kentucky Hemp Association and stop th…”.
Images and page weight
Page weight: 15.0 MB in 172 requests
15.0 MBYour homepage downloads 15.0 MB in 172 requests on a phone: images 11.8 MB (39), scripts 2.3 MB (98) and fonts 517 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 4.3 g of CO₂ per visit
4.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.25 g of CO₂e: 510.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
9 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 12 WCAG 2.2 A/AA and best-practice rules on the phone render: 9 passed and 3 failed. 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.
Title is short (15 characters)
Your title is only 15 characters: “Home - 502 Hemp”. Between 30 and 65 characters leaves room to say what you do and for whom.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
96 internal links, 14 external
The homepage links to 96 pages on 502hemp.com and 14 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Stand with us and the Kentucky Hemp Association and stop the imminent ban on all hemp products! Send an email or call y…”.
Canonical URL set
The canonical URL is https://502hemp.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://502hemp.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://502hemp.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.
2 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.
Other pages
10 pages without an H1
https://502hemp.com/faq, https://502hemp.com/cbd-101, https://502hemp.com/certificate-of-analysis, https://502hemp.com/meet-the-educators, https://502hemp.com/about-the-owner and https://502hemp.com/our-brands and 4 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 31 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
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.
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: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 33 words
The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Shop”, “Contact Us” and “Sign Up now”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
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
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 502hemp.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- WordPress.com
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 502hemp.com, including 20 speed issues, 5 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.