Website review, no card needed

hydrobuilder.com logo

hydrobuilder.com website review

Visit site (opens in a new tab)Reviewed 5 November 202624 issues · 103 checks

This review found 24 issues worth fixing on hydrobuilder.com, 5 of them high impact, across 103 checks. The most urgent: 4,606 HTML elements. 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
1.8 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
110 ms91 msMay 16Oct 31108 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026102 ms
May 23, 2026104 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 2026105 ms
Jun 20, 2026105 ms
Jun 27, 2026104 ms
Jul 4, 202698 ms
Jul 11, 202695 ms
Jul 18, 202693 ms
Jul 25, 202693 ms
Aug 1, 202696 ms
Aug 8, 202697 ms
Aug 15, 202698 ms
Aug 22, 2026101 ms
Aug 29, 2026101 ms
Sep 5, 2026101 ms
Sep 12, 2026102 ms
Sep 19, 2026103 ms
Sep 26, 2026104 ms
Oct 3, 2026105 ms
Oct 10, 2026105 ms
Oct 17, 2026105 ms
Oct 24, 2026105 ms
Oct 31, 2026108 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 hydrobuilder.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hydrobuilder.com at 0.6 s0.6 s
  2. hydrobuilder.com at 1.3 s1.3 s
  3. hydrobuilder.com at 1.9 s1.9 s
  4. hydrobuilder.com at 2.6 s2.6 s
  5. hydrobuilder.com at 3.2 s3.2 s
  6. hydrobuilder.com at 3.9 s3.9 s
  7. hydrobuilder.com at 4.5 s4.5 s
  8. hydrobuilder.com at 5.1 s5.1 s

hydrobuilder.com does not allow embedding, so this is Google's rendering of the page.

Speed

7 to fix72
  • 4,606 HTML elements

    The page has 4,606 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 72

    72/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    480 ms · 188 KiB

    About 188 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 1.2 MB and 519 ms of main-thread time.

  • Shopify adds 268 ms

    268 ms

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

  • Main-thread work: 3.3 s

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

  • Improve image delivery

    150 ms · 143 KiB

    8 images could be 143 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    180 ms · 49 KiB

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    8 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (8 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: 16 ms

    16 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “built for growers mobile banner”.

  • Time to Interactive: 8.2 s

    8.2 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

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

    1.6 s

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

  • Real-user INP: 142 ms

    142 ms

    Real visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (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: 487 ms

    487 ms

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

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 122 ms

    122 ms

    Scripts block the page for only 122 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 260 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 260 requests on a phone: other files 1.3 MB (128), images 1,013 KiB (37) and scripts 910 KiB (75). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    BioSafe_Homepage_Banner-mobile_f81bc9ee-d266-4784-8ded-b7057 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).

  • 3 images in older formats

    3 images (224 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.

  • About 1.0 g of CO₂ per visit

    1.02 g

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

1 checks passed
  • 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 10096
  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 132 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Hydroponics Supplies, Grow Lights, Tents & Nutrients | Hydrobuilder”.

  • 1,215 internal links, 21 external

    The homepage links to 1,215 pages on hydrobuilder.com and 21 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Trusted hydroponics supplier since 2011. 25,000+ grow lights, nutrients, tents & CEA equipment with expert grower suppo…”.

  • One H1 headline

    Your main headline reads: “Hydrobuilder”.

  • Canonical URL set

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

AI search readiness

1 to fix83
  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (7 KiB, 28 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to /pages/brands, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without an H1

    /pages/contact, /pages/commercial, /pages/grow-diagnostics-plant-health-testing-services, /collections/sale, /collections/new-products and /collections/garden-care-pest-control and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    /pages/contact, /pages/commercial, /pages/grow-diagnostics-plant-health-testing-services, /collections/sale, /collections/new-products and /collections/garden-care-pest-control and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <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: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://hbhold.com/partner-with-us/.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (hydrobuilder.com).

  • Valid certificate (53 days left)

    The certificate from Let's Encrypt · YE1 verifies for hydrobuilder.com and is valid for another 53 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://hydrobuilder.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 52 links work

    All 52 links checked from your homepage (40 internal, 12 external) answered without errors.

Domain and trust

  • DNSSEC is off

    hydrobuilder.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

3 checks passed
  • Domain is 16 years old

    16 years

    hydrobuilder.com was registered in Oct 2010 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Certificate issuers are restricted

    CAA records allow only comodoca.com, digicert.com, godaddy.com and letsencrypt.org to issue certificates for hydrobuilder.com, so a mis-issued certificate from anyone else is refused.

  • Registered until Oct 2027

    hydrobuilder.com is registered until Oct 2027.

Content and conversion

1 to fix94
  • 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 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 895 words of copy

    The homepage carries about 895 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop BioSafe” and “Shop ProKure”.

  • 238 calls to action

    The homepage has 238 calls to action, for example “SHOP ILUMINAR”, “SHOP CLIMATEIQ” and “SHOP EZTRIM”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 32 testimonial or review blocks, 5 customer or partner logos, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 3 email links.

  • Phone number on the homepage

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

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be hydrobuilder.com is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 70/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.mandrillapp.com include:servers.mcsv.net include:sent-via.netsuite.com include:mailsenders.netsuite.…”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “selector1” and “k1”), so receivers can verify mail really came from you.

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, Klaviyo and Microsoft Ads (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

  • Hulk Product Options · problem reported Oct 2026attackers planted code in its settings that sent shoppers who pressed Checkout to a fake checkout page taking card details. What to do: update the app, check its settings for code or HTML you didn't add, and test checkout in a private window.
  • Selleasy · problem reported Oct 2026attackers planted code in its settings that sent shoppers who pressed Checkout to a fake checkout page taking card details. What to do: update the app, check its settings for code or HTML you didn't add, and test checkout in a private window.

Your store uses an app that was used in an attack. That is not a sign you were hit: check the app as described.

Apps your storefront loads

Sc Easy Redirects · Klaviyo Email Marketing Sms · Blocky Fraud Blocker · Judge Me Reviews · Cbb Keep Share Cart · Klip Coupons · Quicky · Stockiq · Selleasy · Stape Remix · Hulk Product Options

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

CMS
WordPress
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 24 issues on hydrobuilder.com, including 10 speed issues, 1 SEO issue and 1 conversion gap. 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