Website review, no card needed

cutterbuck.com logo

cutterbuck.com website review

Visit site (opens in a new tab)Reviewed 27 October 202635 issues · 81 checks

This review found 35 issues worth fixing on cutterbuck.com, 16 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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.1 s2.0 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
114 ms103 msMay 9Oct 24113 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026105 ms
May 23, 2026105 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026112 ms
Jul 4, 2026112 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026113 ms
Oct 24, 2026113 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 cutterbuck.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix45
  • Use efficient cache lifetimes

    4.8 s · 5.5 MB

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

  • Reduce unused JavaScript

    1.6 s · 793 KiB

    About 793 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 45

    45/100

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

  • Improve image delivery

    500 ms · 1.4 MB

    23 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Klaviyo and others), adding 3.0 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    450 ms · 74 KiB

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

  • Google Tag Manager adds 347 ms

    347 ms

    Google Tag Manager costs a phone 347 ms of main-thread work and 768 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.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Bigcommerce adds 114 ms

    114 ms

    Bigcommerce costs a phone 114 ms of main-thread work and 1.4 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.

  • Klaviyo adds 139 ms

    139 ms

    Klaviyo costs a phone 139 ms of main-thread work and 332 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.

  • 1,611 HTML elements

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

  • Legacy JavaScript

    250 ms · 71 KiB

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

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 244 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).

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

9 to fix67
  • 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: 19.2 s

    19.2 s

    Your largest element takes 19.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man wearing Seattle Seahawks branded pullover”.

  • Time to Interactive: 29.4 s

    29.4 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Total Blocking Time: 362 ms

    362 ms

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

  • 15 images without width and height

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

  • Cumulative Layout Shift: 0.112

    0.112

    The layout shifts by 0.112 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 106 ms

    106 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 503 ms

    503 ms

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

Images and page weight

1 to fix70
  • Page weight: 7.8 MB in 224 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 224 requests on a phone: images 4.8 MB (79), scripts 2.0 MB (86) and fonts 705 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.21 g

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

3 to fixGoogle 9393
  • 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.

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

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

  • 5 tap targets too small

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

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 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

4 to fixGoogle 9278
  • No H1 headline

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

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Work-to-Weekend Sportswear, Golf Apparel & Fan Gear - Cutter & Buck”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

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

  • No X (Twitter) card tag

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

  • 284 internal links, 2 external

    The homepage links to 284 pages on cutterbuck.com and 2 external pages.

5 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “From the office to outings to the great outdoors, explore sportswear, golf apparel, and fan gear that adapts across set…”.

  • Canonical URL set

    The canonical URL is https://cutterbuck.com/.

  • Structured data in place

    Structured data found: Corporation.

  • 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://cutterbuck.com/content/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://cutterbuck.com/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.

  • Organization data: 5 of 6 facts

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

Other pages

1 to fix95
  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://cutterbuck.com/men/polos, whose canonical is https://cutterbuck.com/men/polos-tees. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 190 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 9674
  • 1 broken image

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

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

4 checks passed
  • 33 calls to action

    The homepage has 33 calls to action, for example “Shop the Title Collection - UCLA Bruins”, “Shop Mens” and “Shop Women”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar, HubSpot and Plausible.

  • Direct contact links

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 2 other companies contacted

    Loading the homepage contacts 2 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 cutterbuck.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager | Hotjar | Plausible
Hosting
Bigcommerce

Company

Employees
382
Founded
1990
Headquarters
Seattle

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on cutterbuck.com, including 21 speed issues, 4 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