xtrainingequipment.com website review

3 images could be 355 KiB 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.

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

Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Affirm, Clarity and Key CDN and others), adding 594 KiB and 398 ms of main-thread time.

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

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

About 130 KiB of JavaScript is downloaded but never used on this page.

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

About 32 KiB of CSS is downloaded but never applied on this page.

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 could be saved by minifying CSS.

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 268 requests on a phone: images 2.3 MB (55), other files 851 KiB (132) and scripts 761 KiB (64). Under 2 MB keeps phones on slow connections fast.

Crumb_Bumper_14.jpg weighs 1.8 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Evo-Plate-Black_fa4460fa-8515-4509-bf21-6aadfdb8ed5c.jpg at 1,440 px wide, shown at 390 px. Resized copies would save about 178 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 59 pages on xtrainingequipment.com and 3 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 https://www.againfaster.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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17525800&Ver=2&mid=94bcc112-257b-41b7-9a6d-d3e2e5bc11f7&bo=1&sid=c8a4d840dc0011f1bb2ff9e650a44ee8&vid=c8a4e310dc0011f1a613a3fbc19e97b9&vids=1&msclkid=N&pi=918639831&lg.

2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

The homepage carries about 811 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.

Opening the homepage sets 20 cookies, 1 of them by other companies (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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.