Website review, no card needed

aksos.nl logo

aksos.nl website review

Visit site (opens in a new tab)Reviewed 18 October 202629 issues · 75 checks

This review found 29 issues worth fixing on aksos.nl, 11 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.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of aksos.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix57
  • Improve image delivery

    9.9 s · 5.9 MB

    20 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.9 s faster on a phone.

  • Use efficient cache lifetimes

    800 ms · 4.9 MB

    44 files are served with short cache lifetimes, so returning visitors download them again (4.9 MB).

  • Reduce unused JavaScript

    900 ms · 167 KiB

    About 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 175 ms

    175 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and diffuse.tools and others), adding 441 KiB and 196 ms of main-thread time.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.

  • Document request latency

    130 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 190 ms of it running JavaScript. That is comfortably low.

  • Server response: 494 ms

    494 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 17.0 s

    17.0 s

    Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “AKSOS 2026 1”.

  • Time to Interactive: 17.0 s

    17.0 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

    The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

  • Speed Index: 8.3 s

    8.3 s

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.067

    0.067

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

  • Total Blocking Time: 48 ms

    48 ms

    Scripts block the page for only 48 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 8.9 MB in 61 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 61 requests on a phone: images 8.1 MB (43), scripts 404 KiB (7) and HTML 194 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

  • 24 images far larger than shown

    5.0 MB

    24 images are downloaded at several times the size a phone draws them, for example img_2945.jpg at 1,920 px wide, shown at 350 px. Resized copies would save about 5.0 MB.

  • 28 images in older formats

    28 images (7.6 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.

  • 28 images below the first screen load straight away

    28 images further down the page (4.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.53 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.53 g of CO₂e: 303.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 7589
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 13 text elements with low contrast

    13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 15 images without alt text

    15 images have no alt text, which hurts accessibility and image search.

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

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 32 automated accessibility rules passed

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

4 to fixGoogle 9284
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (334 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 83 internal links, 19 external

    The homepage links to 83 pages on aksos.nl and 19 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Sterk in KAPITALEN”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “AKSOS Accountants | Sterk in kapitalen | Aksos”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://aksos.nl/sitemap.xml.

AI search readiness

1 to fix88
  • 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://aksos.nl/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 (785 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    11 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 fix86
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 830 words of copy

    The homepage carries about 830 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact opnemen” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Build with love. Powered by VrijdagOnline and Umbraco.
Framework
Tailwind CSS
Analytics
Google Tag Manager

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 aksos.nl, including 11 speed issues, 4 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