Website review, no card needed
aagon.com website review
Visit site (opens in a new tab)Reviewed 25 October 202631 issues · 102 checks
This review found 31 issues worth fixing on aagon.com, 10 of them high impact, across 102 checks. The most urgent: 5 text elements with low contrast. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 95 ms |
| May 9, 2026 | 101 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 103 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 90 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 81 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 338 ms |
| Sep 19, 2026 | 363 ms |
| Sep 26, 2026 | 363 ms |
| Oct 3, 2026 | 363 ms |
| Oct 10, 2026 | 85 ms |
| Oct 17, 2026 | 81 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
Mobile performance score: 80
80/100Your mobile performance score is 80 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 445 KiBAbout 445 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (hsappstatic.net, consentmanager.net and Hubspot), adding 1.1 MB and 494 ms of main-thread time.
Use efficient cache lifetimes
300 ms · 150 KiB9 files are served with short cache lifetimes, so returning visitors download them again (150 KiB).
hsappstatic.net adds 301 ms
301 mshsappstatic.net costs a phone 301 ms of main-thread work and 897 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 274 ms. During a long task the page ignores taps.
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
33 KiB1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 758 ms of it running JavaScript. That is comfortably low.
Server response: 271 ms
271 msYour server sent the HTML in 271 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 10.6 s
10.6 sThe page becomes fully interactive after 10.6 s. Good is under 3.8 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “On this website we use cookies and similar functions to pro…”. Most of its time is element render delay (2.2 s).
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
11 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 77 ms
77 msReal visitors wait 77 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 791 ms
791 msReal visitors wait 791 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 95 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 192 ms
192 msScripts block the page for only 192 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.5 MB in 58 requests
1.5 MBYour homepage downloads 1.5 MB in 58 requests on a phone: scripts 1.0 MB (26), fonts 228 KiB (7) and images 102 KiB (15). That is a lean page.
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 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (102 elements)
All page content should be contained by landmarks: 102 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
8 links without text
8 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
43 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: 43 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (25 characters)
Your title is only 25 characters: “UEM Lösung der Aagon GmbH”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
130 internal links, 9 external
The homepage links to 130 pages on aagon.com and 9 external pages.
5 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Mit Unified Endpoint Management (UEM) sorgen Sie für ein zentrales Management von Geräten Ihrer IT-Umgebung, sogenannte…”.
Canonical URL set
The canonical URL is https://www.aagon.com/.
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.aagon.com/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (823 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (8 KiB, 79 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
/ihre-herausforderungen/it-sicherheit-erhoehen-und-compliance-sicherstellen/zertifizierte-datenloeschung-fuer-endgeraete has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
/en 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 88 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Certificate expires in 3 days
Your certificate from DigiCert Inc · RapidSSL TLS RSA CA G1 expires in 3 days. If it doesn't renew automatically, visitors get a security warning.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
5 checks passed
Served over HTTPS
The homepage is served over HTTPS (aagon.com).
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://aagon.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 45 links work
All 45 links checked from your homepage (40 internal, 5 external) answered without errors.
Domain and trust
No CAA record
aagon.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
aagon.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 30 years old
30 yearsaagon.com was registered in Oct 1996 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.
Registered until Oct 2030
aagon.com is registered until Oct 2030.
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.
Thin social proof
Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 624 words of copy
The homepage carries about 624 words of visible text.
2 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: 2 phone links and 2 email links.
Email authentication
Email authentication score: 90/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:194.25.32.251 ip4:37.208.111.218 ip4:37.208.111.222 ip4:37.208.111.219 ip4:194.25.32.204 include:_spf1.aagon…”.
DKIM signing found
A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
Upkeep, stack and company
- It runs WordPress 3.7.1; the current release is 7.1.3.
- 1 plugin is behind its latest release.friendly-captcha 0.1.25 → 1.19.0
Stack
- CMS
- WordPress 3.7.1
- Framework
- jQuery
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 aagon.com, including 9 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.