Website review, no card needed

drewshoneybees.com logo

drewshoneybees.com website review

Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 65 checks

This review found 24 issues worth fixing on drewshoneybees.com, 4 of them high impact, across 65 checks. The most urgent: page weight: 8.7 MB in 176 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of drewshoneybees.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drewshoneybees.com at 0.4 s0.4 s
  2. drewshoneybees.com at 0.8 s0.8 s
  3. drewshoneybees.com at 1.1 s1.1 s
  4. drewshoneybees.com at 1.5 s1.5 s
  5. drewshoneybees.com at 1.9 s1.9 s
  6. drewshoneybees.com at 2.3 s2.3 s
  7. drewshoneybees.com at 2.6 s2.6 s
  8. drewshoneybees.com at 3.0 s3.0 s

Speed

4 to fix86
  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Google Tag Manager and shop.app), adding 4.2 MB and 456 ms of main-thread time.

  • Shopify adds 245 ms

    245 ms

    Shopify costs a phone 245 ms of main-thread work and 4.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.

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 839 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 248 ms. During a long task the page ignores taps.

  • Improve image delivery

    220 KiB

    10 images could be 220 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    117 KiB

    About 117 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    100 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    5 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).

  • 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: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix92
  • Speed Index: 5.2 s

    5.2 s

    Visually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 5.2 s

    5.2 s

    The page becomes fully interactive after 5.2 s. Good is under 3.8 s.

  • Total Blocking Time: 236 ms

    236 ms

    Scripts block taps and scrolling for 236 ms in total while the page loads. Good is under 200 ms.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “HONEY, BUT BETTER”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix42
  • Page weight: 8.7 MB in 176 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 176 requests on a phone: media 6.8 MB (4), other files 723 KiB (71) and images 535 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    A_better_outcome_you_can_hold-modified.webp 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).

  • 9 images in older formats

    9 images (702 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.

  • 3 images far larger than shown

    27 KiB

    3 images are downloaded at several times the size a phone draws them, for example DHB-Ecomm-Ginger-Front_480e07ca-fd92-4097-a2ae-0fa754269512. at 533 px wide, shown at 161 px. Resized copies would save about 27 KiB.

  • About 2.5 g of CO₂ per visit

    2.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.46 g of CO₂e: 295.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

2 to fixGoogle 9296
  • 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.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 61 internal links, 8 external

    The homepage links to 61 pages on drewshoneybees.com and 8 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Drew's Honeybees keeps bees in wilds of southern New England to bring you the best of sensuously tasty Velvet Honeys an…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Drew's Honeybees–Better, Kinder Products from Healthy Bees”.

  • Canonical URL set

    The canonical URL is https://www.drewshoneybees.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://www.drewshoneybees.com/sitemap.xml.

AI search readiness

100
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 (601 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.drewshoneybees.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.drewshoneybees.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.drewshoneybees.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://www.drewshoneybees.com/collections/all, https://www.drewshoneybees.com/customer_authentication/redirect, https://www.drewshoneybees.com/policies/shipping-policy, https://www.drewshoneybees.com/blogs/coalition-for-better-outcomes and https://www.drewshoneybees.com/blogs/better-beekeeping have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.drewshoneybees.com/customer_authentication/redirect, https://www.drewshoneybees.com/pages/our-values and https://www.drewshoneybees.com/pages/wellness 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.

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

1 to fixGoogle 9693
  • 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

    51 of 60 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 333 words of copy

    The homepage carries about 333 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP NOW” and “Contact Us”.

  • 12 short forms

    12 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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

    6

    Opening 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 drewshoneybees.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews

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

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Norwich

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on drewshoneybees.com, including 8 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25