Website review, no card needed

fiba.basketball logo

fiba.basketball website review

Visit site (opens in a new tab)Reviewed 30 October 202647 issues · 84 checks

This review found 47 issues worth fixing on fiba.basketball, 19 of them high impact, across 84 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
3.9 s2.3 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.6 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.9 s
Oct 17, 20263.2 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
835 ms539 msMay 9Oct 24664 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026772 ms
May 16, 2026776 ms
May 23, 2026763 ms
May 30, 2026754 ms
Jun 6, 2026781 ms
Jun 13, 2026786 ms
Jun 20, 2026801 ms
Jun 27, 2026795 ms
Jul 4, 2026762 ms
Jul 11, 2026718 ms
Jul 18, 2026682 ms
Jul 25, 2026675 ms
Aug 1, 2026615 ms
Aug 8, 2026573 ms
Aug 15, 2026575 ms
Aug 22, 2026575 ms
Aug 29, 2026641 ms
Sep 5, 2026675 ms
Sep 12, 2026649 ms
Sep 19, 2026644 ms
Sep 26, 2026617 ms
Oct 3, 2026573 ms
Oct 10, 2026638 ms
Oct 17, 2026684 ms
Oct 24, 2026664 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 fiba.basketball (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fiba.basketball at 0.7 s0.7 s
  2. fiba.basketball at 1.5 s1.5 s
  3. fiba.basketball at 2.2 s2.2 s
  4. fiba.basketball at 2.9 s2.9 s
  5. fiba.basketball at 3.6 s3.6 s
  6. fiba.basketball at 4.4 s4.4 s
  7. fiba.basketball at 5.1 s5.1 s
  8. fiba.basketball at 5.8 s5.8 s

Speed

13 to fix28
  • Reduce unused JavaScript

    1.9 s · 1.2 MB

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

  • Use efficient cache lifetimes

    1.1 s · 568 KiB

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

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 8.2 s

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

  • 3,091 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, fuseplatform.net and Google CDN and others), adding 2.4 MB and 2.2 s of main-thread time.

  • Google Tag Manager adds 583 ms

    583 ms

    Google Tag Manager costs a phone 583 ms of main-thread work and 673 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.

  • fuseplatform.net adds 562 ms

    562 ms

    fuseplatform.net costs a phone 562 ms of main-thread work and 336 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.

  • Improve image delivery

    150 ms · 346 KiB

    18 images could be 346 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 CDN adds 413 ms

    413 ms

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 79 KiB

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

  • confiant-integrations.net adds 260 ms

    260 ms

    confiant-integrations.net costs a phone 260 ms of main-thread work and 174 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 · 77 KiB

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

  • Render-blocking requests

    200 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 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.

1 checks passed
  • Server response: 43 ms

    43 ms

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

Core Web Vitals

13 to fix0
  • 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.

  • Real-user INP: 652 ms

    652 ms

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

  • Real-user CLS: 0.50

    0.50

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “On this website, you maintain control over the cookies and …”.

  • Time to Interactive: 32.6 s

    32.6 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.171

    0.171

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 8 images without width and height

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

2 checks passed
  • Tap response (INP) got 13% faster for real visitors

    -13%

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

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

    -12%

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

Images and page weight

2 to fix64
  • Page weight: 5.3 MB in 208 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 208 requests on a phone: scripts 3.3 MB (79), images 906 KiB (44) and other files 645 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    kdwjo5yyaa4gbovdaf5n 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 1.5 g of CO₂ per visit

    1.49 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8389
  • 15 buttons without a name

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

  • Invalid ARIA attributes

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

  • 12 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 24 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 3 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 long (94 characters)

    Your title is 94 characters, so Google will cut it off around 60: “The Home of FIBA Basketball - News, Stats, Games, Results, Calendar & Events | FIBA Baske…”.

  • No structured data

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

  • 40 internal links, 25 external

    The homepage links to 40 pages on fiba.basketball and 25 external pages.

5 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “The Official website of FIBA basketball events. Browse news, schedules, stats, rankings, results and events calendar.”.

  • Canonical URL set

    The canonical URL is https://www.fiba.basketball/en.

  • 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://www.fiba.basketball/en/sitemap_index.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    48%

    The HTML your server sends has 312 of the 652 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.fiba.basketball/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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

1 to fix95
  • 10 links to non-canonical URLs

    Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.fiba.basketball/en/news/everything-you-need-to-know-about-suhail-fiba-basketball-world-cup-2027-mascot, whose canonical is https://www.fiba.basketball/en/events/fiba-basketball-world-cup-2027/news/everything-you-need-to-know-about-suhail-fiba-basketball-world-cup-2027-mascot. 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 35 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

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: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

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

    The homepage carries about 652 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Buy Now” and “Register Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Azure

Company

Founded
1932
Headquarters
Mies

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on fiba.basketball, including 26 speed issues, 3 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