Website review, no card needed

akselos.com logo

akselos.com website review

Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 83 checks

This review found 34 issues worth fixing on akselos.com, 11 of them high impact, across 83 checks. The most urgent: 1 image over 500 KB. 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

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.8 sApr 25Oct 32.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.9 s
May 2, 20261.9 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Sep 5, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
151 ms93 msApr 25Jun 27100 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026114 ms
May 2, 2026115 ms
May 9, 2026100 ms
Jun 6, 2026143 ms
Jun 13, 2026144 ms
Jun 27, 2026100 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

Full-page screenshot of akselos.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix56
  • Reduce unused JavaScript

    1.8 s · 277 KiB

    About 277 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Improve image delivery

    1.2 s · 750 KiB

    6 images could be 750 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Render-blocking requests

    1.8 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Mobile performance score: 56

    56/100

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

  • Use efficient cache lifetimes

    650 ms · 168 KiB

    14 files are served with short cache lifetimes, so returning visitors download them again (168 KiB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and cdn-cookieyes.com and others), adding 812 KiB and 602 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 62 KiB

    About 62 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.

  • Google Tag Manager adds 375 ms

    375 ms

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

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 935 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 1,591 HTML elements

    The page has 1,591 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    250 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 56. 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.

  • 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: 38 ms

    38 ms

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

Core Web Vitals

6 to fix62
  • Largest Contentful Paint: 16.6 s

    16.6 s

    Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a-senior-male-engineer-in-a-white-helmet-and-safet”.

  • Time to Interactive: 16.9 s

    16.9 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Largest content (LCP) got 34% slower for real visitors

    +34%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 229 ms

    229 ms

    Scripts block taps and scrolling for 229 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 114 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 checks passed
  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

4 to fix35
  • 1 image over 500 KB

    DCU-Coke-Drum-Dashboard-4.gif weighs 73.5 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 14.6 MB in 96 requests

    14.6 MB

    Your homepage downloads 14.6 MB in 96 requests on a phone: media 12.3 MB (2), images 1.1 MB (16) and scripts 908 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (74.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.

  • 1 image far larger than shown

    81 KiB

    1 image is downloaded at several times the size a phone draws it, for example a-senior-male-engineer-in-a-white-helmet-and-safet.jpg at 1,999 px wide, shown at 390 px. Resized copies would save about 81 KiB.

  • About 4.1 g of CO₂ per visit

    4.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.13 g of CO₂e: 495.1 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

7 to fixGoogle 9591
  • 2 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate 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.

  • 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), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8595
  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

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

  • 97 internal links, 12 external

    The homepage links to 97 pages on akselos.com and 12 external pages.

8 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Akselos provides Structural Performance Management software. We optimise designs, run predictive maintenance & safely e…”.

  • One H1 headline

    Your main headline reads: “RUN YOUR ASSETS SAFER, HARDER, AND LONGER”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Akselos - Structural Performance Management Software”.

  • Canonical URL set

    The canonical URL is https://akselos.com/.

  • Structured data in place

    Structured data found: Article, BreadcrumbList, ImageObject, Organization and Person.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://akselos.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

3 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 (1,261 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://akselos.com/llms.txt (4 KiB, 11 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://akselos.com/contact-us and https://akselos.com/request-a-demo use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://akselos.com/request-a-demo 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 22 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

2 to fixGoogle 9287
  • 3 small tap targets

    3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 886 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: “REQUEST A DEMO”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “CONTACT US”, “REQUEST A DEMO” and “DOWNLOAD THE FULL VERDANTIX REPORT”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • 30 other companies contacted

    Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

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 akselos.com, 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
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 34 issues on akselos.com, including 16 speed issues, 2 SEO issues and 1 conversion gap. 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