Website review, no card needed

callme.dk logo

callme.dk website review

Visit site (opens in a new tab)Reviewed 6 November 202648 issues · 85 checks

This review found 48 issues worth fixing on callme.dk, 15 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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.3 s1.9 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
185 ms146 msMay 16Oct 31179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026151 ms
May 23, 2026150 ms
May 30, 2026152 ms
Jun 6, 2026158 ms
Jun 13, 2026164 ms
Jun 20, 2026171 ms
Jun 27, 2026178 ms
Jul 4, 2026178 ms
Jul 11, 2026178 ms
Jul 18, 2026178 ms
Jul 25, 2026176 ms
Aug 1, 2026173 ms
Aug 8, 2026172 ms
Aug 15, 2026171 ms
Aug 22, 2026173 ms
Aug 29, 2026176 ms
Sep 5, 2026179 ms
Sep 12, 2026180 ms
Sep 19, 2026180 ms
Sep 26, 2026180 ms
Oct 3, 2026179 ms
Oct 10, 2026179 ms
Oct 17, 2026180 ms
Oct 24, 2026180 ms
Oct 31, 2026179 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 callme.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. callme.dk at 0.7 s0.7 s
  2. callme.dk at 1.5 s1.5 s
  3. callme.dk at 2.2 s2.2 s
  4. callme.dk at 3.0 s3.0 s
  5. callme.dk at 3.7 s3.7 s
  6. callme.dk at 4.4 s4.4 s
  7. callme.dk at 5.2 s5.2 s
  8. callme.dk at 5.9 s5.9 s

Speed

13 to fix42
  • Use efficient cache lifetimes

    2.8 s · 7.9 MB

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

  • Reduce unused JavaScript

    5.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

  • Font display

    1.3 s

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 42

    42/100

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

  • 3,243 HTML elements

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

  • Improve image delivery

    1.9 MB

    6 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, bellmetric.net and Trust Pilot and others), adding 1.6 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 989 ms

    989 ms

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

  • Reduce unused CSS

    600 ms · 127 KiB

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

  • Legacy JavaScript

    650 ms · 38 KiB

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

  • Main-thread work: 2.9 s

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

  • 12 long tasks on the main thread

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

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

    112 ms

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

Core Web Vitals

10 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: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vi bruger vores egne cookies samt cookies fra tredjeparter …”.

  • Time to Interactive: 29.3 s

    29.3 s

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

  • Speed Index: 15.3 s

    15.3 s

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

  • Real-user INP: 202 ms

    202 ms

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

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

    593 ms

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

  • 30 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Cumulative Layout Shift: 0.139

    0.139

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

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

    +19%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

Images and page weight

5 to fix18
  • Page weight: 10.2 MB in 93 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 93 requests on a phone: images 3.9 MB (35), media 3.5 MB (2) and scripts 2.3 MB (22). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    1.0 MB

    4 images are downloaded at several times the size a phone draws them, for example oppo-a6x-5g.png_539804 at 640 px wide, shown at 100 px. Resized copies would save about 1.0 MB.

  • 1 image over 500 KB

    oppo-a6x-5g.png_539804 weighs 507 KiB. On a phone connection a single image that size takes seconds.

  • 15 images in older formats

    15 images (1.9 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.

  • 17 images below the first screen load straight away

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

  • About 2.9 g of CO₂ per visit

    2.89 g

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

Accessibility

7 to fix70
  • 21 images without alt text

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (4 elements).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • No page language

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

SEO

3 to fixGoogle 8590
  • Meta description is long (170 characters)

    Your meta description is 170 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.

  • 5 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 100 internal links, 14 external

    The homepage links to 100 pages on callme.dk and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Stort udvalg af mobiler”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Call me | Mobilabonnement, mobilt bredbånd & smartphones”.

  • Canonical URL set

    The canonical URL is https://www.callme.dk/.

  • Structured data in place

    Structured data found: 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.callme.dk/sitemapindex.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    32%

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

  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

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

Other pages

3 to fix86
  • 2 pages share a title

    https://www.callme.dk/abonnementer/mobil/world-mobilabonnement and https://www.callme.dk/abonnementer/mobil/fri-tale-og-80-gb-plus-5g-internet all use the title “Mobilabonnement med fri tale og 80 GB data - Call me”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.callme.dk/abonnementer/mobil/world-mobilabonnement and https://www.callme.dk/abonnementer/mobil/fri-tale-og-80-gb-plus-5g-internet use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.callme.dk/abonnementer/mobil and https://www.callme.dk/webshop/mobiler/brand/apple/iphone-18 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 67 found) and read each the way a search engine does.

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

  • 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 10087
  • 7 small tap targets

    7 of 28 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 “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 3,470 words of copy

    The homepage carries about 3,470 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Call me's netværk er i top”, “Om Call me” and “Mit Call me oversigt”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 callme.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
Bootstrap
Analytics
Google Tag Manager
Hosting
Telia Company AB

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on callme.dk, including 23 speed issues, 3 SEO issues 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