Website review, no card needed

brightsport.com logo

brightsport.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 84 checks

This review found 36 issues worth fixing on brightsport.com, 11 of them high impact, across 84 checks. The most urgent: page weight: 92.8 MB in 144 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
3.5 s2.5 sMay 23Jul 42.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.3 s
May 30, 20263.1 s
Jun 6, 20262.8 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
274 ms154 msMay 30Jun 20168 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026260 ms
Jun 6, 2026208 ms
Jun 13, 2026168 ms
Jun 20, 2026168 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 brightsport.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brightsport.com at 0.5 s0.5 s
  2. brightsport.com at 1.0 s1.0 s
  3. brightsport.com at 1.5 s1.5 s
  4. brightsport.com at 2.0 s2.0 s
  5. brightsport.com at 2.5 s2.5 s
  6. brightsport.com at 3.0 s3.0 s
  7. brightsport.com at 3.5 s3.5 s
  8. brightsport.com at 4.1 s4.1 s

Speed

7 to fix73
  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (myshopify.com, Google Fonts and JSDelivr CDN and others), adding 84.7 MB and 2 ms of main-thread time.

  • Shopify adds 0 ms

    0 ms

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

  • Mobile performance score: 73

    73/100

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

  • Use efficient cache lifetimes

    500 ms · 105 KiB

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

  • Improve image delivery

    496 KiB

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

  • 2,230 HTML elements

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

  • Reduce unused CSS

    150 ms · 41 KiB

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.9 s

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

  • Server response: 61 ms

    61 ms

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

Core Web Vitals

3 to fix65
  • 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 element shown below.

  • Time to Interactive: 11.4 s

    11.4 s

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

  • 7 images without width and height

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

6 checks passed
  • Tap response (INP) got 28% faster for real visitors

    -28%

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

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

    -17%

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

  • Cumulative Layout Shift: 0.076

    0.076

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.0 s

    2.0 s

    Visually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix14
  • Page weight: 92.8 MB in 144 requests

    92.8 MB

    Your homepage downloads 92.8 MB in 144 requests on a phone: media 83.8 MB (11), images 7.8 MB (76) and scripts 659 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    3.7 MB

    11 images are downloaded at several times the size a phone draws them, for example 4312_x_3656_SETS-2.jpg at 4,312 px wide, shown at 65 px. Resized copies would save about 3.7 MB.

  • 4 images in older formats

    4 images (4.1 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.

  • An image on the first screen is lazy-loaded

    image_2024-06-05_124736160_600x.webp 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).

  • About 26.3 g of CO₂ per visit

    26.29 g

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

Accessibility

9 to fixGoogle 6787
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 8 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 53 images without alt text

    53 images have no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

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

  • 6 links without text

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

  • 4 form fields without a label

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “BRIGHT Sport | The Most Unique Balls on The Market – BRIGHT™ Europe”.

  • Meta description is long (187 characters)

    Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • 109 internal links, 4 external

    The homepage links to 109 pages on brightsport.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “.st0 { fill: #ed2f2f; } .st1 { fill: #ddd; } .st2 { fill: #fff; } .st3 { fill: #dd281f; } .st4 { fill: #ededed; }”.

  • Canonical URL set

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

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

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, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix60
  • 5 linked pages are broken

    Your homepage links to https://brightsport.com/products/bright-soccerball, https://brightsport.com/products/bright-sport-golf-balls-old, https://brightsport.com/products/bright%E2%84%A2-golf-balls, https://brightsport.com/products/bright%E2%84%A2-golf-balls-bogo and https://brightsport.com/products/the-bright%E2%84%A2-night-vision-glasses, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://brightsport.com/collections/all and https://brightsport.com/pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://brightsport.com/products/bright-basketball, https://brightsport.com/products/bright%E2%84%A2-rugby-football and https://brightsport.com/products/bright-grip-socks use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://brightsport.com/products/bright%E2%84%A2-rugby-football, whose canonical is https://brightsport.com/products/bright-rugby-football. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://brightsport.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • 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 10 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: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • About 691 words of copy

    The homepage carries about 691 words of visible text.

  • Urgency cues

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

7 checks passed
  • Clear next step on the first screen

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

  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop BRIGHT Balls”, “SHOP FINAL STOCK” and “Shop Our Bestsellers”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating, 1 trust badge and “more than 1,700 customers”.

  • Analytics in place

    Analytics detected: TikTok Pixel.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

  • 14 other companies contacted

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

Apps on your store

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

Apps your storefront loads

Kaching Bundles · Klaviyo Email Marketing Sms · loox.io · weglot.com · snapchat.com · trustpilot.com · nice-team.net · backinstock.org · 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

Stack

Framework
Vue.js
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 36 issues on brightsport.com, including 10 speed issues, 3 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
brightsport.com website review: scores and fixes