Website review, no card needed

fiaextremeh.com logo

fiaextremeh.com website review

Visit site (opens in a new tab)Reviewed 20 October 202654 issues · 89 checks

This review found 54 issues worth fixing on fiaextremeh.com, 23 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
5.2 s3.4 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.0 s
May 9, 20263.7 s
May 16, 20263.9 s
May 23, 20263.7 s
May 30, 20263.6 s
Jun 6, 20263.8 s
Jun 13, 20264.1 s
Jun 20, 20264.6 s
Jun 27, 20265.0 s
Jul 4, 20264.8 s
Jul 11, 20264.5 s
Jul 18, 20264.1 s
Jul 25, 20264.0 s
Aug 1, 20264.3 s
Aug 8, 20264.1 s
Aug 15, 20264.0 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
97 ms71 msMay 2Oct 1788 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202694 ms
May 9, 202693 ms
May 16, 202694 ms
May 23, 202690 ms
May 30, 202680 ms
Jun 6, 202684 ms
Jun 13, 202685 ms
Jun 20, 202684 ms
Jun 27, 202683 ms
Jul 4, 202675 ms
Jul 11, 202674 ms
Jul 18, 202676 ms
Jul 25, 202679 ms
Aug 1, 202683 ms
Aug 8, 202682 ms
Aug 15, 202681 ms
Aug 22, 202685 ms
Aug 29, 202679 ms
Sep 5, 202677 ms
Sep 12, 202677 ms
Sep 19, 202676 ms
Sep 26, 202683 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202688 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 fiaextremeh.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix34
  • Use efficient cache lifetimes

    76.0 s · 42.3 MB

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

  • Improve image delivery

    68.7 s · 23.9 MB

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

  • Reduce unused JavaScript

    5.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 5.9 s faster on a phone.

  • Render-blocking requests

    3.9 s

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

  • Mobile performance score: 34

    34/100

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

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    450 ms · 78 KiB

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

  • Main-thread work: 3.2 s

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

  • Google CDN adds 293 ms

    293 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google CDN and Google Tag Manager), adding 210 KiB and 416 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 24 KiB

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

  • Minify CSS

    150 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

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

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

  • Real-user LCP: 5.0 s

    5.0 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Largest Contentful Paint: 99.8 s

    99.8 s

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

  • Time to Interactive: 102.5 s

    102.5 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • 35 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user INP: 80 ms

    80 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 794 ms

    794 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 44.7 MB in 71 requests

    44.7 MB

    Your homepage downloads 44.7 MB in 71 requests on a phone: images 28.1 MB (47), media 14.3 MB (2) and scripts 1.7 MB (7). Under 2 MB keeps phones on slow connections fast.

  • 23 images over 500 KB

    23 images weigh 25.3 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    2.6 MB

    6 images are downloaded at several times the size a phone draws them, for example m30535_crop169005_1280x720_1790612647212A.png at 1,280 px wide, shown at 350 px. Resized copies would save about 2.6 MB.

  • 34 images in older formats

    34 images (28.0 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.

  • 19 images below the first screen load straight away

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

  • About 12.7 g of CO₂ per visit

    12.67 g

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

Accessibility

10 to fixGoogle 6686
  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 images without alt text

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

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 1 form field without a label

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

  • Headings should not be empty (5 elements)

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

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

8 to fixGoogle 7364
  • No H1 headline

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

  • 51 links crawlers can't follow

    51 links have no real href, so search engines can't follow them.

  • Title is short (9 characters)

    Your title is only 9 characters: “EXTREME H”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • Meta description is long (168 characters)

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

  • No robots.txt

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 39 internal links, 7 external

    The homepage links to 39 pages on fiaextremeh.com and 7 external pages.

2 checks passed
  • Open Graph tags complete

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.fiaextremeh.com/sitemap.xml.

AI search readiness

1 to fix81
  • 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.fiaextremeh.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
  • Text is in the HTML

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

Other pages

4 to fix81
  • 5 pages share a title

    /, https://www.fiaextremeh.com/home, https://www.fiaextremeh.com/fia-world-cup-format, https://www.fiaextremeh.com/teams and https://www.fiaextremeh.com/news all use the title “EXTREME H”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.fiaextremeh.com/fia-world-cup-format and https://www.fiaextremeh.com/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.fiaextremeh.com/home and https://www.fiaextremeh.com/teams use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.fiaextremeh.com/home, https://www.fiaextremeh.com/fia-world-cup-format, https://www.fiaextremeh.com/teams and https://www.fiaextremeh.com/news have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.fiaextremeh.com/fia-world-cup-format and https://www.fiaextremeh.com/news 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.

  • 14 internal pages checked

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

4 checks passed
  • Linked pages load

    10 pages of 14 loaded without an error (the rest turned automated requests away).

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

Best practices

3 to fixGoogle 7785
  • 17 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

    The homepage carries about 470 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 fiaextremeh.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
Angular
Analytics
Google Analytics
Hosting
AWS

Company

Founded
2025

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on fiaextremeh.com, including 18 speed issues, 8 SEO issues and 4 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