Website review, no card needed

iaaf.org logo

iaaf.org website review

Visit site (opens in a new tab)Reviewed 29 October 202647 issues · 85 checks

This review found 47 issues worth fixing on iaaf.org, 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

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.8 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.2 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.8 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
199 ms157 msMay 9Oct 24183 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026177 ms
May 16, 2026176 ms
May 23, 2026176 ms
May 30, 2026175 ms
Jun 6, 2026182 ms
Jun 13, 2026178 ms
Jun 20, 2026178 ms
Jun 27, 2026179 ms
Jul 4, 2026180 ms
Jul 11, 2026183 ms
Jul 18, 2026182 ms
Jul 25, 2026179 ms
Aug 1, 2026172 ms
Aug 8, 2026177 ms
Aug 15, 2026171 ms
Aug 22, 2026170 ms
Aug 29, 2026171 ms
Sep 5, 2026162 ms
Sep 12, 2026188 ms
Sep 19, 2026193 ms
Sep 26, 2026194 ms
Oct 3, 2026194 ms
Oct 10, 2026182 ms
Oct 17, 2026181 ms
Oct 24, 2026183 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 iaaf.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iaaf.org at 0.8 s0.8 s
  2. iaaf.org at 1.7 s1.7 s
  3. iaaf.org at 2.5 s2.5 s
  4. iaaf.org at 3.3 s3.3 s
  5. iaaf.org at 4.2 s4.2 s
  6. iaaf.org at 5.0 s5.0 s
  7. iaaf.org at 5.8 s5.8 s
  8. iaaf.org at 6.7 s6.7 s

Speed

9 to fix28
  • Improve image delivery

    1.4 s · 13.2 MB

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

  • Reduce unused JavaScript

    5.5 s · 1.4 MB

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

  • Render-blocking requests

    1.1 s

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

  • 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: 4.3 s

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

  • 3,581 HTML elements

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

  • Reduce unused CSS

    750 ms · 146 KiB

    About 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 61 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Cookiebot and others), adding 753 KiB and 402 ms of main-thread time.

  • Minify CSS

    150 ms · 51 KiB

    51 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    143 KiB

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

  • 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: 157 ms

    157 ms

    Your server sent the HTML in 157 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 CLS: 0.30

    0.30

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • First Contentful Paint: 17.4 s

    17.4 s

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

  • Largest Contentful Paint: 23.1 s

    23.1 s

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

  • Speed Index: 17.4 s

    17.4 s

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

  • Time to Interactive: 31.4 s

    31.4 s

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

  • Cumulative Layout Shift: 0.273

    0.273

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 252 ms

    252 ms

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 532 ms

    532 ms

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

Images and page weight

5 to fix18
  • Page weight: 31.1 MB in 154 requests

    31.1 MB

    Your homepage downloads 31.1 MB in 154 requests on a phone: images 27.4 MB (61), scripts 3.1 MB (37) and stylesheets 177 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 24 images over 500 KB

    24 images weigh 24.6 MB together. On a phone connection a single image that size takes seconds.

  • 34 images far larger than shown

    19.2 MB

    34 images are downloaded at several times the size a phone draws them, for example 68cd5a3f3279fd93a0604d11.jpg at 4,577 px wide, shown at 351 px. Resized copies would save about 19.2 MB.

  • 40 images in older formats

    40 images (27.3 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.

  • 34 images below the first screen load straight away

    34 images further down the page (26.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 8.8 g of CO₂ per visit

    8.81 g

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

Accessibility

5 to fixGoogle 8292
  • 6 buttons without a name

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

  • 9 text elements with low contrast

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

  • 51 images without alt text

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

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

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

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 7779
  • No structured data

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

  • Meta description is short (25 characters)

    Your meta description is only 25 characters: “World Athletics Home Page”. 70 to 160 characters is enough to sell the click.

  • 26 H1 headlines

    There are 26 <h1> headlines (“World Athletics establishes new Running & Mass Pa…”, “World Athletics strengthens role of Kids' Athleti…” and “Henderson and Kawano set world marathon race walk…”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://worldathletics.org/sitemap/sitemapindex.xml, so Google discovers your pages only by following links.

  • 4 links with vague text

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

  • 70 internal links, 14 external

    The homepage links to 70 pages on iaaf.org and 14 external pages.

4 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “World Athletics Home Page | World Athletics”.

  • Canonical URL set

    The canonical URL is https://worldathletics.org/.

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

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

    51%

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

  • No llms.txt

    There is no https://worldathletics.org/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

3 to fix83
  • 7 pages share a title

    https://worldathletics.org/news, https://worldathletics.org/news/press-releases, https://worldathletics.org/news/news, https://worldathletics.org/news/reports, https://worldathletics.org/news/previews and https://worldathletics.org/news/features and 1 other all use the title “News | World Athletics”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://worldathletics.org/news, https://worldathletics.org/news/press-releases, https://worldathletics.org/news/news, https://worldathletics.org/news/reports, https://worldathletics.org/news/previews and https://worldathletics.org/news/features and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://worldathletics.org/worldathletics-plus, https://worldathletics.org/news/press-releases, https://worldathletics.org/news/news, https://worldathletics.org/news/reports, https://worldathletics.org/news/previews and https://worldathletics.org/news/features and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://worldathletics.org/news/press-releases, https://worldathletics.org/news/news, https://worldathletics.org/news/reports, https://worldathletics.org/news/previews, https://worldathletics.org/news/features and https://worldathletics.org/news/series and 2 others 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.

  • 2 pages slow to respond

    https://worldathletics.org/videos and https://worldathletics.org/competitions took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 “Uncaught (in promise) Error: Bloomreach Engagement initialization failed”.

  • 5 low-resolution images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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 846 words of copy

    The homepage carries about 846 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Register now”, “Shop” and “Kebinatshipi: ‘This was just the start’”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 iaaf.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Rackspace

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 iaaf.org, including 22 speed issues, 6 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