Website review, no card needed

nsf.no logo

nsf.no website review

Visit site (opens in a new tab)Reviewed 26 October 202622 issues · 73 checks

This review found 22 issues worth fixing on nsf.no, 7 of them high impact, across 73 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
966 ms775 msMay 9Oct 24942 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026813 ms
May 16, 2026814 ms
May 23, 2026810 ms
May 30, 2026797 ms
Jun 6, 2026798 ms
Jun 13, 2026806 ms
Jun 20, 2026814 ms
Jun 27, 2026868 ms
Jul 4, 2026896 ms
Jul 11, 2026911 ms
Jul 18, 2026914 ms
Jul 25, 2026916 ms
Aug 1, 2026914 ms
Aug 8, 2026908 ms
Aug 15, 2026898 ms
Aug 22, 2026898 ms
Aug 29, 2026899 ms
Sep 5, 2026917 ms
Sep 12, 2026933 ms
Sep 19, 2026934 ms
Sep 26, 2026937 ms
Oct 3, 2026938 ms
Oct 10, 2026939 ms
Oct 17, 2026944 ms
Oct 24, 2026942 ms
Real-visitor tap response (INP)75th percentile, phones
88 ms78 msMay 9Oct 2483 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202686 ms
May 16, 202686 ms
May 23, 202686 ms
May 30, 202686 ms
Jun 6, 202686 ms
Jun 13, 202686 ms
Jun 20, 202686 ms
Jun 27, 202685 ms
Jul 4, 202686 ms
Jul 11, 202686 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202685 ms
Aug 8, 202682 ms
Aug 15, 202681 ms
Aug 22, 202680 ms
Aug 29, 202679 ms
Sep 5, 202680 ms
Sep 12, 202680 ms
Sep 19, 202680 ms
Sep 26, 202680 ms
Oct 3, 202680 ms
Oct 10, 202680 ms
Oct 17, 202681 ms
Oct 24, 202683 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 nsf.no (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix76
  • Use efficient cache lifetimes

    2.5 s · 763 KiB

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

  • Mobile performance score: 76

    76/100

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

  • Render-blocking requests

    850 ms

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

  • Improve image delivery

    500 ms · 273 KiB

    6 images could be 273 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Reduce unused JavaScript

    450 ms · 170 KiB

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

  • Reduce unused CSS

    300 ms · 71 KiB

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

  • Font display

    150 ms

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

  • 2 long tasks on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (skyra.no), adding 134 KiB and 123 ms of main-thread time.

  • 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: 0.6 s

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

  • Server response: 128 ms

    128 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “En illustrasjon av flere sykepleiere som arbeider på sykehu…”.

  • Time to Interactive: 7.3 s

    7.3 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

9 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.0 s

    1.0 s

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

  • Real-user INP: 75 ms

    75 ms

    Real visitors wait 75 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: 515 ms

    515 ms

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

  • Cumulative Layout Shift: 0.068

    0.068

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Total Blocking Time: 53 ms

    53 ms

    Scripts block the page for only 53 ms while loading. Good is under 200 ms.

Images and page weight

100
  • 1 image in older formats

    1 image (94 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.

  • 2 images below the first screen load straight away

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

  • About 0.4 g of CO₂ per visit

    0.40 g

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

2 checks passed
  • Page weight: 1.4 MB in 40 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 40 requests on a phone: fonts 434 KiB (9), images 410 KiB (9) and scripts 335 KiB (5). That is a lean page.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9397
  • 1 tap target too small

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • Title is short (29 characters)

    Your title is only 29 characters: “Norsk Sykepleierforbund - NSF”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 X (Twitter) card tag

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

  • 57 internal links, 6 external

    The homepage links to 57 pages on nsf.no and 6 external pages.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Norsk Sykepleierforbund jobber for dine rettigheter og anerkjennelse som sykepleier. Vi er Norges fjerde største fagfor…”.

  • One H1 headline

    Your main headline reads: “Sykepleiefaget i front for å gi trygge og gode helsetjenester”.

  • Canonical URL set

    The canonical URL is https://www.nsf.no/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

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

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 (318 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.nsf.no/forsikring-og-medlemsfordeler/om-medlemskap-i-norsk-sykepleierforbund, https://www.nsf.no/forsikring-og-medlemsfordeler/forsikring-og-medlemsfordeler, https://www.nsf.no/kurs-og-arrangementer, https://www.nsf.no/nsf-student, https://www.nsf.no/lonn-og-tariff and https://www.nsf.no/arbeidstid-og-turnus and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.nsf.no/forsikring-og-medlemsfordeler/forsikring-og-medlemsfordeler, whose canonical is https://www.nsf.no/forsikring-og-medlemsfordeler. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 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 304 words of copy

    The homepage carries about 304 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Matomo.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 nsf.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
Drupal
Analytics
Matomo
Hosting
Globalconnect

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on nsf.no, including 10 speed issues, 3 SEO issues and 4 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