Website review, no card needed

sykehusapotekene.no logo

sykehusapotekene.no website review

Visit site (opens in a new tab)Reviewed 29 October 202621 issues · 74 checks

This review found 21 issues worth fixing on sykehusapotekene.no, 7 of them high impact, across 74 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
1.1 s778 msMay 9Oct 24814 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026962 ms
May 16, 2026961 ms
May 23, 2026974 ms
May 30, 2026956 ms
Jun 6, 2026960 ms
Jun 13, 2026954 ms
Jun 20, 2026953 ms
Jun 27, 2026949 ms
Jul 4, 2026969 ms
Jul 11, 2026977 ms
Jul 18, 2026997 ms
Jul 25, 20261.0 s
Aug 1, 2026975 ms
Aug 8, 2026977 ms
Aug 15, 2026953 ms
Aug 22, 2026951 ms
Aug 29, 2026958 ms
Sep 5, 2026920 ms
Sep 12, 2026884 ms
Sep 19, 2026842 ms
Sep 26, 2026818 ms
Oct 3, 2026810 ms
Oct 10, 2026816 ms
Oct 17, 2026829 ms
Oct 24, 2026814 ms
Real-visitor tap response (INP)75th percentile, phones
90 ms72 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202681 ms
May 16, 202677 ms
May 23, 202674 ms
May 30, 202674 ms
Jun 6, 202677 ms
Jun 13, 202678 ms
Jun 20, 202680 ms
Jun 27, 202686 ms
Jul 4, 202684 ms
Jul 11, 202682 ms
Jul 18, 202684 ms
Jul 25, 202680 ms
Aug 1, 202681 ms
Aug 8, 202683 ms
Aug 15, 202685 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202688 ms
Oct 24, 202686 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 sykehusapotekene.no (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix62
  • Use efficient cache lifetimes

    3.0 s · 706 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 96 KiB

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

  • Reduce unused JavaScript

    150 ms · 35 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (azure.com, Silktide and azurecontainerapps.io), adding 90 KiB and 84 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    51 KiB

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

  • 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, 249 ms of it running JavaScript. That is comfortably low.

  • Server response: 30 ms

    30 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “En person som gir en person en pakke”.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • Cumulative Layout Shift: 0.211

    0.211

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

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

  • 2 images without width and height

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

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

    +10%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 81 ms to 86 ms 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: 0.6 s

    0.6 s

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

  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 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.6 s

    0.6 s

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

  • Real-user TTFB: 271 ms

    271 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 42 ms

    42 ms

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

Images and page weight

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

    134467-sykehusapotekene0017.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).

  • About 0.3 g of CO₂ per visit

    0.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.1 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.1 MB in 59 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 59 requests on a phone: scripts 530 KiB (42), images 232 KiB (7) and other files 164 KiB (4). 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

1 to fixGoogle 10099
  • All page content should be contained by landmarks (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is short (29 characters)

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 21 internal links, 3 external

    The homepage links to 21 pages on sykehusapotekene.no and 3 external pages.

6 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Vi kan legemidler! Vår kompetanse og nærhet til sykehusene gjør at du får effektiv og tilpasset hjelp og veiledning”.

  • One H1 headline

    Your main headline reads: “Sykehus­apotekene HF Mer enn et vanlig apotek”.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://www.sykehusapotekene.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.sykehusapotekene.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 (688 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.sykehusapotekene.no/rad-og-veiledning and https://www.sykehusapotekene.no/fag-og-forskning have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.sykehusapotekene.no/klikk-og-hent-er-midlertidig-nede 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.

  • 1 page slow to respond

    https://www.sykehusapotekene.no/rad-og-veiledning/temaer/rad-om-medisinbruk_ny/fa-en-god-start-med-hjertemedisinen-din took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://norwayeast-0.in.applicationinsights.azure.com//v2/track' violates the following Content Security…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 734 words of visible text.

1 checks passed
  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 sykehusapotekene.no, 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
Hosting
Episerver

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on sykehusapotekene.no, including 9 speed issues, 2 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