Website review, no card needed

kreftforeningen.no logo

kreftforeningen.no website review

Visit site (opens in a new tab)Reviewed 27 October 202624 issues · 76 checks

This review found 24 issues worth fixing on kreftforeningen.no, 9 of them high impact, across 76 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
985 ms883 msMay 9Oct 24929 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026943 ms
May 16, 2026930 ms
May 23, 2026930 ms
May 30, 2026912 ms
Jun 6, 2026920 ms
Jun 13, 2026927 ms
Jun 20, 2026942 ms
Jun 27, 2026958 ms
Jul 4, 2026968 ms
Jul 11, 2026968 ms
Jul 18, 2026973 ms
Jul 25, 2026966 ms
Aug 1, 2026955 ms
Aug 8, 2026932 ms
Aug 15, 2026912 ms
Aug 22, 2026900 ms
Aug 29, 2026906 ms
Sep 5, 2026907 ms
Sep 12, 2026902 ms
Sep 19, 2026901 ms
Sep 26, 2026895 ms
Oct 3, 2026916 ms
Oct 10, 2026932 ms
Oct 17, 2026936 ms
Oct 24, 2026929 ms
Real-visitor tap response (INP)75th percentile, phones
120 ms109 msMay 9Oct 24110 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026111 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026116 ms
Jul 4, 2026119 ms
Jul 11, 2026119 ms
Jul 18, 2026119 ms
Jul 25, 2026118 ms
Aug 1, 2026117 ms
Aug 8, 2026114 ms
Aug 15, 2026113 ms
Aug 22, 2026113 ms
Aug 29, 2026112 ms
Sep 5, 2026113 ms
Sep 12, 2026114 ms
Sep 19, 2026113 ms
Sep 26, 2026116 ms
Oct 3, 2026114 ms
Oct 10, 2026113 ms
Oct 17, 2026112 ms
Oct 24, 2026110 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 kreftforeningen.no (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kreftforeningen.no at 0.4 s0.4 s
  2. kreftforeningen.no at 0.9 s0.9 s
  3. kreftforeningen.no at 1.3 s1.3 s
  4. kreftforeningen.no at 1.8 s1.8 s
  5. kreftforeningen.no at 2.2 s2.2 s
  6. kreftforeningen.no at 2.7 s2.7 s
  7. kreftforeningen.no at 3.1 s3.1 s
  8. kreftforeningen.no at 3.6 s3.6 s

Speed

7 to fix68
  • Reduce unused JavaScript

    1.4 s · 837 KiB

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

  • Render-blocking requests

    1.4 s

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

  • 3,472 HTML elements

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

  • Improve image delivery

    300 ms · 1.8 MB

    3 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 68

    68/100

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

  • Use efficient cache lifetimes

    300 ms · 287 KiB

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

  • 4 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, puzzel.com and cookieinformation.com and others), adding 252 KiB and 210 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 20 KiB

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

  • Legacy JavaScript

    9 KiB

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

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 133 ms

    133 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • Total Blocking Time: 261 ms

    261 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

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

    1.1 s

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

  • Real-user INP: 110 ms

    110 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 426 ms

    426 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 103 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 103 requests on a phone: images 2.2 MB (8), scripts 1.4 MB (66) and fonts 113 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (116 KiB) 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 below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.08 g

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

5 to fixGoogle 9594
  • 1 button without a name

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

  • 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 27 images in the HTML carry an alt attribute.

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

SEO

Google 100100
  • 52 internal links, 13 external

    The homepage links to 52 pages on kreftforeningen.no and 13 external pages.

8 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Sammen jobber vi for at færre skal få kreft, at flere skal overleve kreft og for bedre livskvalitet for pasienter og på…”.

  • One H1 headline

    Your main headline reads: “Kreftforeningen”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Kreftforeningen – Vi er til for alle rammet av kreft”.

  • Canonical URL set

    The canonical URL is https://kreftforeningen.no/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://kreftforeningen.no/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://kreftforeningen.no/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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://kreftforeningen.no/aktuelt has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

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

  • 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    19 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 572 words of copy

    The homepage carries about 572 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Matomo.

  • Direct contact links

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

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.

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 kreftforeningen.no, 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
React
Analytics
Google Tag Manager | Matomo
Hosting
Blix

Company

Employees
200
Founded
1938
Headquarters
Oslo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on kreftforeningen.no, including 12 speed 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