varoninc.se website review

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

8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Shopify and others), adding 2.9 MB and 1.2 s of main-thread time.

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

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

cloudfront.net costs a phone 231 ms of main-thread work and 413 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,926 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

xcottons.com costs a phone 96 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.

azurefd.net costs a phone 59 ms of main-thread work and 330 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 78 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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.9 MB in 415 requests on a phone: scripts 2.7 MB (104), images 1.6 MB (28) and other files 1.3 MB (246). Under 2 MB keeps phones on slow connections fast.

SE9_banner1080-1080_3.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images are downloaded at several times the size a phone draws them, for example 1600-1600-9_55528c4e-270f-4593-a96a-faeb4e0151c9.webp at 1,200 px wide, shown at 330 px. Resized copies would save about 243 KiB.

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

7 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 69 characters, so Google will cut it off around 60: “Högkvalitativ professionell syrgaskoncentrator från VARON. – VARON-SE”.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 149 pages on varoninc.se and 20 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://varoninc.se/collections/syrgaskoncentrator, https://varoninc.se/collections/barbar-syrgaskoncentrator, https://varoninc.se/collections/latta-syrgaskoncentrator and https://varoninc.se/collections/syrgaskoncentrator-i-hemmet have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

2 images are served at too low a resolution for sharp phone screens.

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.

Social proof on the homepage: 123 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 1,621 words of visible text.

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