Website review, no card needed

barrybonds.com logo

barrybonds.com website review

Visit site (opens in a new tab)Reviewed 8 November 202645 issues · 89 checks

This review found 45 issues worth fixing on barrybonds.com, 19 of them high impact, across 89 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s1.1 sMay 16Jun 131.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.1 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.3 s

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 barrybonds.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. barrybonds.com at 0.6 s0.6 s
  2. barrybonds.com at 1.2 s1.2 s
  3. barrybonds.com at 1.8 s1.8 s
  4. barrybonds.com at 2.3 s2.3 s
  5. barrybonds.com at 2.9 s2.9 s
  6. barrybonds.com at 3.5 s3.5 s
  7. barrybonds.com at 4.1 s4.1 s
  8. barrybonds.com at 4.7 s4.7 s

Speed

7 to fix60
  • Render-blocking requests

    2.2 s

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

  • Reduce unused JavaScript

    1.2 s · 240 KiB

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

  • Mobile performance score: 60

    60/100

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

  • Improve image delivery

    50 ms · 797 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Twitter and Facebook and others), adding 2.7 MB and 384 ms of main-thread time.

  • Use efficient cache lifetimes

    400 ms · 68 KiB

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

  • Shopify adds 26 ms

    26 ms

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

  • Minify JavaScript

    150 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 16 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 20 KiB

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

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

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 647 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 11.4 s

    11.4 s

    Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Barry Bonds”.

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Time to Interactive: 11.4 s

    11.4 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • 33 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 33 ms

    33 ms

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

Images and page weight

4 to fix35
  • Page weight: 4.1 MB in 253 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 253 requests on a phone: images 2.3 MB (35), other files 768 KiB (96) and scripts 680 KiB (97). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    bb-business.jpg weighs 535 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (535 KiB) is 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.

  • 2 images far larger than shown

    6 KiB

    2 images are downloaded at several times the size a phone draws them, for example barry-bonds-san-francisco-giants-game.jpg at 600 px wide, shown at 195 px. Resized copies would save about 6 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (232 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.15 g

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

Accessibility

15 to fixGoogle 5578
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 4 tap targets too small

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

  • Form elements should have a visible label (3 elements)

    Form elements should have a visible label: 3 elements on the page fail this check, rated serious by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (58 elements)

    All page content should be contained by landmarks: 58 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 8 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 80 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

6 to fixGoogle 7771
  • No meta description

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

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Barry Bonds Official Website | San Francisco Giants Legend and BASHOF”.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“Barry Bonds Official Gear”, “Barry Bonds” and “OFFICIAL Barry Bonds GEAR”). One clear main headline is easier for people and search engines.

  • 27 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • Open Graph partly set

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

  • 152 internal links, 6 external

    The homepage links to 152 pages on barrybonds.com and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • 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://barrybonds.com/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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://barrybonds.com/collections/all-products, https://barrybonds.com/pages/bio, https://barrybonds.com/blogs/blog, https://barrybonds.com/blogs/news, https://barrybonds.com/pages/foundation and https://barrybonds.com/pages/media and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://barrybonds.com/blogs/blog and https://barrybonds.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://barrybonds.com/pages/media has 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 27 found) and read each the way a search engine does.

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

  • 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 9287
  • 16 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “"" is not a function”.

  • 3 low-resolution images

    3 images are 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

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

  • No analytics detected

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

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

    The homepage carries about 725 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP NOW”, “LEARN MORE” and “SUBSCRIBE”.

  • 6 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 2 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 barrybonds.com, 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

Framework
Angular
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 45 issues on barrybonds.com, including 12 speed issues, 6 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