Website review, no card needed

brooklynfitboxing.com logo

brooklynfitboxing.com website review

Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 79 checks

This review found 38 issues worth fixing on brooklynfitboxing.com, 10 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
4.9 s1.8 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.0 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.3 s
Aug 29, 20264.0 s
Sep 5, 20264.4 s
Sep 12, 20264.5 s
Sep 19, 20264.4 s
Sep 26, 20263.8 s
Oct 3, 20263.1 s
Oct 10, 20262.6 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
277 ms223 msMay 9Oct 24246 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026229 ms
May 16, 2026235 ms
May 23, 2026237 ms
May 30, 2026241 ms
Jun 6, 2026244 ms
Jun 13, 2026244 ms
Jun 20, 2026243 ms
Jun 27, 2026241 ms
Jul 4, 2026239 ms
Jul 11, 2026238 ms
Jul 18, 2026239 ms
Jul 25, 2026237 ms
Aug 1, 2026236 ms
Aug 8, 2026240 ms
Aug 15, 2026243 ms
Aug 22, 2026249 ms
Aug 29, 2026262 ms
Sep 5, 2026269 ms
Sep 12, 2026271 ms
Sep 19, 2026270 ms
Sep 26, 2026263 ms
Oct 3, 2026259 ms
Oct 10, 2026256 ms
Oct 17, 2026253 ms
Oct 24, 2026246 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 brooklynfitboxing.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brooklynfitboxing.com at 0.4 s0.4 s
  2. brooklynfitboxing.com at 0.8 s0.8 s
  3. brooklynfitboxing.com at 1.1 s1.1 s
  4. brooklynfitboxing.com at 1.5 s1.5 s
  5. brooklynfitboxing.com at 1.9 s1.9 s
  6. brooklynfitboxing.com at 2.3 s2.3 s
  7. brooklynfitboxing.com at 2.6 s2.6 s
  8. brooklynfitboxing.com at 3.0 s3.0 s

Speed

10 to fix45
  • Reduce unused JavaScript

    2.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 45

    45/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and opticksprotection.com and others), adding 2.5 MB and 1.2 s of main-thread time.

  • Improve image delivery

    150 ms · 450 KiB

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

  • Google Tag Manager adds 432 ms

    432 ms

    Google Tag Manager costs a phone 432 ms of main-thread work and 686 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 353 ms

    353 ms

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

  • Main-thread work: 3.5 s

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

  • 1,533 HTML elements

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

  • Google Maps adds 75 ms

    75 ms

    Google Maps costs a phone 75 ms of main-thread work and 337 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

    150 ms · 45 KiB

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

  • 14 long tasks on the main thread

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

  • Use efficient cache lifetimes

    98 KiB

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

  • Legacy JavaScript

    25 KiB

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

  • Minify CSS

    7 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

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

  • Time to Interactive: 24.1 s

    24.1 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ESTA VEZ, SÍ. ELIJO FITBOXING. El problema no era el deport…”.

  • Speed Index: 6.0 s

    6.0 s

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

  • Real-user INP: 251 ms

    251 ms

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

  • Real-user TTFB: 836 ms

    836 ms

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

  • Cumulative Layout Shift: 0.237

    0.237

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

  • Total Blocking Time: 468 ms

    468 ms

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

  • 28 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 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 229 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

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

    -30%

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

Images and page weight

1 to fix33
  • Page weight: 6.1 MB in 157 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 157 requests on a phone: scripts 2.6 MB (46), media 1.4 MB (1) and images 1.0 MB (46). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.74 g

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

Accessibility

5 to fixGoogle 8885
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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.

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 67 images in the HTML carry an alt attribute.

  • 14 automated accessibility rules passed

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

SEO

4 to fixGoogle 9286
  • No structured data

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

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at brooklynfitboxing.com/robots.txt, the first file search crawlers ask for.

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

  • 25 internal links, 11 external

    The homepage links to 25 pages on brooklynfitboxing.com and 11 external pages.

5 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “La mayor red de clubes de fitboxing del mundo. Boxeo sin contacto y fuerza al ritmo de la música.”.

  • One H1 headline

    Your main headline reads: “Más de 275 clubes te esperan”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Brooklyn Fitboxing | La clase a la que siempre querrás volver”.

  • Canonical URL set

    The canonical URL is https://www.brooklynfitboxing.com/public/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix83
  • 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://www.brooklynfitboxing.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.brooklynfitboxing.com/public/es/en-us/club is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.brooklynfitboxing.com/public/es/en-us, whose canonical is https://www.brooklynfitboxing.com/public/es/es-es. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.brooklynfitboxing.com/public/es/en-us/privacy-policy, https://www.brooklynfitboxing.com/public/es/en-us/legal-notice, https://www.brooklynfitboxing.com/public/es/en-us/general-purchase-conditions and https://www.brooklynfitboxing.com/public/es/en-us/about-cookies have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 internal pages checked

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

4 checks passed
  • Linked pages load

    6 pages of 9 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • Only about 16 words

    The homepage has only about 16 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.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop” and “Call me”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 39 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 brooklynfitboxing.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
Analytics
Google Tag Manager
Hosting
Dinahosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on brooklynfitboxing.com, including 20 speed issues, 4 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