Website review, no card needed

aarsleff.com logo

aarsleff.com website review

Visit site (opens in a new tab)Reviewed 19 October 202654 issues · 93 checks

This review found 54 issues worth fixing on aarsleff.com, 19 of them high impact, across 93 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.3 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.7 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.5 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
145 ms103 msMay 2Oct 17114 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026126 ms
May 9, 2026127 ms
May 16, 2026133 ms
May 23, 2026140 ms
May 30, 2026128 ms
Jun 6, 2026129 ms
Jun 13, 2026126 ms
Jun 20, 2026121 ms
Jun 27, 2026122 ms
Jul 4, 2026121 ms
Jul 11, 2026113 ms
Jul 18, 2026112 ms
Jul 25, 2026108 ms
Aug 1, 2026113 ms
Aug 8, 2026118 ms
Aug 15, 2026128 ms
Aug 22, 2026129 ms
Aug 29, 2026134 ms
Sep 5, 2026135 ms
Sep 12, 2026137 ms
Sep 19, 2026125 ms
Sep 26, 2026120 ms
Oct 3, 2026118 ms
Oct 10, 2026114 ms
Oct 17, 2026114 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 aarsleff.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aarsleff.com at 0.7 s0.7 s
  2. aarsleff.com at 1.4 s1.4 s
  3. aarsleff.com at 2.1 s2.1 s
  4. aarsleff.com at 2.8 s2.8 s
  5. aarsleff.com at 3.5 s3.5 s
  6. aarsleff.com at 4.2 s4.2 s
  7. aarsleff.com at 4.9 s4.9 s
  8. aarsleff.com at 5.6 s5.6 s

Speed

11 to fix36
  • Improve image delivery

    4.3 s · 981 KiB

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

  • Reduce unused JavaScript

    2.9 s · 533 KiB

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

  • Use efficient cache lifetimes

    2.0 s · 373 KiB

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

  • Font display

    1.9 s

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (raffle.ai, cadesignform.dk and Google Tag Manager and others), adding 1.3 MB and 742 ms of main-thread time.

  • Render-blocking requests

    800 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • raffle.ai adds 368 ms

    368 ms

    raffle.ai costs a phone 368 ms of main-thread work and 409 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.7 s

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

  • 2,558 HTML elements

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

  • Vimeo adds 65 ms

    65 ms

    Vimeo costs a phone 65 ms of main-thread work and 561 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.

  • Reduce unused CSS

    150 ms · 22 KiB

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

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

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

    2 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • Largest Contentful Paint: 18.9 s

    18.9 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

  • Cumulative Layout Shift: 0.42

    0.42

    The layout shifts by 0.42 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 457 ms

    457 ms

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 4 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user INP: 120 ms

    120 ms

    Real visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

Images and page weight

4 to fix53
  • 1 image over 500 KB

    oc-animationer weighs 504 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.8 MB in 64 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 64 requests on a phone: images 2.4 MB (20), scripts 1.2 MB (21) and fonts 73 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.5 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.

  • 3 images below the first screen load straight away

    3 images further down the page (451 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.06 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 7485
  • Elements must only use permitted ARIA attributes (4 elements)

    Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 9 images without alt text

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

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 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.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7574
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

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

  • 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 XML sitemap

    No XML sitemap at https://www.aarsleff.com/sitemap.xml, so Google discovers your pages only by following links.

  • 11 links with vague text

    11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

  • 252 internal links, 11 external

    The homepage links to 252 pages on aarsleff.com and 11 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Infrastructure and construction for modern societies”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Per Aarsleff A/S - General infrastructure contractor”.

  • robots.txt in place

    robots.txt is in place.

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://www.aarsleff.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 (1,113 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.aarsleff.com/aarsleff-world/the-harbour/shell-structures-niveau-3, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://www.aarsleff.com/aarsleff-world, https://www.aarsleff.com/references, https://www.aarsleff.com/contact, https://www.aarsleff.com/aarsleff-world/the-harbour, https://www.aarsleff.com/aarsleff-world/the-harbour/construction-pits-niveau-3 and https://www.aarsleff.com/aarsleff-world/the-harbour/sheet-pile-walls-uk-niveau-3 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.aarsleff.com/aarsleff-world and https://www.aarsleff.com/contact have 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 159 found) and read each the way a search engine does.

4 checks passed
  • 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

4 to fixGoogle 5483
  • 199 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://yui.customizer.cadesignform.dk/3.18.1/cssreset/cssreset-min.css' from origin 'http…”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 1,111 words of copy

    The homepage carries about 1,111 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” and “Conference call”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Conference call”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 2 of them by other companies (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.

  • 14 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics

Company

Employees
8,782
Founded
1961
Headquarters
Aarhus

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on aarsleff.com, including 22 speed issues, 6 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