Website review, no card needed

apmterminals.com logo

apmterminals.com website review

Visit site (opens in a new tab)Reviewed 23 October 202633 issues · 78 checks

This review found 33 issues worth fixing on apmterminals.com, 11 of them high impact, across 78 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

Real-visitor load time (LCP)75th percentile, phones
3.7 s3.0 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.6 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
290 ms256 msMay 2Oct 17277 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026286 ms
May 9, 2026284 ms
May 16, 2026284 ms
May 23, 2026284 ms
May 30, 2026283 ms
Jun 6, 2026282 ms
Jun 13, 2026281 ms
Jun 20, 2026283 ms
Jun 27, 2026282 ms
Jul 4, 2026285 ms
Jul 11, 2026283 ms
Jul 18, 2026278 ms
Jul 25, 2026273 ms
Aug 1, 2026264 ms
Aug 8, 2026260 ms
Aug 15, 2026260 ms
Aug 22, 2026262 ms
Aug 29, 2026266 ms
Sep 5, 2026269 ms
Sep 12, 2026268 ms
Sep 19, 2026269 ms
Sep 26, 2026270 ms
Oct 3, 2026272 ms
Oct 10, 2026274 ms
Oct 17, 2026277 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of apmterminals.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apmterminals.com at 0.7 s0.7 s
  2. apmterminals.com at 1.5 s1.5 s
  3. apmterminals.com at 2.2 s2.2 s
  4. apmterminals.com at 2.9 s2.9 s
  5. apmterminals.com at 3.6 s3.6 s
  6. apmterminals.com at 4.4 s4.4 s
  7. apmterminals.com at 5.1 s5.1 s
  8. apmterminals.com at 5.8 s5.8 s

Speed

7 to fix60
  • Use efficient cache lifetimes

    2.5 s · 368 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.5 s · 239 KiB

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

  • Mobile performance score: 60

    60/100

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

  • Improve image delivery

    150 ms · 354 KiB

    6 images could be 354 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.

  • Legacy JavaScript

    300 ms · 23 KiB

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

  • 1,543 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, maerskline.com and cookieinformation.com and others), adding 286 KiB and 289 ms of main-thread time.

  • Font display

    200 ms

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

  • Reduce unused CSS

    150 ms · 38 KiB

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

  • 6 long tasks on the main thread

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

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

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 10.6 s

    10.6 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Time to Interactive: 10.7 s

    10.7 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 910 ms

    910 ms

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

  • Tap response (INP) held steady for real visitors

    -3%

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

5 checks passed
  • Real-user INP: 179 ms

    179 ms

    Real visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 109 ms

    109 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix65
  • 1 image over 500 KB

    260819-APMTerminals-Hapag-Lloyd-1600.jpg weighs 716 KiB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    809 KiB

    4 images are downloaded at several times the size a phone draws them, for example 260819-APMTerminals-Hapag-Lloyd-1600.jpg at 1,600 px wide, shown at 326 px. Resized copies would save about 809 KiB.

  • About 0.4 g of CO₂ per visit

    0.43 g

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

3 checks passed
  • Page weight: 1.5 MB in 56 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 56 requests on a phone: scripts 682 KiB (17), images 663 KiB (10) and fonts 111 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9394
  • 5 text elements with low contrast

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (6 elements).

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 23 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • Title is short (20 characters)

    Your title is only 20 characters: “Home - APM Terminals”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • Meta description is long (417 characters)

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 11 internal links, 0 external

    The homepage links to 11 pages on apmterminals.com and 0 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Lifting standards”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.apmterminals.com/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.apmterminals.com/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 (196 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.apmterminals.com/en/about/who-we-are is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.apmterminals.com/careers/vacancies has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.apmterminals.com/careers/vacancies and https://www.apmterminals.com/service-locator have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.apmterminals.com/en/news/news-releases and https://www.apmterminals.com/careers/vacancies have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://www.apmterminals.com/en/news/news-releases/2026/260819-APMTerminals-and-Hapag-Lloyd-partner-at-Maasvlakte-II and https://www.apmterminals.com/en/tools/terminal-alerts took over 3 s to send their HTML from our server.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 8 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.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'getRegistrations')”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 196 words

    The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More...”.

  • 1 call to action

    The homepage has 1 call to action, for example “Learn More...”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 apmterminals.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Company

Employees
20,600
Founded
2001
Headquarters
The Hague

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on apmterminals.com, including 15 speed issues, 5 SEO issues and 3 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