Website review, no card needed
abraxas.ch website review
Visit site (opens in a new tab)Reviewed 3 November 202631 issues · 75 checks
This review found 31 issues worth fixing on abraxas.ch, 12 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 999 ms |
| Jun 13, 2026 | 976 ms |
| Jun 20, 2026 | 986 ms |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 981 ms |
| Oct 17, 2026 | 981 ms |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 958 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 75 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 81 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 80 ms |
| Jun 27, 2026 | 81 ms |
| Jul 4, 2026 | 82 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 80 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 82 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 80 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 76 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 76 ms |
| Oct 24, 2026 | 78 ms |
| Oct 31, 2026 | 79 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
How it loaded on a phone
1.9 s
3.8 s
5.8 s
7.7 s
9.6 s
11.5 s
13.4 s
15.3 s
Speed
Improve image delivery
2.0 s · 985 KiB5 images could be 985 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 371 KiB11 files are served with short cache lifetimes, so returning visitors download them again (371 KiB).
Render-blocking requests
1.8 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 85 KiBAbout 85 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
450 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 872 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (Cloudflare CDN, Siteimprove and Google Fonts and others), adding 50 KiB and 55 ms of main-thread time.
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.
1 checks passed
Server response: 148 ms
148 msYour server sent the HTML in 148 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.0 s
9.0 sYour largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website verwendet essentielle Cookies, um ihren ordnu…”. Most of its time is element render delay (8.6 s).
Speed Index: 15.2 s
15.2 sVisually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.1 s
9.1 sThe page becomes fully interactive after 9.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.17
0.17The layout shifts by 0.17 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 75 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 339 ms
339 msReal visitors wait 339 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
4 images in older formats
4 images (397 KiB) 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 below the first screen load straight away
1 image further down the page (206 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.7 MB in 36 requests
1.7 MBYour homepage downloads 1.7 MB in 36 requests on a phone: images 1.2 MB (8), scripts 245 KiB (9) and stylesheets 95 KiB (5). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA progressbar nodes must have an accessible name (1 element)
ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Für die digitale Schweiz. Mit Sicherheit.”, “Setzen Sie auf Sicherheit für Ihre digitale Zukun…” and “Deine Karriere beginnt hier.”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
118 internal links, 7 external
The homepage links to 118 pages on abraxas.ch and 7 external pages.
5 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Abraxas ist die führende Anbieterin innovativer ICT-Lösungen für Behörden in der Schweiz: Steuern, Polizei, Bund, Kanto…”.
Title: 65 characters
Your title is a healthy 65 characters: “Für die digitale Schweiz. Mit Sicherheit. | Abraxas Informatik AG”.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.abraxas.ch/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.abraxas.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 (484 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://www.abraxas.ch/de/loesungen, https://www.abraxas.ch/de/support and https://www.abraxas.ch/de/loesungen/kompetenzbereiche are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://www.abraxas.ch/de/loesungen, https://www.abraxas.ch/de/referenzen, https://www.abraxas.ch/de/suche and https://www.abraxas.ch/de/loesungen/kompetenzbereiche have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.abraxas.ch/de/suche has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
26 small tap targets
26 of 115 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”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 511 words of copy
The homepage carries about 511 words of visible text.
1 checks passed
Analytics in place
Analytics detected: LinkedIn Insight.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
5 other companies contacted
Loading the homepage contacts 5 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 abraxas.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Abxnet
Company
- Founded
- 1998
- 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 31 issues on abraxas.ch, including 12 speed issues, 3 SEO issues and 4 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.