Website review, no card needed

enkontrast.no logo

enkontrast.no website review

Visit site (opens in a new tab)Reviewed 12 November 202636 issues · 75 checks

This review found 36 issues worth fixing on enkontrast.no, 14 of them high impact, across 75 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

Full-page screenshot of enkontrast.no (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix76
  • Use efficient cache lifetimes

    1.4 s · 6.5 MB

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

  • Render-blocking requests

    2.9 s

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

  • Improve image delivery

    2.9 MB

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

  • Mobile performance score: 76

    76/100

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

  • Font display

    450 ms

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

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 637 KiB and 256 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 40 KiB

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

  • Reduce unused JavaScript

    142 KiB

    About 142 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Minify CSS

    16 KiB

    16 KiB could be saved by minifying CSS.

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

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

  • Server response: 114 ms

    114 ms

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

Core Web Vitals

5 to fix81
  • Time to Interactive: 9.9 s

    9.9 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 10 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 40 ms

    40 ms

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

Images and page weight

5 to fix28
  • Page weight: 6.9 MB in 114 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 114 requests on a phone: images 5.9 MB (37), scripts 633 KiB (41) and fonts 197 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Enkontrast_web_TopSlider_1220x517px_02-1.jpg weighs 600 KiB. On a phone connection a single image that size takes seconds.

  • 11 images in older formats

    11 images (1.2 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.

  • 6 images far larger than shown

    352 KiB

    6 images are downloaded at several times the size a phone draws them, for example 317738086_1525387871260569_9105602629389059702_nfull.jpg at 640 px wide, shown at 116 px. Resized copies would save about 352 KiB.

  • 9 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    1.95 g

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

Accessibility

7 to fixGoogle 7789
  • 11 text elements with low contrast

    11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

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

  • All page content should be contained by landmarks (49 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 16 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9281
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“Interiør- & fødselsplakater”, “Interiør- & fødselsplakater” and “Bestselgere”). One clear main headline is easier for people and search engines.

  • 62 internal links, 13 external

    The homepage links to 62 pages on enkontrast.no and 13 external pages.

5 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “En Kontrast – Interiør- og fødselsplakater”.

  • Canonical URL set

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

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.enkontrast.no/interiorplakater, https://www.enkontrast.no/fodselsplakater, https://www.enkontrast.no/blogg, https://www.enkontrast.no/product/fodselsplakat-abstract, https://www.enkontrast.no/product/circle and https://www.enkontrast.no/product/infinite-earth and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.enkontrast.no/blogg has no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.enkontrast.no/blogg, https://www.enkontrast.no/product/fodselsplakat-abstract, https://www.enkontrast.no/product/fodselsplakat-lilla, https://www.enkontrast.no/product/geometric-hexagon, https://www.enkontrast.no/en-hjorneoppgradering and https://www.enkontrast.no/kaker-til-inspirasjon and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

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

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.enkontrast.no' has been blocke…”.

1 checks passed
  • 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 569 words of copy

    The homepage carries about 569 words of visible text.

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 17 cookies set on arrival

    17

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 enkontrast.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
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
One.com A/S

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on enkontrast.no, including 11 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