Website review, no card needed

swissvax.it logo

swissvax.it website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 76 checks

This review found 33 issues worth fixing on swissvax.it, 12 of them high impact, across 76 checks. The most urgent: page weight: 5.7 MB in 399 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.1 sJun 6Sep 261.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.4 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Aug 29, 20261.3 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
378 ms154 msJun 6Sep 26348 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 2026180 ms
Jun 13, 2026188 ms
Jun 20, 2026206 ms
Jun 27, 2026222 ms
Jul 4, 2026263 ms
Jul 11, 2026273 ms
Jul 18, 2026294 ms
Sep 5, 2026352 ms
Sep 26, 2026348 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of swissvax.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swissvax.it at 1.2 s1.2 s
  2. swissvax.it at 2.3 s2.3 s
  3. swissvax.it at 3.5 s3.5 s
  4. swissvax.it at 4.7 s4.7 s
  5. swissvax.it at 5.8 s5.8 s
  6. swissvax.it at 7.0 s7.0 s
  7. swissvax.it at 8.2 s8.2 s
  8. swissvax.it at 9.3 s9.3 s

Speed

11 to fix58
  • Main-thread work: 5.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hcaptcha.com, swissvax.de and Google Tag Manager and others), adding 3.1 MB and 2.0 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • hcaptcha.com adds 821 ms

    821 ms

    hcaptcha.com costs a phone 821 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.

  • Reduce unused JavaScript

    816 KiB

    About 816 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    387 KiB

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

  • swissvax.de adds 308 ms

    308 ms

    swissvax.de costs a phone 308 ms of main-thread work and 382 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 adds 223 ms

    223 ms

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

  • Google Tag Manager adds 259 ms

    259 ms

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

  • 15 long tasks on the main thread

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

  • 2,081 HTML elements

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Improve image delivery

    71 KiB

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

  • Legacy JavaScript

    27 KiB

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

  • Reduce unused CSS

    19 KiB

    About 19 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 95 ms

    95 ms

    Your server sent the HTML in 95 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix61
  • Time to Interactive: 32.5 s

    32.5 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • Total Blocking Time: 808 ms

    808 ms

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Tap response (INP) got 90% slower for real visitors

    +90%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.011

    0.011

    The layout barely moves while loading (CLS 0.011, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.7 MB in 399 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 399 requests on a phone: scripts 2.5 MB (76), other files 1.7 MB (275) and images 639 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.61 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8893
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 9 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (32 elements)

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

  • 1 form field without a label

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

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9289
  • Title is long (97 characters)

    Your title is 97 characters, so Google will cut it off around 60: “Swissvax – Cura auto premium, polish e cera dal 1930 – SWISSVAX Logistics UG (haftungsbes…”.

  • Structured data has 1 problem

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

  • 188 internal links, 10 external

    The homepage links to 188 pages on swissvax.it and 10 external pages.

6 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Cura auto svizzera artigianale: cere Carnauba, polish, cura della pelle e prodotti detailing. Partner OEM di Rolls-Royc…”.

  • One H1 headline

    Your main headline reads: “Cera per auto premium e cura dell'auto”.

  • Canonical URL set

    The canonical URL is https://swissvax.it/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://swissvax.it/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

  • No llms.txt

    There is no https://swissvax.it/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,261 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://swissvax.it/collections/quick-detailing/oberflache_lack is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211058975&tm=gtm002&Ver=2&mid=d3b1c8d8-5413-4fea-b1fb-c34d72c12262&bo=3&sid=bf62f7c0ddc911f1bd66e3c45b65f674&vid=bf6315d0ddc911f199a367f9bbabe78b&vids=1&msclkid=N&pi=9.

  • 4 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 938 words of copy

    The homepage carries about 938 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “AccessoriBuono regalo From €50,00 Shop →”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 29 other companies contacted

    Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at swissvax.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on swissvax.it, including 16 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25