trainwell.net website review

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

website-files.com costs a phone 1.7 s of main-thread work and 10.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (website-files.com, frontapp.com and Google Tag Manager and others), adding 13.0 MB and 4.0 s of main-thread time.

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

frontapp.com costs a phone 906 ms of main-thread work and 1.5 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.

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

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

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

Facebook costs a phone 411 ms of main-thread work and 222 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.

Klaviyo costs a phone 225 ms of main-thread work and 323 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

1 image could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

4 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get a personalized training plan, 1-on-1 coaching from a re…”.

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

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

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

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

7 images 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 114 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.3 MB in 142 requests on a phone: media 9.2 MB (8), scripts 2.1 MB (54) and fonts 1.2 MB (11). Under 2 MB keeps phones on slow connections fast.

690a3ac2a04f301743fe0841_human_powered_tigheter_crop.svg 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).

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

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

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

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

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

There are 3 <h1> headlines (“Personal Training You'll Actually Stick With”, “Our trainers specialize in..” and “Everyone deserves an incredible trainer.”). One clear main headline is easier for people and search engines.

Structured data found (FAQPage, Organization, Service and SoftwareApplication) but with 1 problem, for example “Service: no offers (price) block”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 33 pages on trainwell.net and 21 external pages.

https://www.trainwell.net/contact and https://www.trainwell.net/partnerships use the same meta description. A description written for each page earns more clicks.

https://www.trainwell.net/copilot has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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 1,471 words of visible text.

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

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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.