Website review, no card needed

swissvax.ch logo

swissvax.ch website review

Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 82 checks

This review found 29 issues worth fixing on swissvax.ch, 7 of them high impact, across 82 checks. The most urgent: page weight: 4.3 MB in 331 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.6 s797 msMay 16Oct 31893 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 2026980 ms
Aug 8, 2026961 ms
Aug 15, 2026961 ms
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 2026978 ms
Sep 12, 2026993 ms
Sep 19, 2026978 ms
Sep 26, 2026968 ms
Oct 3, 2026970 ms
Oct 10, 2026973 ms
Oct 17, 20261.0 s
Oct 24, 2026968 ms
Oct 31, 2026893 ms
Real-visitor tap response (INP)75th percentile, phones
186 ms110 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026121 ms
May 23, 2026120 ms
May 30, 2026120 ms
Jun 6, 2026119 ms
Jun 13, 2026121 ms
Jun 20, 2026135 ms
Jun 27, 2026142 ms
Jul 4, 2026143 ms
Jul 11, 2026138 ms
Jul 18, 2026136 ms
Jul 25, 2026128 ms
Aug 1, 2026128 ms
Aug 8, 2026136 ms
Aug 15, 2026137 ms
Aug 22, 2026145 ms
Aug 29, 2026146 ms
Sep 5, 2026146 ms
Sep 12, 2026154 ms
Sep 19, 2026162 ms
Sep 26, 2026169 ms
Oct 3, 2026177 ms
Oct 10, 2026170 ms
Oct 17, 2026162 ms
Oct 24, 2026156 ms
Oct 31, 2026154 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.ch (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swissvax.ch at 0.4 s0.4 s
  2. swissvax.ch at 0.8 s0.8 s
  3. swissvax.ch at 1.1 s1.1 s
  4. swissvax.ch at 1.5 s1.5 s
  5. swissvax.ch at 1.9 s1.9 s
  6. swissvax.ch at 2.3 s2.3 s
  7. swissvax.ch at 2.6 s2.6 s
  8. swissvax.ch at 3.0 s3.0 s

Speed

8 to fix68
  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 1.7 MB and 906 ms of main-thread time.

  • Mobile performance score: 68

    68/100

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

  • Google Tag Manager adds 360 ms

    360 ms

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

  • Main-thread work: 3.7 s

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

  • Use efficient cache lifetimes

    286 KiB

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

  • Shopify adds 197 ms

    197 ms

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

  • 2,126 HTML elements

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

  • 12 long tasks on the main thread

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

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    27 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • 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: 16 ms

    16 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 22.4 s

    22.4 s

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

  • 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 29% slower for real visitors

    +29%

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

  • Total Blocking Time: 582 ms

    582 ms

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

  • Speed Index: 4.7 s

    4.7 s

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user INP: 160 ms

    160 ms

    Real visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 474 ms

    474 ms

    Real visitors wait 474 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 38% faster for real visitors

    -38%

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

  • First Contentful Paint: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 331 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 331 requests on a phone: scripts 2.0 MB (76), other files 1.3 MB (213) and images 504 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.0 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

6 to fixGoogle 8592
  • Unlabelled dropdowns

    2 dropdowns have no label.

  • 6 text elements with low contrast

    6 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 (8 elements)

    All page content should be contained by landmarks: 8 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.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

3 to fixGoogle 8586
  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Swissvax – Premium car care, polishes & car waxes hand-made since 1930 – SWISSVAX AG”.

  • Meta description is long (170 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 161 internal links, 37 external

    The homepage links to 161 pages on swissvax.ch and 37 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Premium Car Wax & Detailing Products”.

  • Canonical URL set

    The canonical URL is https://swissvax.ch/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.ch/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.

3 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,688 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://swissvax.ch/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 1,378 words of copy

    The homepage carries about 1,378 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ALL PRODUCTS”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Shop All Products” and “Accessories"Nude" Flyer $12.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
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Multifeeds · Forms · Gdpr Backpack · 61f56232 · Upcart

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on swissvax.ch, including 13 speed issues, 3 SEO issues and 2 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