finishers.com website review

Your mobile performance score is 69 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

About 164 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

4 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 third-party services load with your homepage (Cloudinary and Sentry), adding 114 KiB and 0 ms of main-thread time.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RUNNER, RUN THE WORLD Identify the races corresponding to y…”.

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

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

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

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

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

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

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

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

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is 77 characters, so Google will cut it off around 60: “🏃 Calendar of races: trails, half marathons, marathons, walks... | Finishers”.

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

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 111 pages on finishers.com and 2 external pages.

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.

There is no /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.

/en/events, /contact and /en/contact have no <title>, so Google invents the link text in results.

/en/events, /en/destinations, /en/tags, /en/activities, /en/c and /en/blog and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /activities/road-running, whose canonical is /disciplines/course-a-pied. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en/events, /contact and /en/contact have no <h1> headline, so visitors and search engines get no clear main topic.

/contact and /en/contact 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.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://finishers.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://www.finishers.com/organizer.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 22 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 785 words of visible text.

DMARC is set to p=none, so mail pretending to be finishers.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.

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