SEO report for java-forum.org

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 java-forum.org…

Indexing & crawling 79%

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://java-forum.org/sitemap.xml listing 3 sitemaps.

  Not declared in robots.txt.

  Most recent lastmod: 2026-11-09T05:38:37+00:00.

  Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• !

  Canonical URLhigh

  Canonical: https://www.java-forum.org/

  Points to a DIFFERENT address – Google will probably index that one instead of this page.

  The canonical uses the other www / non-www version of your domain.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✗

  www / non-wwwmedium

  Both www.java-forum.org and java-forum.org 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 50%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “JAVA Forum | Hilfe für Java Entwickler & Informatik-Studenten”

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

  Repeated words: java.

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

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  157 characters, ~1005px of ~990px.

  Long – Google will probably truncate it.

  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.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• !

  Open Graph & social cardsmedium

  Open Graph title or image missing.

  No twitter:card tag.

  Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

  Make the tags with the free Open Graph generator

  Read the guide: does social media help SEO?

• ✗

  Faviconlow

  No favicon linked.

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

• ✓

  Languagelow

  lang="de-DE"

Content quality 88%

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

• ✓

  Word countmedium

  1,181 words of main content (menus and footer excluded).

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

• i

  Readabilitymedium

  Reading-ease scores only work for English; this page is lang="de-DE".

• ✓

  Topic focushigh

  7 of 7 title keywords appear in the main content.

• ✓

  H1 headingcritical

  “JAVA Forum | Hilfe für Java Entwickler & Informatik-Studenten”

• !

  Heading structuremedium

  43 headings for 1181 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.

  Read the guide: the on-page SEO checklist

• !

  Text-to-code ratiolow

  7% of the HTML is visible text.

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

AI search readiness 56%

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.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✗

  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.

  Read the guide: how to write SEO content

• ✗

  Entity clarityhigh

  No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

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

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• !

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

  Links found to contact and privacy; missing about.

  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, SearchAction, EntryPoint.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 83%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  191 internal and 2 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “g”, “definitive quelle fuer die lebenszeit von java objekten?”, “l”, “z”.

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

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

  3 link(s) point to a redirect – link to the final address instead.

• !

  Internal nofollowlow

  5 internal link(s) are nofollow, so search engines may not follow them.

  Fix: Remove rel="nofollow" from links to your own pages.

Performance 87%

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

• ✓

  Server response (TTFB)high

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

• ✓

  HTML sizemedium

  123 kB of HTML.

• ✓

  Compressionmedium

  Compressed with gzip.

• !

  Render-blocking resourceshigh

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

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

  Read the guide: Core Web Vitals

• ✓

  Scripts & third partiesmedium

  10 script tag(s); files loaded from 3 other domain(s): googletagmanager.com, unpkg.com, gravatar.com.

• ✓

  Imagesmedium

  20 image(s).

  All images reserve their space.

  12 use WebP/AVIF or responsive srcset.

• !

  Cachinglow

  Cache-Control: private, no-cache, 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 75%

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.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: nosniff.

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

  Read the guide: the technical SEO checklist

• ✓

  Server fingerprintlow

  No X-Powered-By header (server: cloudflare).

Mobile & accessibility 83%

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

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1, viewport-fit=cover

• ✓

  Image alt textmedium

  All 20 images have alt text.

• ✓

  Form labelsmedium

  All 4 form fields are labelled.

• ✓

  Link nameslow

  Every link has a readable name.

• ✗

  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.

  Read the guide: mobile-friendly websites

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.