Website review, no card needed
fiaformulae.com website review
Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 79 checks
This review found 34 issues worth fixing on fiaformulae.com, 11 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 171 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 168 ms |
| Jun 6, 2026 | 167 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 211 ms |
| Jun 27, 2026 | 217 ms |
| Jul 4, 2026 | 223 ms |
| Jul 11, 2026 | 223 ms |
| Jul 18, 2026 | 213 ms |
| Jul 25, 2026 | 210 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 253 ms |
| Aug 29, 2026 | 254 ms |
| Sep 5, 2026 | 253 ms |
| Sep 12, 2026 | 243 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 208 ms |
| Oct 3, 2026 | 201 ms |
| Oct 10, 2026 | 194 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 184 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
How it loaded on a phone
0.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.0 s
4.6 s
Speed
Reduce unused JavaScript
2.9 s · 537 KiBAbout 537 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 873 KiB36 files are served with short cache lifetimes, so returning visitors download them again (873 KiB).
Render-blocking requests
1.6 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
600 ms · 999 KiB22 images could be 999 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 177 KiBAbout 177 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and bloomreach.com and others), adding 3.4 MB and 341 ms of main-thread time.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 305 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
boltdns.net adds 0 ms
0 msboltdns.net costs a phone 0 ms of main-thread work and 1.3 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.
brightcovecdn.com adds 0 ms
0 msbrightcovecdn.com costs a phone 0 ms of main-thread work and 945 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.
stadion.io adds 0 ms
0 msstadion.io costs a phone 0 ms of main-thread work and 758 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.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 21.8 s
21.8 sYour largest element takes 21.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Every race winner of the 2025/26 Formula E Season (so far)”.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Speed Index: 13.2 s
13.2 sVisually, the page fills in at 13.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 847 ms
847 msReal visitors wait 847 ms for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 171 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 33% faster for real visitors
-33%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 195 ms
195 msScripts block the page for only 195 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 128 requests
4.7 MBYour homepage downloads 4.7 MB in 128 requests on a phone: images 3.0 MB (49), scripts 1.1 MB (36) and stylesheets 272 KiB (20). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
906 KiB6 images are downloaded at several times the size a phone draws them, for example image.jpg at 1,280 px wide, shown at 246 px. Resized copies would save about 906 KiB.
6 images in older formats
6 images (1.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.
An image on the first screen is lazy-loaded
WhatsApp_Image_2026-10-21_at_15.36.41__1_.jpeg 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.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 161.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail 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.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
103 internal links, 15 external
The homepage links to 103 pages on fiaformulae.com and 15 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Formula E is Change.Accelerated. Get the latest news, video highlights, race results, calendar, team & driver profiles …”.
One H1 headline
Your main headline reads: “Official Home of the ABB FIA Formula E World Championship”.
Title: 57 characters
Your title is a healthy 57 characters: “Official Home of the ABB FIA Formula E World Championship”.
Canonical URL set
The canonical URL is https://www.fiaformulae.com/en.
Structured data in place
Structured data found: SportsOrganization and WebSite.
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.fiaformulae.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.fiaformulae.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (795 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.fiaformulae.com/en/calendar, https://www.fiaformulae.com/en/tickets, https://www.fiaformulae.com/en/ways-to-watch and https://www.fiaformulae.com/en/video have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.fiaformulae.com/en/video has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.fiaformulae.com/en/fia-girls-on-track took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 found) and read each the way a search engine does.
5 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.
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 15 pages that loaded have a <title>.
Best practices
23 small tap targets
23 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “gtag is not defined”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 779 words of copy
The homepage carries about 779 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Shop” and “Register”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Quantcast (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 fiaformulae.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
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Google Cloud
Company
- Founded
- 2014
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on fiaformulae.com, including 20 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.