kirken.no website review

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

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

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

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

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

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

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

11 KiB could be saved by minifying CSS.

11 KiB could be saved by minifying JavaScript.

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

3 third-party services load with your homepage (azure.com, Matomo and cookieinformation.com), adding 136 KiB and 122 ms of main-thread time.

1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

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

Desktop scores 97 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Den norske kirke Finn menighet Søk etter innhold Finn menig…”.

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

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

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

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

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

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

1 image is downloaded at several times the size a phone draws it, for example pynt til høsttakkefest foto hans jakob heimvoll.jpeg at 1,920 px wide, shown at 390 px. Resized copies would save about 98 KiB.

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

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.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your meta description is only 51 characters: “Den norske kirke, Den norske kyrkja, kirken, kyrkja”. 70 to 160 characters is enough to sell the click.

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 63 pages on kirken.no and 8 external pages.

A phone browser shows 2,319 words, but the HTML your server sends has only 556. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

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

https://www.kirken.no/nb-NO/bli-med/bli-med-i-den-norske-kirke is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://www.kirken.no/nb-NO all use the title “Startside kirken.no - Den norske kirke”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kirken.no/nb-NO/om-kirken/slik-styres-kirken/samisk-kirkeliv, https://www.kirken.no/nb-NO/om-kirken/die-norwegische-kirche, https://www.kirken.no/nb-NO/om-den-norske-kirke, https://www.kirken.no/nb-NO/min-side, https://www.kirken.no/nb-NO/bli-med/bli-med-i-den-norske-kirke and https://www.kirken.no/nb-NO/dap-i-den-norske-kirke/tvilling-d%C3%A5p and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kirken.no/nb-NO/om-kirken/kontakt-oss/varsling, https://www.kirken.no/nb-NO/bli-med/bli-med-i-den-norske-kirke and https://www.kirken.no/nb-NO/om-kirken/aktuelt/2026/kirker%C3%A5dsm%C3%B8te%20oktober%202026 took over 3 s to send their HTML from our server.

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

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

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

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…”.

Chrome logged issues while loading the page (“Cookie”).

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,319 words of visible text.

Opening the homepage sets 9 cookies (measured from a US location before any click).

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.

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