Website review, no card needed

beehero.io logo

beehero.io website review

Visit site (opens in a new tab)Reviewed 22 October 202632 issues · 85 checks

This review found 32 issues worth fixing on beehero.io, 11 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.4 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.8 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
109 ms75 msMay 2Aug 1595 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202688 ms
May 9, 202688 ms
May 23, 202679 ms
May 30, 202687 ms
Jun 6, 202689 ms
Jun 13, 202696 ms
Jun 20, 2026105 ms
Aug 15, 202695 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

Full-page screenshot of beehero.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix48
  • Reduce unused JavaScript

    5.9 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

  • Render-blocking requests

    1.6 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    300 ms · 44.1 MB

    22 files are served with short cache lifetimes, so returning visitors download them again (44.1 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and website-files.com and others), adding 46.5 MB and 1.3 s of main-thread time.

  • website-files.com adds 127 ms

    127 ms

    website-files.com costs a phone 127 ms of main-thread work and 44.2 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.

  • Reduce unused CSS

    900 ms · 228 KiB

    About 228 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • YouTube adds 838 ms

    838 ms

    YouTube costs a phone 838 ms of main-thread work and 1.9 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: 3.3 s

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

  • 13 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Improve image delivery

    27 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 15.3 s

    15.3 s

    Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • Total Blocking Time: 312 ms

    312 ms

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 88 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 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: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 530 ms

    530 ms

    Real visitors wait 530 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.013

    0.013

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

Images and page weight

1 to fix70
  • Page weight: 47.0 MB in 90 requests

    47.0 MB

    Your homepage downloads 47.0 MB in 90 requests on a phone: media 43.6 MB (8), scripts 2.4 MB (28) and images 494 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 13.3 g of CO₂ per visit

    13.32 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8894
  • 19 tap targets too small

    19 tap targets are too small or too close together to hit reliably with a finger.

  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 9278
  • Title is short (12 characters)

    Your title is only 12 characters: “BeeHero Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (265 characters)

    Your meta description is 265 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links with vague text

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

  • 58 internal links, 20 external

    The homepage links to 58 pages on beehero.io and 20 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Take Control of Your Pollination Today.”.

  • 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.beehero.io/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.beehero.io/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (460 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 12 pages without a meta description

    https://www.beehero.io/crops-we-pollinate, https://www.beehero.io/in-hive---precision-pollination-as-a-service, https://www.beehero.io/in-field---pollination-insight-platform-pip, https://www.beehero.io/beekeeping-solutions, https://www.beehero.io/technology and https://www.beehero.io/research and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.

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

  • 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 to fixGoogle 8891
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 373 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get A FREE Pollination Consultation”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact” and “Get a FREE PollinationConsultation”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 5 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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

    15

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 beehero.io, 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 Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on beehero.io, including 15 speed issues, 5 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