walkingpad.no website review

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

8 third-party services load with your homepage (Klaviyo, loox.io and Snapchat and others), adding 642 KiB and 1.1 s of main-thread time.

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

Klaviyo costs a phone 454 ms of main-thread work and 314 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,841 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

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

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

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

Polyfills for old browsers add 28 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.

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

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

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

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

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

Your homepage downloads 5.1 MB in 225 requests on a phone: images 3.3 MB (49), scripts 817 KiB (89) and other files 694 KiB (69). Under 2 MB keeps phones on slow connections fast.

b5ce11e5-0a85-43b5-bb47-9f56807d5684.png weighs 2.0 MB. On a phone connection a single image that size takes seconds.

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 84 pages on walkingpad.no and 15 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.

https://www.treningsgiganten.no/pages/vi-ble-kopiert, https://www.treningsgiganten.no/collections/trappemaskin, https://www.treningsgiganten.no/collections/kondisjon, https://www.treningsgiganten.no/collections/all and https://www.treningsgiganten.no/collections/black-month-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.treningsgiganten.no/products/walkingpad-x14-incline and https://www.treningsgiganten.no/products/walkingpad-y16-ai-performance use the same meta description. A description written for each page earns more clicks.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

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