akerbp.com website review

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

15 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.

About 636 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

Google CDN costs a phone 257 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

7 third-party services load with your homepage (Google CDN, JSDelivr CDN and Cloudflare CDN and others), adding 1,022 KiB and 367 ms of main-thread time.

About 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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.

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

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

3 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 86 ms to 92 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.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 66 requests on a phone: images 4.7 MB (17), scripts 1.1 MB (25) and other files 348 KiB (4). Under 2 MB keeps phones on slow connections fast.

skarv-sc-7-samlet-v15-plakat-scaled.jpg weighs 1.7 MB. On a phone connection a single image that size takes seconds.

10 images (2.1 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.

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

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

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

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 2 elements on the page fail this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 2 <h1> headlines (“Vi skalredusere utslippjobbe smarteresamarbeide m…” and “The rebel revolution”). One clear main headline is easier for people and search engines.

Your meta description is 225 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 84 pages on akerbp.com and 8 external pages.

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

/investor and /investor/investors-2 all use the title “Investor Relations - Aker BP”. Search engines can't tell which page to show for a search, so each competes with the others.

/en, /om-oss, /styret, /ledelsen, /var-virksomhet and /baerekraft-2 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /investor/investors-2, whose canonical is /investor. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/baerekraft-2 has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images are served at too low a resolution for sharp phone screens.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

1 link go through two or more redirects, for example https://www.google.com/calendar/render?action=TEMPLATE&text=DATE:29.10.2026&dates=Quarterly%20Report%20-%20Q3/Quarterly%20Report%20-%20Q3.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

akerbp.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

akerbp.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 1 cookie (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.