Website review, no card needed

brgsports.me logo

brgsports.me website review

Visit site (opens in a new tab)Reviewed 27 October 202645 issues · 85 checks

This review found 45 issues worth fixing on brgsports.me, 22 of them high impact, across 85 checks. The most urgent: improve image delivery. 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 brgsports.me (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brgsports.me at 0.6 s0.6 s
  2. brgsports.me at 1.3 s1.3 s
  3. brgsports.me at 1.9 s1.9 s
  4. brgsports.me at 2.5 s2.5 s
  5. brgsports.me at 3.1 s3.1 s
  6. brgsports.me at 3.8 s3.8 s
  7. brgsports.me at 4.4 s4.4 s
  8. brgsports.me at 5.0 s5.0 s

Speed

13 to fix35
  • Improve image delivery

    11.8 s · 2.5 MB

    13 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.8 s faster on a phone.

  • Use efficient cache lifetimes

    8.8 s · 2.0 MB

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

  • Reduce unused JavaScript

    5.6 s · 998 KiB

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

  • Render-blocking requests

    3.0 s

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

  • Reduce unused CSS

    1.1 s · 250 KiB

    About 250 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 2.1 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 (YouTube, jQuery CDN and Google CDN and others), adding 2.3 MB and 1.5 s of main-thread time.

  • YouTube adds 914 ms

    914 ms

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

  • 11 long tasks on the main thread

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

  • jQuery CDN adds 262 ms

    262 ms

    jQuery CDN costs a phone 262 ms of main-thread work and 30 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.

  • Google CDN adds 200 ms

    200 ms

    Google CDN costs a phone 200 ms of main-thread work and 348 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.

  • envisionwise.com adds 68 ms

    68 ms

    envisionwise.com costs a phone 68 ms of main-thread work and 394 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.

  • Minify JavaScript

    150 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 25 KiB

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

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix44
  • First Contentful Paint: 11.2 s

    11.2 s

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

  • Largest Contentful Paint: 29.7 s

    29.7 s

    Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 29.8 s

    29.8 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Total Blocking Time: 890 ms

    890 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

2 to fix50
  • Page weight: 5.2 MB in 71 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 71 requests on a phone: images 2.9 MB (29), scripts 1.6 MB (19) and fonts 368 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    585 KiB

    6 images are downloaded at several times the size a phone draws them, for example ChatGPTImageSep30202605_09_22PM.webp at 1,920 px wide, shown at 370 px. Resized copies would save about 585 KiB.

  • 1 image in older formats

    1 image (32 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.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 8686
  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 4 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

3 to fixGoogle 10079
  • No H1 headline

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

  • Title is short (10 characters)

    Your title is only 10 characters: “BRG Sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 8 internal links, 12 external

    The homepage links to 8 pages on brgsports.me and 12 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “BRG Sports is a division of Maine-based Bennett Radio Group that is committed to bringing you high quality video covera…”.

  • Structured data in place

    Structured data found: RadioStation.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://brgsports.me/sitemap.xml.

AI search readiness

2 to fix37
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • No llms.txt

    There is no https://brgsports.me/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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

1 to fix95
  • 5 pages without an H1

    https://brgsports.me/upcoming-games/event-calendar, https://brgsports.me/upcoming-games/submit-an-event, https://brgsports.me/past-games/youtube, https://brgsports.me/contact/contact-us and https://brgsports.me/advertise have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://brgsports.me/upcoming-games/event-calendar, https://brgsports.me/contact/contact-us and https://brgsports.me/advertise have 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.

  • 6 internal pages checked

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

6 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • 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 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 13 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://storage.googleapis.com/cdn-1-envisionwise/1/src/css/slick-slider/slick.css' from o…”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix56
  • 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.

  • 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 analytics detected

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

  • Only about 69 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Contact Us” and “contact us”.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 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 brgsports.me, 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
Hosting
Google Cloud

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 brgsports.me, including 19 speed issues, 3 SEO issues and 6 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