Website review, no card needed
aevengroup.com website review
Visit site (opens in a new tab)Reviewed 17 November 202617 issues · 74 checks
This review found 17 issues worth fixing on aevengroup.com, 4 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
92AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 856 ms |
| Jun 6, 2026 | 793 ms |
| Jun 13, 2026 | 865 ms |
| Jun 20, 2026 | 865 ms |
| Jun 27, 2026 | 838 ms |
| Jul 4, 2026 | 948 ms |
| Jul 11, 2026 | 895 ms |
| Jul 18, 2026 | 929 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 996 ms |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 936 ms |
| Oct 24, 2026 | 943 ms |
| Oct 31, 2026 | 971 ms |
| Nov 7, 2026 | 943 ms |
| Nov 14, 2026 | 949 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 82 ms |
| Jun 13, 2026 | 84 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 85 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 85 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 85 ms |
| Nov 7, 2026 | 87 ms |
| Nov 14, 2026 | 85 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Improve image delivery
72 KiB1 image could be 72 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
56 KiB5 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
1 third-party service on the page
1 third-party service load with your homepage (cookieinformation.com), adding 29 KiB and 26 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.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 31 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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 TTFB: 880 ms
880 msReal visitors wait 880 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 1.6 s
1.6 sYour largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We and our business partners use technologies, including co…”.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.6 s
1.6 sThe page is fully interactive after 1.6 s.
Images and page weight
1 image far larger than shown
55 KiB1 image is downloaded at several times the size a phone draws it, for example image_datacenter-dk_01.jpg at 800 px wide, shown at 156 px. Resized copies would save about 55 KiB.
About 0.05 g of CO₂ per visit
0.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.05 g of CO₂e: 6.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 184 KiB in 10 requests
184 KiBYour homepage downloads 184 KiB in 10 requests on a phone: images 88 KiB (2), fonts 43 KiB (1) and scripts 29 KiB (3). 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.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more 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.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
35 internal links, 5 external
The homepage links to 35 pages on aevengroup.com and 5 external pages.
6 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “We help you build and run IT that adapts, combining the reliability of local infrastructure in Denmark with the hybridi…”.
One H1 headline
Your main headline reads: “Adaptive digital infrastructure”.
Title: 47 characters
Your title is a healthy 47 characters: “Adaptive digital infrastructure | Aeven | Aeven”.
Canonical URL set
The canonical URL is https://www.aevengroup.com/.
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.aevengroup.com/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.aevengroup.com/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 (204 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://www.aevengroup.com/what-we-do, https://www.aevengroup.com/what-we-do/application-services, https://www.aevengroup.com/what-we-do/consulting-advisory, https://www.aevengroup.com/what-we-do/data-centers, https://www.aevengroup.com/what-we-do/data-ai-automation and https://www.aevengroup.com/what-we-do/digital-workplace and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.aevengroup.com/why-aeven and https://www.aevengroup.com/what-we-do have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.aevengroup.com/what-we-do has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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 15 pages that loaded have a <title>.
Best practices
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
18 of 20 tappable elements near the top are at least 24 px.
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 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 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 294 words of copy
The homepage carries about 294 words of visible text.
1 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Contact us”.
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.
1 other company contacted
Loading the homepage contacts 1 host 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 aevengroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Company
- Founded
- 2022
- Headquarters
- Ballerup
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on aevengroup.com, including 2 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.