Website review, no card needed

benchmadecutlery.net logo

benchmadecutlery.net website review

Visit site (opens in a new tab)Reviewed 16 November 202642 issues · 81 checks

This review found 42 issues worth fixing on benchmadecutlery.net, 17 of them high impact, across 81 checks. The most urgent: page weight: 15.8 MB in 599 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 benchmadecutlery.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. benchmadecutlery.net at 0.8 s0.8 s
  2. benchmadecutlery.net at 1.5 s1.5 s
  3. benchmadecutlery.net at 2.3 s2.3 s
  4. benchmadecutlery.net at 3.1 s3.1 s
  5. benchmadecutlery.net at 3.8 s3.8 s
  6. benchmadecutlery.net at 4.6 s4.6 s
  7. benchmadecutlery.net at 5.4 s5.4 s
  8. benchmadecutlery.net at 6.1 s6.1 s

Speed

15 to fix35
  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 11.7 s

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

  • Mobile performance score: 35

    35/100

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

  • 5,298 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, benchmade.com and alia-prod.com and others), adding 14.4 MB and 2.8 s of main-thread time.

  • benchmade.com adds 480 ms

    480 ms

    benchmade.com costs a phone 480 ms of main-thread work and 11.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.

  • Reduce unused JavaScript

    1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 688 ms

    688 ms

    Google Tag Manager costs a phone 688 ms of main-thread work and 911 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.

  • Use efficient cache lifetimes

    150 ms · 582 KiB

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

  • alia-prod.com adds 421 ms

    421 ms

    alia-prod.com costs a phone 421 ms of main-thread work and 610 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.

  • Reduce unused CSS

    300 ms · 104 KiB

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

  • Shopify adds 284 ms

    284 ms

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    316 KiB

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

  • Osano CMP adds 305 ms

    305 ms

    Osano CMP costs a phone 305 ms of main-thread work and 86 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

    76 KiB

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

  • Minify JavaScript

    22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 88 ms

    88 ms

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

Core Web Vitals

6 to fix39
  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Benchmade knife with bronze blade and camouflage handle lie…”.

  • 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: 42.2 s

    42.2 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • 3 images without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

3 to fix45
  • Page weight: 15.8 MB in 599 requests

    15.8 MB

    Your homepage downloads 15.8 MB in 599 requests on a phone: media 6.6 MB (4), scripts 3.7 MB (170) and images 3.4 MB (36). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    CONSUMER_P1-_DT_402b58b7-2bdd-44dc-8df7-16c7596fbd3d.webp weighs 655 KiB. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (1.7 MB) 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 4.5 g of CO₂ per visit

    4.49 g

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

2 checks passed
  • 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 fix85
  • Zoom is disabled

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

  • 2 text elements with low contrast

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

  • 2 links without text

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

  • 2 tap targets too small

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

1 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

SEO

9 to fixGoogle 5434
  • Page is set to noindex

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

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (20 characters)

    Your title is only 20 characters: “Benchmadecutlery.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Canonical points to another host

    Your canonical URL points to benchmade.com, not benchmadecutlery.net, so Google may credit that host instead.

  • Structured data has 2 problems

    Structured data found (Organization and SiteNavigationElement) but with 2 problems, for example “Organization: url points at a different host (https://www.benchmade.com/pages/benchmadecutlery-com)”.

  • No XML sitemap

    No XML sitemap at https://www.benchmade.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 301 internal links, 17 external

    The homepage links to 301 pages on benchmadecutlery.net and 17 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 8887
  • 10 small tap targets

    10 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://www.benchmade.com/api/collect' from origin 'https://benchmadecutlery.net' has been blocked …”.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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 analytics detected

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

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

    The homepage carries about 266 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

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

  • 44 calls to action

    The homepage has 44 calls to action, for example “SHOP ELIGIBLE KNIVES”, “SHOP” and “Shop By Category”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

  • 36 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) loads with the page.

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 benchmadecutlery.net, 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
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on benchmadecutlery.net, including 21 speed issues, 9 SEO issues and 3 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