tanrevel.com website review

14 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.

Optimizely costs a phone 1.1 s of main-thread work and 515 KiB 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.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

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

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

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

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

52 KiB could be saved by minifying JavaScript.

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

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Glow Booster Serum & Gradual Tanning Lotion hero image”.

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

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

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

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 266 requests on a phone: scripts 2.0 MB (80), media 1.4 MB (1) and images 1.1 MB (51). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example startskarm_f7e3941c-3dad-48c3-b20a-a800adef31a1.jpg at 1,600 px wide, shown at 342 px. Resized copies would save about 121 KiB.

1 image further down the page (80 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

[role]s are not contained by their required parent element (5 elements).

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

Some list items are not inside a list.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://tanrevel.se)”.

The homepage links to 161 pages on tanrevel.com and 3 external pages.

https://tanrevel.com/collections/all-products, https://tanrevel.com/collections/bestsellers, https://tanrevel.com/collections/devices and https://tanrevel.com/pages/undertonstest have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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.

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.

The homepage carries about 718 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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