bastsauna.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

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

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

YouTube costs a phone 674 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.

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

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

Shopify costs a phone 448 ms of main-thread work and 581 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 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

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

azurefd.net costs a phone 86 ms of main-thread work and 329 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 184 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.

1 image could be 26 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 KiB JavaScript is shipped twice across bundles.

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.

5 KiB could be saved by minifying JavaScript.

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.

Real visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.88 (75th percentile). Good is under 0.1.

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

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

The layout shifts by 0.896 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 354 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-11-07, real Chrome visitors' tap response (inp) went from 170 ms to 263 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.7 MB in 470 requests on a phone: scripts 2.8 MB (190), images 1.4 MB (72) and other files 887 KiB (159). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

11 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found ((untyped), Organization and WebSite) but with 4 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

6 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 295 pages on bastsauna.com and 13 external pages.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Large scripts ship without source maps.

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.

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: “10.000+ Satisfied customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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