Website review, no card needed

huckberry.shop logo

huckberry.shop website review

Visit site (opens in a new tab)Reviewed 8 November 202647 issues · 87 checks

This review found 47 issues worth fixing on huckberry.shop, 23 of them high impact, across 87 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

Full-page screenshot of huckberry.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. huckberry.shop at 0.7 s0.7 s
  2. huckberry.shop at 1.4 s1.4 s
  3. huckberry.shop at 2.1 s2.1 s
  4. huckberry.shop at 2.8 s2.8 s
  5. huckberry.shop at 3.5 s3.5 s
  6. huckberry.shop at 4.2 s4.2 s
  7. huckberry.shop at 4.9 s4.9 s
  8. huckberry.shop at 5.7 s5.7 s

Speed

11 to fix28
  • Reduce unused JavaScript

    5.9 s · 1.4 MB

    About 1.4 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.

  • huckberry.com adds 2.8 s

    2.8 s

    huckberry.com costs a phone 2.8 s of main-thread work and 2.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Use efficient cache lifetimes

    1.7 s · 571 KiB

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

  • Mobile performance score: 28

    28/100

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

  • 8,379 HTML elements

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

  • Main-thread work: 7.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (huckberry.com, alhena.ai and TikTok and others), adding 3.2 MB and 3.5 s of main-thread time.

  • Avoid multiple page redirects

    901 ms

    The page goes through 2 redirects before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    500 ms

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

  • alhena.ai adds 199 ms

    199 ms

    alhena.ai costs a phone 199 ms of main-thread work and 318 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.

  • Legacy JavaScript

    200 ms · 51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 56 KiB

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

  • Duplicated JavaScript

    150 ms · 7 KiB

    7 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Document request latency

    150 ms

    The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Improve image delivery

    13 KiB

    1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    8 KiB

    8 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: 28 ms

    28 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Largest Contentful Paint: 25.0 s

    25.0 s

    Your largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “immersive-hero-mobile-4-6-aspect-ratio-2.jpg”.

  • Speed Index: 16.1 s

    16.1 s

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

  • Time to Interactive: 30.6 s

    30.6 s

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

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 404 ms

    404 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 920 ms

    920 ms

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

  • 1 image without width and height

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.6 MB in 276 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 276 requests on a phone: scripts 2.9 MB (86), images 898 KiB (70) and fonts 252 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 157.6 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

5 to fixGoogle 7486
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    2 dropdowns have no label.

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (1 element).

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • SVG elements with an img role do not have an accessible text alternative

    SVG elements with an img role do not have an accessible text alternative (130 elements).

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

6 to fixGoogle 7768
  • Page is set to noindex

    The robots meta tag says “noindex”: Google is told not to list this page at all.

  • Canonical points to another host

    Your canonical URL points to huckberry.com, not huckberry.shop, so Google may credit that host instead.

  • 24 links with vague text

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

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

  • One H1 headline

    Your <h1> is empty.

  • 25 internal links, 0 external

    The homepage links to 25 pages on huckberry.shop and 0 external pages.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Curating the world’s coolest men’s clothing, footwear, gear and gifts. Free U.S. Shipping +$98, Free Returns and Unreal…”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Huckberry: The One Stop Men’s Shop”.

  • 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://huckberry.shop/sitemap.xml.

AI search readiness

100
3 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.

  • llms.txt published

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

Other pages

6 to fix60
  • 1 page without a title

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

  • 13 linked pages hidden from search

    https://huckberry.shop/customer_authentication/redirect, https://huckberry.shop/products/ford-mechanics-shirt, https://huckberry.shop/products/fast-lane-logo-snapback-hat, https://huckberry.shop/products/streak-logo-rope-hat, https://huckberry.shop/products/ripstop-huck-patch-hat-1 and https://huckberry.shop/products/streak-logo-snapback-hat and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://huckberry.shop/products/fast-lane-logo-snapback-hat and https://huckberry.shop/products/streak-logo-snapback-hat all use the title “Fast Lane Logo Snapback Hat – Huckberry”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://huckberry.shop/customer_authentication/redirect, https://huckberry.shop/policies/refund-policy, https://huckberry.shop/policies/privacy-policy, https://huckberry.shop/policies/terms-of-service and https://huckberry.shop/policies/contact-information have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://huckberry.shop/products/fast-lane-logo-snapback-hat and https://huckberry.shop/products/streak-logo-snapback-hat use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://huckberry.shop/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

Best practices

2 to fixGoogle 9274
  • 1 broken image

    1 image failed to load on a phone, for example https://huckberry.com/favicon.ico.

  • 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 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 37 words

    The homepage has only about 37 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact information”.

  • 4 short forms

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

Privacy and tracking

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 6 of them by other companies (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.

  • 3 other companies contacted

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

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 huckberry.shop, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on huckberry.shop, including 22 speed issues, 6 SEO issues and 5 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