Website review, no card needed

coopbank.dk logo

coopbank.dk website review

Visit site (opens in a new tab)Reviewed 27 October 202632 issues · 82 checks

This review found 32 issues worth fixing on coopbank.dk, 9 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
1.5 s1.1 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
171 ms138 msMay 9Oct 24166 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026148 ms
May 16, 2026151 ms
May 23, 2026151 ms
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026155 ms
Jun 20, 2026155 ms
Jun 27, 2026156 ms
Jul 4, 2026158 ms
Jul 11, 2026157 ms
Jul 18, 2026151 ms
Jul 25, 2026142 ms
Aug 1, 2026142 ms
Aug 8, 2026144 ms
Aug 15, 2026154 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026162 ms
Sep 12, 2026161 ms
Sep 19, 2026159 ms
Sep 26, 2026161 ms
Oct 3, 2026162 ms
Oct 10, 2026163 ms
Oct 17, 2026167 ms
Oct 24, 2026166 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 coopbank.dk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix53
  • Reduce unused JavaScript

    1.6 s · 337 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 441 KiB

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

  • Render-blocking requests

    1.4 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

  • 3,055 HTML elements

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

  • Improve image delivery

    900 ms · 173 KiB

    1 image could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and website-files.com and others), adding 2.2 MB and 844 ms of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Google Tag Manager adds 610 ms

    610 ms

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

    300 ms · 60 KiB

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

  • website-files.com adds 57 ms

    57 ms

    website-files.com costs a phone 57 ms of main-thread work and 1.5 MB 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.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 9 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.7 s

    13.7 s

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

  • Time to Interactive: 14.0 s

    14.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Total Blocking Time: 501 ms

    501 ms

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 140 ms

    140 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 318 ms

    318 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

2 to fix75
  • Page weight: 2.2 MB in 59 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 59 requests on a phone: images 1.2 MB (15), scripts 804 KiB (29) and fonts 123 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    304 KiB

    4 images are downloaded at several times the size a phone draws them, for example 6abba0ac8dcb7ddfbc218014_6abba08fd09eada0b84d38cf_hero-bolig at 1,752 px wide, shown at 390 px. Resized copies would save about 304 KiB.

  • 1 image in older formats

    1 image (422 KiB) is 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.

  • About 0.6 g of CO₂ per visit

    0.63 g

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

8 to fixGoogle 8590
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Elements must only use permitted ARIA attributes (9 elements)

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 5 links without text

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

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 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 9289
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Coop Bank – Til hverdagen og de store beslutninger - Bliv kunde i dag”.

  • Structured data has 1 problem

    Structured data found (WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("/")”.

  • 174 internal links, 6 external

    The homepage links to 174 pages on coopbank.dk and 6 external pages.

6 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Konto, kort, opsparing og lån – Vores rådgivere hjælper dig med at træffe den beslutning, der giver mening for dig. Bli…”.

  • One H1 headline

    Your main headline reads: “En bank du kan regne med”.

  • Canonical URL set

    The canonical URL is https://coopbank.dk/.

  • 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://coopbank.dk/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    55%

    The HTML your server sends has 1,056 of the 1,918 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://coopbank.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.

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

Other pages

100
  • 15 internal pages checked

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

1 to fixGoogle 10093
  • 25 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

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

  • 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 1,918 words of copy

    The homepage carries about 1,918 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Download nu”, “Start investering” and “Download app”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 1 cookie set on arrival

    1

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

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

Upkeep, stack and company

Stack

CMS
Webflow
Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Webflow

Company

Employees
81
Founded
2013
Headquarters
Albertslund

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on coopbank.dk, including 15 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