C — https://www.maersk.com | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

'unsafe-eval' found in script source

Security › Content Security Policy

'unsafe-inline' found in script source

Security › Content Security Policy

Cookie 'bm_sz' is missing the Secure flag

Security › Cookie Security

Page weighs 11.4 MB (6.3 MB transferred)

Performance › Page Weight Budget

15 link(s) with no accessible text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.maersk.com)](https://beavercheck.com/results/ef2540f3-625a-b877-67f4-7ce9d5b96f4a)

HTML

<a href="https://beavercheck.com/results/ef2540f3-625a-b877-67f4-7ce9d5b96f4a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.maersk.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.maersk.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.67 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

7.05 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

374 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.030

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

15.07 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

7.14 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
assets.maerskline.com/mop/rum/latest/mop-rum.js	0.0 ms	67.3 KiB
www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B	21600.0 s	82.5 KiB
assets.maerskline.com/mds/fonts/text/MaerskText-Light.woff2	0.0 ms	26.5 KiB
/casemanagement_assets/green/chat-scripts/Initial-Chat-Sc...	0.0 ms	6.9 KiB
/mds/latest/design-tokens/maersk/light/css/design-tokens-...	0.0 ms	5.3 KiB
service.force.com/embeddedservice/5.0/esw.min.js	86400.0 s	9.4 KiB
assets.maerskline.com/scp/visitor-min.js	0.0 ms	1.3 KiB
assets.maerskline.com/mds/fonts/fonts-cdn.css	0.0 ms	975 B
www.maersk.com/content/media/ign/icons/header/24px/manage-booking-icon.svg	864000.0 s	1.7 KiB
www.maersk.com/content/media/ign/icons/header/24px/mi-book-open.svg	864000.0 s	740 B
www.maersk.com/content/media/ign/icons/header/24px/mi-vessel-side.svg	864000.0 s	658 B
www.maersk.com/content/media/ign/icons/header/24px/mi-route.svg	864000.0 s	575 B
www.maersk.com/content/media/ign/icons/header/24px/mi-shield-check.svg	864000.0 s	537 B
www.maersk.com/content/media/ign/icons/header/24px/mi-comments.svg	864000.0 s	533 B
www.maersk.com/content/media/ign/icons/header/24px/mi-calendar-clock.svg	864000.0 s	498 B
www.maersk.com/content/media/ign/icons/header/24px/mi-airplane.svg	864000.0 s	465 B
www.maersk.com/content/media/ign/icons/header/24px/mi-calendar-check.svg	864000.0 s	342 B
www.maersk.com/content/media/ign/icons/header/24px/mi-boxes-stacked.svg	864000.0 s	304 B
www.maersk.com/content/media/ign/icons/header/24px/mi-envelope.svg	864000.0 s	292 B
www.maersk.com/content/media/ign/icons/header/24px/mi-container-stacked.svg	864000.0 s	285 B
assets.maerskline.com/mds/fonts/headline/MaerskHeadline-Regular.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Bold.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/headline/MaerskHeadline-Light.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Medium.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Regular.woff2	0.0 ms	0 B
assets.maerskline.com/integrated-global-nav/2/loader.js	300.0 s	0 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:42.78 source:map[column:56913 line:0 type:source-location url:https://www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:69.019 label:Time to first byte subpart:timeToFirstByte] map[duration:27.709 label:Resource load delay subpart:resourceLoadDelay] map[duration:53.135 label:Resource load duration subpart:resourceLoadDuration] map[duration:9012.675 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Digital Logistics Services

path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,2,IMG

selector: div.homepage-hero__content > div.background-poc > picture.background-poc__cover > img

snippet: <img src="/~/media_sc9/maersk/homepage/hero/digital-services_400x800.jpg?h=800&w=400…" alt="Digital Logistics Services" loading="eager">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: Digital Logistics Services

path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,2,IMG

selector: div.homepage-hero__content > div.background-poc > picture.background-poc__cover > img

snippet: <img src="/~/media_sc9/maersk/homepage/hero/digital-services_400x800.jpg?h=800&w=400…" alt="Digital Logistics Services" loading="eager">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
assets.maerskline.com/integrated-global-nav/2/loader.js	0 B
/mds/latest/design-tokens/maersk/light/css/design-tokens-...	5.3 KiB	151 ms
assets.maerskline.com/mds/fonts/fonts-cdn.css	975 B	768 ms
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	89.6 KiB	1.4 s

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 410 ms 80.5 KiB

URL	Transfer Size	Est Savings
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	88.9 KiB	80.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.2 s 181.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-TMZZL49K	161.9 KiB	75.4 KiB
www.maersk.com/Assets_sc9/Maersk/scripts/main.js?v=1.0.9561.33888.30	88.1 KiB	70.4 KiB
/integrated-global-nav/3/3.4.22-2026.0306.104242/ign.maeu...	88.6 KiB	35.6 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	884 ms	17 ms	0.0 ms
www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B	875 ms	625 ms	27 ms
www.maersk.com/	498 ms	101 ms	3.0 ms
assets.maerskline.com/mop/rum/latest/mop-rum.js	413 ms	279 ms	22 ms
/integrated-global-nav/3/3.4.22-2026.0306.104242/ign.maeu...	363 ms	202 ms	33 ms
www.googletagmanager.com/gtm.js?id=GTM-TMZZL49K	288 ms	215 ms	62 ms
www.maersk.com/Assets_sc9/Maersk/scripts/main.js?v=1.0.9561.33888.30	277 ms	141 ms	32 ms
policy.app.cookieinformation.com/latest/maersk.com/en.js	86 ms	9.7 ms	35 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	1.7 s
Other	1.1 s
Style & Layout	566 ms
Script Parsing & Compilation	235 ms
Parse HTML & CSS	166 ms
Rendering	70 ms
Garbage Collection	42 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.maersk.com/~/media_sc9/maersk/homepage/video/Il25_homepage-loop_10s_5mb.mp4	5.1 MiB
/~/media_sc9/maersk/homepage/video/IL25-homepage-video_19...	461.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-TMZZL49K	162.3 KiB
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	89.6 KiB
/integrated-global-nav/3/3.4.22-2026.0306.104242/ign.maeu...	89.1 KiB
www.maersk.com/Assets_sc9/Maersk/scripts/main.js?v=1.0.9561.33888.30	88.1 KiB
www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B	82.5 KiB
assets.maerskline.com/mop/rum/latest/mop-rum.js	67.3 KiB
/~/media_sc9/maersk/homepage/hero/digital-services_400x80...	31.1 KiB
assets.maerskline.com/mds/fonts/text/MaerskText-Light.woff2	26.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
LinkedIn `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/linkedin.svg
YouTube `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/youtube.svg
Instagram `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/instagram.svg
Facebook `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/facebook.svg
X `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/x.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 3 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 6 animated elements found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div.service-widget__tabs > nav.tabs > div.tabs__wrapper > button.tabs__next `div.service-widget__tabs > nav.tabs > div.tabs__wrapper > button.tabs__next`
div.p-page__section__outer > div.p-page__section__inner > div.p-section__sticky-callout > button.p-section__sticky-callout__close `div.p-page__section__outer > div.p-page__section__inner > div.p-section__sticky-callout > button.p-section__sticky-callout__close`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Failing Elements
All categories Digitalisation Growth Integrated logistics Resilience Sustainabi… `div.p-page__section__inner > div.p-section__insights-mosaic > div.form-input > select.form-input__field`
All regions North America Latin America Europe India Middle East and Africa Asi… `div.p-page__section__chile > div.p-section__featured-news__actions__filter > div.form-input > select#fld-regions`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
body > div#chatDiv > iframe#chatFrame `body > div#chatDiv > iframe#chatFrame`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
Middle East Situation `div.p-page__section__inner > div.p-section__sticky-callout > div.p-section__sticky-callout__copy > h3.p-section__sticky-callout__title`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
www.maersk.com/east-west-network	Read more
www.maersk.com/insights/logistics-trend-map	Read more
www.maersk.com/east-west-network	Read more
www.maersk.com/insights/logistics-trend-map	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

522 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.01 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.017

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.51 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.01 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
assets.maerskline.com/mop/rum/latest/mop-rum.js	0.0 ms	67.3 KiB
www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B	21600.0 s	82.4 KiB
assets.maerskline.com/mds/fonts/text/MaerskText-Light.woff2	0.0 ms	26.5 KiB
/casemanagement_assets/green/chat-scripts/Initial-Chat-Sc...	0.0 ms	6.9 KiB
/mds/latest/design-tokens/maersk/light/css/design-tokens-...	0.0 ms	5.3 KiB
service.force.com/embeddedservice/5.0/esw.min.js	86400.0 s	9.4 KiB
assets.maerskline.com/scp/visitor-min.js	0.0 ms	1.3 KiB
assets.maerskline.com/mds/fonts/fonts-cdn.css	0.0 ms	975 B
www.maersk.com/content/media/ign/icons/header/24px/manage-booking-icon.svg	864000.0 s	1.7 KiB
www.maersk.com/content/media/ign/icons/header/24px/mi-book-open.svg	864000.0 s	745 B
www.maersk.com/content/media/ign/icons/header/24px/mi-vessel-side.svg	864000.0 s	660 B
www.maersk.com/content/media/ign/icons/header/24px/mi-route.svg	864000.0 s	585 B
www.maersk.com/content/media/ign/icons/header/24px/mi-shield-check.svg	864000.0 s	546 B
www.maersk.com/content/media/ign/icons/header/24px/mi-comments.svg	864000.0 s	535 B
www.maersk.com/content/media/ign/icons/header/24px/mi-calendar-clock.svg	864000.0 s	505 B
www.maersk.com/content/media/ign/icons/header/24px/mi-airplane.svg	864000.0 s	474 B
www.maersk.com/content/media/ign/icons/header/24px/mi-calendar-check.svg	864000.0 s	344 B
www.maersk.com/content/media/ign/icons/header/24px/mi-boxes-stacked.svg	864000.0 s	313 B
www.maersk.com/content/media/ign/icons/header/24px/mi-container-stacked.svg	864000.0 s	295 B
www.maersk.com/content/media/ign/icons/header/24px/mi-envelope.svg	864000.0 s	294 B
assets.maerskline.com/mds/fonts/headline/MaerskHeadline-Regular.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Bold.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/headline/MaerskHeadline-Light.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Medium.woff2	0.0 ms	0 B
assets.maerskline.com/mds/fonts/text/MaerskText-Regular.woff2	0.0 ms	0 B
assets.maerskline.com/integrated-global-nav/2/loader.js	300.0 s	0 B

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.225 source:map[column:56913 line:0 type:source-location url:https://www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
Digital Logistics Services `div.homepage-hero__content > div.background-poc > picture.background-poc__cover > img`	/~/media_sc9/maersk/homepage/hero/digital-services_1920x9...	118.1 KiB	53.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:49.316 label:Time to first byte subpart:timeToFirstByte] map[duration:25.592 label:Resource load delay subpart:resourceLoadDelay] map[duration:64.723 label:Resource load duration subpart:resourceLoadDuration] map[duration:10148.758 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Digital Logistics Services

path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,2,IMG

selector: div.homepage-hero__content > div.background-poc > picture.background-poc__cover > img

snippet: <img src="https://www.maersk.com/~/media_sc9/maersk/homepage/hero/digital-services_1…" alt="Digital Logistics Services" loading="eager">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: Digital Logistics Services

path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,2,IMG

selector: div.homepage-hero__content > div.background-poc > picture.background-poc__cover > img

snippet: <img src="https://www.maersk.com/~/media_sc9/maersk/homepage/hero/digital-services_1…" alt="Digital Logistics Services" loading="eager">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
assets.maerskline.com/integrated-global-nav/2/loader.js	0 B
/mds/latest/design-tokens/maersk/light/css/design-tokens-...	5.3 KiB
assets.maerskline.com/mds/fonts/fonts-cdn.css	975 B	213 ms
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	89.6 KiB	161 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 40 ms 78.9 KiB

URL	Transfer Size	Est Savings
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	88.9 KiB	78.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 80 ms 181.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-TMZZL49K	161.9 KiB	75.4 KiB
www.maersk.com/Assets_sc9/Maersk/scripts/main.js?v=1.0.9561.33888.30	88.1 KiB	70.3 KiB
/integrated-global-nav/3/3.4.22-2026.0306.104242/ign.maeu...	88.6 KiB	35.6 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.maersk.com/~/media_sc9/maersk/homepage/video/Il25_homepage-loop_10s_5mb.mp4	5.1 MiB
/~/media_sc9/maersk/homepage/video/IL25-homepage-video_19...	1.3 MiB
www.googletagmanager.com/gtm.js?id=GTM-TMZZL49K	162.3 KiB
/~/media_sc9/maersk/homepage/hero/digital-services_1920x9...	118.8 KiB
www.maersk.com/Assets_sc9/Maersk/css/maeu.css?v=1.0.9561.33888.30	89.6 KiB
/integrated-global-nav/3/3.4.22-2026.0306.104242/ign.maeu...	89.1 KiB
www.maersk.com/Assets_sc9/Maersk/scripts/main.js?v=1.0.9561.33888.30	88.1 KiB
/~/media_sc9/maersk/homepage/video/IL25-homepage-video_19...	85.0 KiB
www.maersk.com/31BUw3CMS62TMjGsKGfh/GE9iL0rOEhau8S/CRtoImUcAQ/aQpmaSY/2FS4B	82.4 KiB
assets.maerskline.com/mop/rum/latest/mop-rum.js	67.3 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
LinkedIn `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/linkedin.svg
YouTube `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/youtube.svg
Instagram `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/instagram.svg
Facebook `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/facebook.svg
X `div.ign-footer__social__container > div.ign-footer__social__links > a.ign-footer__social__link > img.ign-icon`	www.maersk.com/content/media/ign/icons/footer/social/24px/x.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 3 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid non-composited animations 3 animated elements found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 10 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid long main-thread tasks

Accessibility

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Failing Elements
All categories Digitalisation Growth Integrated logistics Resilience Sustainabi… `div.p-page__section__inner > div.p-section__insights-mosaic > div.form-input > select.form-input__field`
All regions North America Latin America Europe India Middle East and Africa Asi… `div.p-page__section__chile > div.p-section__featured-news__actions__filter > div.form-input > select#fld-regions`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
body > div#chatDiv > iframe#chatFrame `body > div#chatDiv > iframe#chatFrame`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Failing Elements
Middle East Situation `div.p-page__section__inner > div.p-section__sticky-callout > div.p-section__sticky-callout__copy > h3.p-section__sticky-callout__title`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

	URL	Displayed size	Actual size	Expected size
East-west-network `li.ign-header__megamenu__ul__li > div.ign-header__promo > div.ign-header__promo__container > img.ign-header__promo__img`	data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7	168 x 168	1 x 1	168 x 168

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
www.maersk.com/akam/13/2f77f8c3	`Failed to load resource: the server responded with a status of 404 ()`

Issue type
Content security policy

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Page has the HTML doctype

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
www.maersk.com/east-west-network	Read more
www.maersk.com/insights/logistics-trend-map	Read more
www.maersk.com/east-west-network	Read more
www.maersk.com/insights/logistics-trend-map	Read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.maersk.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Navigation

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Navigation

Best Practices

User Experience

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts