Core Web Vitals targets for maritime corporate sites

Core Web Vitals are not a ranking factor in the way “high quality content” is a ranking factor. They’re a tiebreaker, applied per-page, that can make the difference between a maritime service page sitting in position 6 versus position 4. On commercial queries with thin SERP differences, that one place can be the page that wins the buyer.

Most maritime corporate sites I audit fail Core Web Vitals on the templates that matter most. Not because the technology is hard but because nobody held the developers accountable for performance after the brand-led redesign.

The three metrics and where maritime sites fail them

LCP (Largest Contentful Paint). Target: under 2.5 seconds. The single biggest LCP killer on maritime sites is the hero photograph. A 4MB photo of a container ship at the Suez Canal, served as a JPG at full resolution, will tank LCP on every page. The fix is not subtle: convert to WebP or AVIF, serve responsive sizes, lazy-load anything below the fold, preload the hero.

INP (Interaction to Next Paint). Target: under 200ms. INP measures how quickly the page responds when a user interacts. Maritime sites with bloated JavaScript (chat widgets, multiple analytics scripts, third-party newsletter popups) often have INP in the 400-600ms range. The fix is auditing the JavaScript bundle and removing what isn’t earning its weight.

CLS (Cumulative Layout Shift). Target: under 0.1. CLS gets bad on sites where images and embedded content load without reserved space, causing the page to jump as content arrives. Define width and height on every image and iframe. Reserve space for cookie banners and chat widgets.

What to measure on, and what not to

The mistake most maritime brands make is running Lighthouse on the homepage, getting a 92 score and assuming the site is fine. The homepage on most maritime sites is the most-optimised page on the site. The service templates, where buyers actually convert, are where the real performance debt lives.

Run real-device testing on:

• Your top three service pages
• Two regional or office pages
• A representative case study
• The contact and quote-request templates

Use Chrome’s Web Vitals extension or the Search Console Core Web Vitals report, which uses real Chrome user data. Lighthouse is useful for diagnosing causes but not for measuring real-world performance.

The five performance wins worth doing

In our maritime audits, these five interventions tend to deliver the bulk of the available gains:

1. Replace hero images with optimised modern formats. WebP at 80% quality, sized to viewport, preloaded. Removes 2-3MB and 1+ second of LCP.
2. Defer non-critical JavaScript. Move analytics, marketing pixels and chat widgets to load after first paint. Knocks INP down by 200-400ms.
3. Reserve space for everything. Set explicit dimensions on images, embeds, ads and dynamic content. CLS drops to near zero.
4. Self-host fonts. Maritime brands love custom fonts (corporate identity reasons). Self-hosting with font-display: swap and preloading the critical weights removes external request blocking.
5. Cache headers and CDN. Most maritime sites are served from a single regional host. A CDN like Cloudflare or Fastly cuts TTFB by 200-500ms for international buyers, which directly improves LCP.

What “good enough” looks like

You don’t need a 100 Lighthouse score. You need to pass Core Web Vitals on real-world data, which means roughly:

• 75% of visits hit LCP under 2.5s
• 75% of visits hit INP under 200ms
• 75% of visits hit CLS under 0.1

If your Search Console CWV report shows “Good” status on the templates that drive pipeline, the work is done well enough. Going from “Good” to “perfect” rarely moves rankings.

The goal isn’t a vanity score. The goal is a service page that loads fast enough that a fleet director on a hotel WiFi connection in Mumbai doesn’t bounce before reading the value proposition. Pass that bar on the templates that drive enquiries and the rest is housekeeping.