Skip to content
Hibernia Line — Cork to Boulogne-sur-Mer
SEO & site-health audit

The current site,measured honestly.

Before proposing a new platform, we ran a full, evidence-backed audit of the live hibernia-line.com. It's a genuinely well-built marketing site — strong content, clean fundamentals — with a few high-value gaps in international SEO, page experience and accessibility.

Audited
2 Jul 2026
Pages analysed
~100 + blog
Languages
EN · FR · DE · NL
Stack
WordPress · WPML · Elementor
Overall score
74/100
Good foundations

Weighted across seven categories. Higher than a typical new-launch site thanks to real content depth — held back by three fixable issues.

The scorecard

Seven categories, weighted by impact

Each score is backed by specific evidence — response headers, page markup, sitemaps and a real browser audit — not a single automated grade.

Technical SEO

25% weight

Canonicals, redirects & sitemaps correct — but hreflang missing, headers weak, TTFB slow

70

Content quality

20% weight

Deep interior pages + a real blog with Article & author schema

82

On-page SEO

15% weight

Query-led interior titles, single H1, strong meta descriptions

83

Structured data

15% weight

WebSite/Org/Breadcrumb + Article; no Service/Offer for the route

74

Performance (CWV)

10% weight

TTFB ~2.0s on a heavy stack — field data unavailable this run *

55

Image optimisation

10% weight

Alt text mostly present, images lazy-load; formats unverified

72

AI search / GEO

5% weight

llms.txt present, AI crawlers allowed, rich schema aids answers

80

* Performance is scored from server response time and stack weight — Google's field Core Web Vitals were unavailable during this run (see methodology).

Lighthouse (mobile)

Google's own checks agree

A real Chrome audit rates the fundamentals highly — SEO and best practices are perfect. Accessibility is the one score with headroom, and it maps directly to the fixes below.

100
SEO
100
Best practices
82
Accessibility
Fix first

Three high-impact issues

Each is concrete, evidenced and fixable — and each is money left on the table for a route selling into France and the Continent.

Critical · 01

No hreflang on a four-language site

Evidence

Fully translated FR / DE / NL pages exist and are indexable, yet every page returns 0 <link rel="alternate" hreflang> tags. The only hreflang attributes sit on the WPML language-switcher links, which Google ignores.

Impact

The translations are invisible as language alternates. Wrong-language pages can rank in France & the Continent and cross-language signals get diluted — on a route whose demand is heavily French.

The fix

Enable WPML hreflang output (reciprocal en/fr/de/nl + x-default) and add per-language sitemap entries.

Critical · 02

Weak HTTP security headers (35/100)

Evidence

Missing HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options and Referrer-Policy. Only Permissions-Policy is set.

Impact

Clickjacking, MIME-sniffing and downgrade exposure, plus weaker trust signals — the bar is higher when payments happen on the booking subdomain.

The fix

Add HSTS, nosniff, SAMEORIGIN, a strict Referrer-Policy and a scoped CSP at the server / CDN.

Critical · 03

Accessibility gaps (Lighthouse 82)

Evidence

CTA blocks render white text at 1.67:1 contrast (AA needs 4.5:1); the “Book now” button and all social icons have no accessible name; the route <select> has no label.

Impact

Excludes screen-reader and keyboard users, dents conversion through poor legibility, and carries EU Accessibility Act exposure for EU travel commerce.

The fix

Fix CTA contrast, add aria-labels / visible text to icon links, and label the search select.

Worth fixing

Medium-impact opportunities

Home & /fr/ titles overflow

79 and 85 characters — they truncate in results. Interior page titles are already well-sized.

Server response ~2.0s

A heavy Elementor + WPML stack. Page caching, trimmed CSS/JS and modern image formats would cut it sharply.

Structured-data gaps

No Service/Offer/TouristTrip for the route; Organization lacks sameAs & contactPoint. FAQPage is present but inert for a commercial site.

Incomplete Twitter Card

Open Graph is complete, but twitter:title/description/image are missing (they can inherit OG).

Already strong

What the current site gets right

  • http→https and www→non-www both 301; self-referencing canonicals
  • Clean index,follow everywhere with a valid sitemap index
  • Interior pages run 1,300–2,500 words; blog posts 3,000+
  • Blog uses Article + author schema — genuine E-E-A-T
  • Query-targeted interior titles and a single H1 per page
  • Full Open Graph set on every page
  • llms.txt present (80/100) — ahead of most sites on AI search
  • Lighthouse SEO 100 & Best Practices 100
Where this platform comes in

The brochure is strong. The booking journey is the opportunity.

The live site already hands off to a third-party booking engine and ships a route map and search widget — the exact surfaces this platform rebuilds natively, with a faster funnel, hreflang done right, and a real-time operator console behind it.

How this was measured

Evidence was gathered by scripted HTTP fetches, live header and redirect checks, XML-sitemap enumeration across ~100 URLs, and a real Chrome (Lighthouse) audit. Two limitations: Google's PageSpeed field & lab Core Web Vitals were rate-limited during this run, so performance is estimated from server response time and stack weight; and the Lighthouse navigation ran in snapshot mode. Everything else is directly verified. Scores are guidance, not a substitute for the underlying evidence.