SEO report

SEO report for developers.de

https://developers.de/ · checked Wed, 11 Nov 2026 08:18 GMT

✓ 27 Passed! 8 Warnings✗ 11 FailedAI readiness 59%Built with Ghost

Fix these first

  1. Render-blocking resourceshigh

    2 blocking script(s) and 9 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

    See the details

  2. Title tagcritical

    “DEVELOPERS.DE”

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

    See the details

  3. H1 headingcritical

    5 H1 headings – one clear H1 is best practice.

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

    See the details

  4. www / non-wwwmedium

    Both www.developers.de and developers.de load without redirecting – Google may see duplicate sites.

    Fix: Pick one version (with or without www) and 301-redirect the other to it.

    See the details

  5. Question-led contentmedium

    No headings phrased as questions.

    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.

    See the details

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

    Links found to privacy; missing about and contact.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

    See the details

  7. Anchor text qualitymedium

    Same text used for different pages: “read more”.

    Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

    See the details

  8. HSTSmedium

    No Strict-Transport-Security header.

    Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

    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 developers.de…

Indexing & crawling 92%

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://developers.de/sitemap.xml listing 4 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-10-27T13:59:22.000Z.

  • ✓

    Canonical URLhigh

    Canonical: https://developers.de/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✗

    www / non-wwwmedium

    Both www.developers.de and developers.de load without redirecting – Google may see duplicate sites.

    Fix: Pick one version (with or without www) and 301-redirect the other to it.

Search snippet & sharing 71%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “DEVELOPERS.DE”

    About 169px of Google's ~580px desktop width – short; use the space.

    Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  • ✓

    Meta descriptionhigh

    88 characters, ~587px of ~990px.

    Good length.

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

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    Twitter/X card: summary_large_image.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✗

    Languagelow

    No lang attribute on <html>.

    Fix: Add lang="en-GB" (or your language) to the <html> tag.

Content quality 79%

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

  • ✓

    Word countmedium

    454 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 70 (plain English), about 11 words per sentence.

  • i

    Topic focushigh

    No title keywords to compare.

  • !

    H1 headingcritical

    5 H1 headings – one clear H1 is best practice.

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

  • ✓

    Heading structuremedium

    5 headings for 454 words.

    Levels are in order.

  • ✓

    Text-to-code ratiolow

    11% of the HTML is visible text.

AI search readiness 59%

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

    No headings phrased as questions.

    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.

    No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✓

    Freshness signalsmedium

    The page shows when it was published or last updated.

  • ✗

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

    Links found to privacy; missing about and contact.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): Website, Organization, ImageObject, WebPage.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 53%

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

  • !

    Server response (TTFB)high

    1066 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

    26 kB of HTML.

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

    2 blocking script(s) and 9 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  • !

    Scripts & third partiesmedium

    19 script tag(s); files loaded from 2 other domain(s): cdnjs.cloudflare.com, developersde.blob.core.windows.net.

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

  • !

    Imagesmedium

    1 image(s).

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

    0 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: public, max-age=0

    Fix: Set Cache-Control so browsers and CDNs can reuse the page.

  • 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 67%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✗

    HSTSmedium

    No Strict-Transport-Security header.

    Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  • ✗

    Security headerslow

    Present: none.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✗

    Server fingerprintlow

    X-Powered-By reveals “Express, ASP.NET”.

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

Mobile & accessibility 90%

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

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1.0

  • ✓

    Image alt textmedium

    All 1 images have alt text.

  • ✓

    Tap-to-contactmedium

    One-tap contact: email.

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.

  • ✓

    Contact details on pagemedium

    No phone number found.

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

    An email link is shown.

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