SEO report

SEO report for www.ramboll.com

https://www.ramboll.com/ · checked Sun, 01 Nov 2026 19:20 GMT

✓ 31 Passed! 6 Warnings✗ 10 FailedAI readiness 75%

Fix these first

  1. H1 headingcritical

    No H1 heading.

    Fix: Use one H1 that states the page topic with its main keyword.

    See the details

  2. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

  3. HTML sizemedium

    444 kB of HTML – heavy for phones.

    Fix: Remove inline bloat, base64 images and unused markup.

    See the details

  4. Scripts & third partiesmedium

    44 script tag(s); files loaded from 1 other domain(s): assets-eu-01.kc-usercontent.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

    See the details

  5. Imagesmedium

    15 image(s).

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    See the details

  6. Tap-to-contactmedium

    No tel: or mailto: links.

    Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

    See the details

  7. Meta descriptionhigh

    64 characters, ~398px of ~990px.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

    See the details

  8. Server response (TTFB)high

    848 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

    Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to ramboll.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

  • ✓

    Status codecritical

    The page returned HTTP 200.

  • ✓

    Indexablecritical

    No noindex instruction – the page can appear in search.

  • ✓

    robots.txthigh

    robots.txt found.

    Googlebot is allowed to crawl this page.

  • ✓

    XML sitemaphigh

    Sitemap index found at https://www.ramboll.com/sitemap.xml listing 19 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-11-01.

  • ✓

    Canonical URLhigh

    Canonical: https://www.ramboll.com

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://ramboll.com/ → https://www.ramboll.com/

    A single redirect to your preferred address is normal; just make sure your own links use the final address.

  • ✓

    www / non-wwwmedium

    ramboll.com redirects to www.ramboll.com.

  • ✓

    hreflangmedium

    15 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

  • ✓

    Title tagcritical

    “Architecture, engineering and consultancy - Ramboll”

    About 464px of Google's ~580px desktop width.

  • !

    Meta descriptionhigh

    64 characters, ~398px of ~990px.

    Short – sell the click with a benefit and a call to action.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    No twitter:card tag.

  • ✗

    Faviconlow

    No favicon linked.

    Fix: Add a square favicon at least 48×48px.

  • ✓

    Languagelow

    lang="en"

Content quality 47%

Is there enough clear, useful text that matches what the page targets?

  • ✓

    Word countmedium

    473 words of main content (inside <main>).

    Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  • !

    Readabilitymedium

    Flesch reading ease 30 (fairly difficult), about 15 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    3 of 3 title keywords appear in the main content.

  • ✗

    H1 headingcritical

    No H1 heading.

    Fix: Use one H1 that states the page topic with its main keyword.

  • !

    Heading structuremedium

    16 headings for 473 words – a lot for the amount of text.

    Levels are in order.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  • ✗

    Text-to-code ratiolow

    1% of the HTML is visible text.

    Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 75%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

  • ✓

    AI crawler accesshigh

    Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

  • ✓

    Snippet controlshigh

    No snippet restrictions – search and AI answers can quote this page.

  • ✗

    llms.txtlow

    No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

    Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  • !

    Question-led contentmedium

    2 heading(s) phrased as questions, e.g. “How airflow modelling in cleanroom design improves performance”.

    Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  • ✓

    Entity clarityhigh

    Identified as: Organization, Person.

    2 official profile link(s) (sameAs).

  • ✗

    Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

  • ✓

    Trust pages (E-E-A-T)medium

    Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    2 JSON-LD block(s): Service, Organization, Person, ContactPoint.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 50%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

  • !

    Server response (TTFB)high

    848 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

    Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

  • ✗

    HTML sizemedium

    444 kB of HTML – heavy for phones.

    Fix: Remove inline bloat, base64 images and unused markup.

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✓

    Render-blocking resourceshigh

    0 blocking script(s) and 1 stylesheet(s) in <head>.

  • ✗

    Scripts & third partiesmedium

    44 script tag(s); files loaded from 1 other domain(s): assets-eu-01.kc-usercontent.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  • ✗

    Imagesmedium

    15 image(s).

    6 without width/height – can cause layout shift (CLS).

    4 image(s) after the first three aren't lazy-loaded.

    12 use WebP/AVIF or responsive srcset.

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  • ✓

    Cachinglow

    Cache-Control: s-maxage=300, stale-while-revalidate

  • i

    HTTP/3low

    Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 92%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✓

    HSTSmedium

    HSTS: max-age=63072000; includeSubDomains; preload

  • ✓

    Security headerslow

    Present: CSP, nosniff, Referrer-Policy, clickjacking protection.

  • ✗

    Server fingerprintlow

    X-Powered-By reveals “Next.js”.

    Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 80%

Usable on phones and by everyone – Google indexes the mobile version.

  • ✓

    Mobile viewportcritical

    viewport: width=device-width

  • ✓

    Image alt textmedium

    All 15 images have alt text.

  • ✗

    Tap-to-contactmedium

    No tel: or mailto: links.

    Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

  • i

    LocalBusiness markuphigh

    No LocalBusiness structured data.

  • i

    Contact details on pagemedium

    No phone number found.

    No postcode found (fine for service-area businesses).

  • i

    Map & directionslow

    No map or directions link.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.