horze.se website review

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

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

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

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

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

8 third-party services load with your homepage (Usercentrics CMP, Shopify and fraud0.com and others), adding 1.1 MB and 668 ms of main-thread time.

Usercentrics CMP costs a phone 457 ms of main-thread work and 188 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.

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

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

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

149 KiB could be saved by minifying JavaScript.

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

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

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 20.6 s. Good is under 3.8 s.

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

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

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

Real visitors wait 342 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your homepage downloads 17.5 MB in 411 requests on a phone: media 13.7 MB (1), scripts 2.0 MB (240) and images 1.2 MB (90). Under 2 MB keeps phones on slow connections fast.

MC_blackweek1_mobile_kw452.jpg 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).

1 image (96 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 4.96 g of CO₂e: 594.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA attributes must conform to valid values: 4 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (6 elements).

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url is not an absolute URL ("https://horze.se/collections")”.

The homepage links to 851 pages on horze.se and 8 external pages.

https://horze.se/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://horze.se/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://horze.se/pages/horze-club, https://horze.se/pages/kontakta and https://horze.se/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://horze.se/pages/horze-club, https://horze.se/pages/kontakta, https://horze.se/pages/instruktion-for-returregistrering, https://horze.se/customer_authentication/redirect, https://horze.se/collections/new-in and https://horze.se/collections/ryttare and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://horze.se/collections/jodhpurbyxor-dam, https://horze.se/collections/dam-regn-ridbyxor and https://horze.se/collections/dam-western-jeans took over 3 s to send their HTML from our server.

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

321 of 656 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Klaviyo (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies, 2 of them by other companies (measured from a US location before any click).

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