Website review, no card needed
realmadhoney.com website review
Visit site (opens in a new tab)Reviewed 20 November 202625 issues · 64 checks
This review found 25 issues worth fixing on realmadhoney.com, 7 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.5 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 4, 2026 | 252 ms |
| Jul 11, 2026 | 272 ms |
| Jul 18, 2026 | 269 ms |
| Jul 25, 2026 | 261 ms |
| Aug 1, 2026 | 261 ms |
| Aug 8, 2026 | 252 ms |
| Aug 15, 2026 | 250 ms |
| Aug 22, 2026 | 252 ms |
| Aug 29, 2026 | 252 ms |
| Sep 5, 2026 | 251 ms |
| Sep 12, 2026 | 247 ms |
| Sep 19, 2026 | 245 ms |
| Sep 26, 2026 | 246 ms |
| Oct 3, 2026 | 252 ms |
| Oct 10, 2026 | 258 ms |
| Oct 17, 2026 | 262 ms |
| Oct 24, 2026 | 270 ms |
| Oct 31, 2026 | 279 ms |
| Nov 7, 2026 | 283 ms |
| Nov 14, 2026 | 282 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 275 ms
275 msReal visitors wait 275 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Largest content (LCP) got 65% slower for real visitors
+65%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 866 ms
866 msReal visitors wait 866 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 252 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.8 MB
5.8 MBYour homepage downloads 5.8 MB on a phone, 2.2 MB of it images (37%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
PDP_Carousel1.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.6 g of CO₂ per visit
1.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.64 g of CO₂e: 197.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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Form elements must have labels (1 element)
Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 10 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Wild Mad HoneyNature’s Rarest Ritual in a Jar”, “Mad Honey” and “Mad Honey”). One clear main headline is easier for people and search engines.
72 internal links, 12 external
The homepage links to 72 pages on realmadhoney.com and 12 external pages.
7 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Find questions about using Mad Honey | Read about the effects of Mad Honey, safety guidelines and Real Mad Honey delive…”.
Title: 46 characters
Your title is a healthy 46 characters: “Buy Strong & Potent Mad Honey | Real Mad Honey”.
Canonical URL set
The canonical URL is https://realmadhoney.com/.
Structured data in place
Structured data found: FAQPage, Organization, ProductGroup and SocialMediaPosting.
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://realmadhoney.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (8,643 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://realmadhoney.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://realmadhoney.com/collections/all, https://realmadhoney.com/pages/reviews, https://realmadhoney.com/pages/what-is-mad-honey, https://realmadhoney.com/pages/why-trust-us, https://realmadhoney.com/pages/source-of-mad-honey and https://realmadhoney.com/pages/full-documentary have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://realmadhoney.com/pages/reviews and https://realmadhoney.com/pages/why-trust-us 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 23 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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.
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 14 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: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
12 of 14 tappable elements near the top are at least 24 px.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 2,509 words of copy
The homepage carries about 2,509 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: “SHOP MAD HONEY JARS”.
10 calls to action
The homepage has 10 calls to action, for example “SHOP MAD HONEY JARS”, “BUY YOUR HONEY” and “Shop Mad Honey Jars”.
11 short forms
11 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 29 testimonial or review blocks, 6 customer or partner logos, 8 trust badges and “Loved by 100,000+ customers”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are 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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and TikTok Pixel (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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
42 other companies contacted
Loading the homepage contacts 42 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 realmadhoney.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus;WooCommerce Checkout
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on realmadhoney.com, including 7 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.