Website review, no card needed
asga.ch website review
Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 85 checks
This review found 40 issues worth fixing on asga.ch, 15 of them high impact, across 85 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 7.7 s |
| May 9, 2026 | 7.7 s |
| May 16, 2026 | 7.7 s |
| May 23, 2026 | 7.7 s |
| May 30, 2026 | 7.7 s |
| Jun 6, 2026 | 7.7 s |
| Jun 13, 2026 | 7.7 s |
| Jun 20, 2026 | 7.7 s |
| Jun 27, 2026 | 7.8 s |
| Jul 4, 2026 | 7.5 s |
| Jul 11, 2026 | 7.1 s |
| Jul 18, 2026 | 6.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 139 ms |
| May 9, 2026 | 150 ms |
| May 16, 2026 | 152 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 102 ms |
| Oct 17, 2026 | 102 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
Speed
Render-blocking requests
3.5 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Font display
2.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.3 s).
Reduce unused JavaScript
600 ms · 667 KiBAbout 667 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
900 ms · 236 KiBAbout 236 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 84). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
941 KiB3 files are served with short cache lifetimes, so returning visitors download them again (941 KiB).
Improve image delivery
883 KiB7 images could be 883 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,547 HTML elements
The page has 1,547 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
mailxpert.ch adds 47 ms
47 msmailxpert.ch costs a phone 47 ms of main-thread work and 946 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.
4 third-party services on the page
4 third-party services load with your homepage (mailxpert.ch, thechatmaster.com and Google Fonts and others), adding 991 KiB and 64 ms of main-thread time.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
1 checks passed
Server response: 120 ms
120 msYour server sent the HTML in 120 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.2 s
3.2 sReal visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 11.9 s
11.9 sYour largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “glückliches altes Ehepaar”.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
6 checks passed
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 139 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 58% faster for real visitors
-58%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 7.7 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Total Blocking Time: 42 ms
42 msScripts block the page for only 42 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 124 requests
3.4 MBYour homepage downloads 3.4 MB in 124 requests on a phone: scripts 1.5 MB (49), images 1.2 MB (15) and fonts 361 KiB (11). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (1.0 MB) are 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 far larger than shown
377 KiB1 image is downloaded at several times the size a phone draws it, for example shutterstock_1785276425-scaled.jpg at 2,560 px wide, shown at 403 px. Resized copies would save about 377 KiB.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
237 internal links, 7 external
The homepage links to 237 pages on asga.ch and 7 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Die Asga Pensionskasse ist die größte unabhängige Gemeinschafts-Vorsorgeeinrichtungen der Schweiz, spezialisiert auf KM…”.
One H1 headline
Your main headline reads: “Home”.
Title: 46 characters
Your title is a healthy 46 characters: “Asga Pensionskasse - Weil gemeinsam besser ist”.
Canonical URL set
The canonical URL is https://www.asga.ch/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://www.asga.ch/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://www.asga.ch/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 (715 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages point its canonical at the homepage
https://www.asga.ch/en, https://www.asga.ch/fr and https://www.asga.ch/it declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://www.asga.ch/offertanfrage is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
https://www.asga.ch/en, https://www.asga.ch/fr and https://www.asga.ch/it all use the title “Home - Asga Pensionskasse”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://www.asga.ch/offertanfrage, https://www.asga.ch/news, https://www.asga.ch/en, https://www.asga.ch/fr and https://www.asga.ch/it have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 560 words of copy
The homepage carries about 560 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 asga.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
Company
- Employees
- 84
- Founded
- 1962
- Headquarters
- St. Gallen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on asga.ch, including 18 speed issues, 1 SEO issue and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.