warrior.com website review

About 608 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Optanon and cloudflarestream.com), adding 350 KiB and 245 ms of main-thread time.

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

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

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

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

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

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

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.

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 visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use of cookies or similar technologies to maintain secur…”. Most of its time is element render delay (2.5 s).

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

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

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

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

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

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

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

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

20 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

The homepage links to 31 pages on warrior.com and 6 external pages.

Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

robots.txt blocks GPTBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.warrior.com/en/products/apparel, https://www.warrior.com/en/the-alpha-pro, https://www.warrior.com/en/stories, https://www.warrior.com/en/customizer/categorie/customizer, https://www.warrior.com/en/guide/hockey-helmets-explained and https://www.warrior.com/en/guide/lacrosse-helmets-explained and 4 others use the same meta description. A description written for each page earns more clicks.

https://www.warrior.com/fr, https://www.warrior.com/en/products/hockey, https://www.warrior.com/en/products/lacrosse, https://www.warrior.com/en/products/apparel, https://www.warrior.com/en/the-alpha-pro and https://www.warrior.com/en/favorite have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.warrior.com/en/stories, https://www.warrior.com/en/favorite and https://www.warrior.com/en/product/answer-unstrung-head 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.

https://www.warrior.com/en/the-alpha-pro, https://www.warrior.com/en/guide/hockey-helmets-explained, https://www.warrior.com/en/guide/lacrosse-helmets-explained, https://www.warrior.com/en/guide/apparel-guide and https://www.warrior.com/en/product/evo-v-head-unstrung took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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: 2 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.

The homepage has only about 133 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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