jmband.is website review

hcaptcha.com costs a phone 1.0 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (hcaptcha.com, zakeke.com and Shopify and others), adding 3.0 MB and 1.9 s of main-thread time.

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

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

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

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

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

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

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

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

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

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

15 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi og våre partnere, inkludert Shopify, bruker informasjons…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.9 MB in 596 requests on a phone: scripts 2.4 MB (234), other files 1.5 MB (271) and images 1.1 MB (26). Under 2 MB keeps phones on slow connections fast.

d427297a-f449-49d7-974a-b33716e67627.png weighs 803 KiB. On a phone connection a single image that size takes seconds.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Some list items are not inside a list.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “JM Band | +5.500 sérprentaðar vörur og afhending frá degi til dags”.

There are 2 <h1> headlines (“” and “Adgangskontroll fra JM Band®”). One clear main headline is easier for people and search engines.

The homepage links to 417 pages on jmband.is and 34 external pages.

Your homepage links to https://jmband.is/products/papir-armband-utrykt-pa-lager, which answers with an error. Visitors hit a dead end and search engines drop it.

https://jmband.is/collections/stoffarmband and https://jmband.is/collections/stoffarmband/QR+RFID+NFC use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://jmband.is/collections/stoffarmband/QR+RFID+NFC, whose canonical is https://jmband.is/collections/stoffarmband/nfc+rfid. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://jmband.is/collections/armbaand, https://jmband.is/collections/papirarmband, https://jmband.is/products/papir-armband-svart-tryk, https://jmband.is/products/papir-armband-full-farge, https://jmband.is/products/startnummer-armband and https://jmband.is/collections/stoffarmband and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

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