aksels.com website review

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

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

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

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

Your mobile performance score is 52. 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 900 ms.

8 third-party services load with your homepage (Shopify, Klaviyo and Azure Web Services and others), adding 1.2 MB and 660 ms of main-thread time.

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

Shopify costs a phone 144 ms of main-thread work and 485 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 68 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.

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

Polyfills for old browsers add 32 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 34.0 s. Good is under 3.8 s.

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SHOP ALL Shop Now”.

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

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

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' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.4 MB in 255 requests on a phone: images 6.6 MB (23), scripts 1.6 MB (106) and other files 883 KiB (107). Under 2 MB keeps phones on slow connections fast.

Aksels_Website_HERO_390x145.svg weighs 6.1 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example Aksels_Website_HERO_390x145.svg at 1,393 px wide, shown at 390 px. Resized copies would save about 1.8 MB.

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

1 button has no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

There are 13 <h1> headlines (“Leggings”, “Women's V-Neck T-Shirt” and “Women's Triblend T-Shirt”). One clear main headline is easier for people and search engines.

The homepage links to 260 pages on aksels.com and 7 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://aksels.com/collections/shop-all-mens, https://aksels.com/collections/mens-hats, https://aksels.com/collections/shop-all-womens, https://aksels.com/collections/womens-hat, https://aksels.com/collections/shop-all-kids and https://aksels.com/collections/kids-apparel and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

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

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