trooper.ch website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 3.5 MB and 1.2 s of main-thread time.

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

35 images could be 782 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Shopify costs a phone 392 ms of main-thread work and 1.4 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.

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

varify.io costs a phone 25 ms of main-thread work and 529 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.

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

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

82 KiB could be saved by minifying JavaScript.

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

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

7 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “POLICE / ARMY / SECURITY / OUTDOOR PROFESSIONELLES EQUIPMEN…”.

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

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

The layout shifts by 0.151 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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-11-07, real Chrome visitors' tap response (inp) went from 120 ms to 137 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 7.5 MB in 467 requests on a phone: images 2.9 MB (112), scripts 2.5 MB (128) and other files 1.7 MB (174). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (61 KiB) is 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.

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

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

1 text element doesn'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.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

There are 2 <h1> headlines (“” and “Outdoor-Shop, Armyshop und Polizeibedarf - Ihre Q…”). One clear main headline is easier for people and search engines.

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

The homepage links to 172 pages on trooper.ch and 12 external pages.

https://www.trooper.ch/products/p-40-all-terrain-gen-3-tactical-pants, https://www.trooper.ch/collections/taktischer-einsatz-taschenlampen, https://www.trooper.ch/collections/schutzweste-weichballistik-unterziehweste-1, https://www.trooper.ch/collections/einsatzschuhe and https://www.trooper.ch/collections/bekleidung-1 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.trooper.ch/products/p-40-all-terrain-gen-3-tactical-pants, https://www.trooper.ch/collections/taktischer-einsatz-taschenlampen, https://www.trooper.ch/collections/schutzweste-weichballistik-unterziehweste-1, https://www.trooper.ch/collections/einsatzschuhe and https://www.trooper.ch/collections/bekleidung-1 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 110 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=134624868&tm=gtm002&Ver=2&mid=e26b377e-9973-47e5-bd2a-e2a2c5e75c00&bo=1&sid=64dde360dc7d11f1ba82f759a37460fa&vid=64de26e0dc7d11f1ab8b55eb03b1b12d&vids=1&msclkid=N&gtm_.

2 errors were logged to the browser console while the page loaded, for example “Both API calls failed: TimeoutError: signal timed out”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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 2,075 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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 26 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.