jdeprofessional.no website review

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

15 images could be 737 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.

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

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

About 12 KiB of CSS is downloaded but never applied on this page.

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.

1 third-party service load with your homepage (Optanon), adding 44 KiB and 0 ms of main-thread time.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (2.8 s).

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

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

3 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-17, real Chrome visitors' tap response (inp) went from 93 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

6 images are downloaded at several times the size a phone draws them, for example MCZO5U7YUW2ZDUVGH5OVRWA4X57A at 1,414 px wide, shown at 358 px. Resized copies would save about 354 KiB.

1 image (40 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.42 g of CO₂e: 50.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 9 elements on the page fail this check, rated critical by axe-core.

2 buttons have no accessible name, so screen readers announce just “button”.

Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your page has no <title>, so Google has to invent the blue link in search results.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

9 links have no real href, so search engines can't follow them.

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

A phone browser shows 408 words, but the HTML your server sends has only 0. 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.jdeprofessional.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 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'script-src' contains an invalid source: 'https://*techsee.me…”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 408 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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