Website review, no card needed

al-bank.dk logo

al-bank.dk website review

Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 75 checks

This review found 26 issues worth fixing on al-bank.dk, 8 of them high impact, across 75 checks. The most urgent: 1 button without a name. 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 al-bank.dk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix75
  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    750 ms

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

  • 6 third-party services on the page

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

  • Google Tag Manager adds 549 ms

    549 ms

    Google Tag Manager costs a phone 549 ms of main-thread work and 523 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 JavaScript

    150 ms · 309 KiB

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

  • imgix adds 0 ms

    0 ms

    imgix costs a phone 0 ms of main-thread work and 575 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 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 26 KiB

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

  • Improve image delivery

    147 KiB

    5 images could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    122 KiB

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    15 KiB

    Polyfills for old browsers add 15 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.

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

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

  • Server response: 132 ms

    132 ms

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

Core Web Vitals

5 to fix77
  • Time to Interactive: 10.6 s

    10.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Familie på stranden”.

  • Total Blocking Time: 323 ms

    323 ms

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

  • Speed Index: 3.4 s

    3.4 s

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

  • 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

    0

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

Images and page weight

1 to fix98
  • An image on the first screen is lazy-loaded

    billede_knaek-koden.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 57.7 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: 1.7 MB in 95 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 95 requests on a phone: scripts 926 KiB (53), images 597 KiB (24) and fonts 91 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 9692
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious 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.

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

  • 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 18 images 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 6983
  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 132 internal links, 22 external

    The homepage links to 132 pages on al-bank.dk and 22 external pages.

7 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Som kunde i Arbejdernes Landsbank får du rådgivning baseret på ansvarlighed, nærvær og enkelthed. Bliv kunde i en bank …”.

  • One H1 headline

    Your main headline reads: “Store beslutninger er lettere sammen”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Arbejdernes Landsbank Privat | En personlig og ansvarlig bank”.

  • Canonical URL set

    The canonical URL is https://www.al-bank.dk/privat.

  • Structured data in place

    Structured data found: ItemList and Organization.

  • 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.al-bank.dk/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.al-bank.dk/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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (948 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 3 linked pages hidden from search

    https://www.al-bank.dk/erhverv, https://www.al-bank.dk/foreninger and https://www.al-bank.dk/private-banking are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page with very little text

    https://www.al-bank.dk/en/private 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 115 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “raffle Search: no instance found”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix40
  • 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.

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

    The homepage carries about 739 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

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

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 al-bank.dk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Azure

Company

Employees
1,323
Founded
1919
Headquarters
Copenhagen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on al-bank.dk, including 11 speed issues, 1 SEO issue and 3 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