bugasaltswiss.ch website review

About 497 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and weglot.com and others), adding 7.8 MB and 753 ms of main-thread time.

Your mobile performance score is 64. 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 850 ms.

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

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Klaviyo costs a phone 89 ms of main-thread work and 309 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 36 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.

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

10 KiB could be saved by minifying CSS.

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.

Your largest element takes 10.2 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 29.4 s (Speed Index). Good is under 3.4 s.

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

15 images 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' tap response (inp) went from 101 ms to 116 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 1.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 10.2 MB in 412 requests on a phone: media 6.5 MB (3), scripts 1.5 MB (106) and other files 1.2 MB (232). Under 2 MB keeps phones on slow connections fast.

ezgif-4-122f03c415_360x.gif weighs 965 KiB. On a phone connection a single image that size takes seconds.

1 image (965 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.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 22 characters: “Bug-A-Salt Switzerland”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 28 pages on bugasaltswiss.ch and 9 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://www.bugasaltswiss.ch/en/pages/meet-bug-a-salt-3-0, https://www.bugasaltswiss.ch/en/collections/3-0-singles, https://www.bugasaltswiss.ch/en/pages/wholesale-enquiries and https://www.bugasaltswiss.ch/en/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bugasaltswiss.ch/en/collections/3-0-singles/products/bug-a-salt-3-0-advanced-combat-fibre-optic, whose canonical is https://www.bugasaltswiss.ch/en/products/bug-a-salt-3-0-advanced-combat-fibre-optic. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.bugasaltswiss.ch/en/collections/3-0, https://www.bugasaltswiss.ch/en/collections/3-0-singles and https://www.bugasaltswiss.ch/en/pages/wholesale-enquiries have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.bugasaltswiss.ch/en/pages/wholesale-enquiries has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136011762&tm=gtm002&Ver=2&mid=a7cdbf58-6b10-4d15-8fcf-9948c674ab00&bo=1&sid=e8fb1f80df2611f1bc2205db6b10bc28&vid=e8fb1460df2611f1b154cbdffed2f1b3&vids=1&msclkid=N&pi=9.

4 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

1 image is served at too low a resolution for sharp phone screens.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 20 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.