SEOWebsiteTool
66Grade C

supplyrisktool.edeka

Home

5 failed · 7 warnings · 17 passed

Audited Fri, 07 Aug 2026 23:16:05 GMT · https://supplyrisktool.edeka/

Meta & Head

11.1/25

Title, description, canonical, social tags — what search engines read first.

  • Meta descriptionhigh impactlow effort

    No meta description found

    The meta description is your ad copy in search results; without one, engines pull an arbitrary snippet from the page, which usually reads poorly and costs you clicks. Add <meta name="description" content="..."> with 70–160 characters that summarize the page and give a concrete reason to click — what the visitor gets plus a differentiator (free, instant, no signup). Write a unique description per page: one duplicated across the site is treated much like a missing one.

  • Page allows indexinghigh impactlow effort

    <meta name="robots" content="NOODP,NOINDEX">

    This page tells search engines not to index it, so it can never rank — every other optimization is wasted while this tag is present. If that's unintentional, remove the noindex directive (or the whole robots meta tag) and request re-indexing in Google Search Console. A common pitfall: staging noindex tags shipped to production during a launch.

  • Character encoding declaredlow impactlow effort

    No character encoding declaration found

    Without a declared character encoding, browsers have to guess how to decode your text; a wrong guess garbles apostrophes, accents, and currency symbols, and the guessing itself can delay rendering. Add <meta charset="utf-8"> as the very first element inside <head> — browsers only scan the opening bytes of the document for it. Also confirm your server isn't sending a conflicting charset in the Content-Type header, since a mismatch produces exactly the garbled text you're trying to prevent.

  • Title taghigh impactlow effort

    <title> is "Home" (4 characters)

    Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.

  • Open Graph tagsmedium impactlow effort

    Missing Open Graph tags: og:description

    Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:description tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.

  • Twitter card taglow impactlow effort

    No twitter:card meta tag found

    X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.

3 passing checks
  • Canonical URLCanonical href is "https://supplyrisktool.edeka"
  • Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
  • FaviconA <link rel="icon"> is present

Content & Structure

18.8/25

Headings, copy depth, images, structured data, internal linking.

  • Word counthigh impactlow effort

    238 words of visible text

    Under 300 words, search engines typically classify a page as thin content, and thin pages rarely rank for anything competitive. Decide which query this page should answer, then write substantive copy — aim for 600+ words covering what it is, how it works, common questions, and concrete examples. If the page genuinely has nothing more to say, merge it into a stronger related page with a 301 redirect rather than padding it with filler that helps no one.

  • Structured data (JSON-LD)medium impactmedium effort

    No JSON-LD structured data blocks found

    Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.

6 passing checks
  • Single H1 heading1 h1 found: "Supply Risk ToolRisiken kennen, Liefer&shy;ketten nachhaltig gestalten"
  • Heading hierarchy5 headings in order without skipped levels
  • Image alt text6 of 6 images have alt text
  • HTML lang attribute<html lang="de">
  • JavaScript-dependent contentvisible text ~4598 chars in the initial HTML
  • Internal linking11 internal, 1 external links

Technical

19.3/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • robots.txt present and permissivemedium impactlow effort

    robots.txt disallows all crawling

    Your robots.txt contains a blanket "Disallow: /", which tells every search engine to stay out — your pages cannot be crawled and will not rank while this rule is in place. This is usually a staging-environment setting that shipped to production by accident. Replace the blanket rule with targeted ones, e.g. "Disallow: /admin/" for areas you genuinely want excluded, or remove it entirely if everything should be crawlable. Note that Disallow only blocks crawling, not indexing — use a noindex meta tag for pages you want out of results.

  • Fast time to first bytehigh impactmedium effort

    1354 ms

    Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.

  • XML sitemap availablemedium impactlow effort

    sitemap.xml is valid but robots.txt does not reference it

    Your sitemap is valid, but robots.txt never mentions it, so crawlers you haven't manually notified may never find it — the robots.txt reference is the universal discovery mechanism. Add one line to robots.txt: "Sitemap: https://www.example.com/sitemap.xml", using the full absolute URL (a relative path is invalid here). The line can go anywhere in the file, and you can list several sitemaps. Also submit it in Google Search Console to get indexing-coverage reporting on top of discovery.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

8 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • Short redirect chainno redirects; URL resolves directly
  • Reasonable HTML size15.9 KB
  • Missing pages return 404missing paths return HTTP 404/410
  • www and non-www resolve consistentlywww and non-www converge on the same host
  • HTML5 doctype<!DOCTYPE html> present

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for supplyrisktool.edeka

More “s” sitesRecent audits

supplyrisktool.edeka — SEO Score 66/100 (Grade C) | SEO Website Tool