SEO report

SEO report for 2023.java2days.com

https://2023.java2days.com/ · checked Thu, 05 Nov 2026 01:26 GMT

✓ 25 Passed! 2 Warnings✗ 19 FailedAI readiness 50%Built with WordPress

Fix these first

Your site is built with WordPress. The steps below say where each setting is, and our WordPress SEO guide walks through the rest.

  1. Title tagcritical

    “Java2Days 2023 – Meet and Learn From the Top Gurus in the Java Community”

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

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

    See the details

  2. XML sitemaphigh

    No XML sitemap found at /sitemap.xml or in robots.txt.

    Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

    On WordPress: WordPress makes one at /wp-sitemap.xml, and Yoast or Rank Math make /sitemap_index.xml. Submit it in Google Search Console.

    See the details

  3. Meta descriptionhigh

    No meta description – Google will pick text from the page.

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

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

    See the details

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

    See the details

  5. JSON-LD present & validhigh

    No JSON-LD structured data.

    Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

    See the details

  6. Render-blocking resourceshigh

    11 blocking script(s) and 17 stylesheet(s) in <head>.

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

    See the details

  7. H1 headingcritical

    61 H1 headings – one clear H1 is best practice.

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

    On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.

    See the details

  8. Open Graph & social cardsmedium

    Open Graph title or image missing.

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

    On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.

    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 2023.java2days.com…

Indexing & crawling 81%

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

    No robots.txt found (HTTP 404) – crawlers may read everything.

    Googlebot is allowed to crawl this page.

    Fix: Add a robots.txt that allows crawling and lists your sitemap.

  • ✗

    XML sitemaphigh

    No XML sitemap found at /sitemap.xml or in robots.txt.

    Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

    On WordPress: WordPress makes one at /wp-sitemap.xml, and Yoast or Rank Math make /sitemap_index.xml. Submit it in Google Search Console.

  • ✓

    Canonical URLhigh

    Canonical: https://2023.java2days.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://java2days.com/ → https://2023.java2days.com/

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

  • ✓

    www / non-wwwmedium

    www.2023.java2days.com isn't in use (HTTP 526).

Search snippet & sharing 17%

How the page looks in Google results and when shared.

  • ✗

    Title tagcritical

    “Java2Days 2023 – Meet and Learn From the Top Gurus in the Java Community”

    About 706px of Google's ~580px desktop width – it will probably be cut off.

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

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

  • ✗

    Meta descriptionhigh

    No meta description – Google will pick text from the page.

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

    On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

  • ✗

    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.

    On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="en-US"

Content quality 70%

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

  • ✓

    Word countmedium

    12,837 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.

  • ✓

    Readabilitymedium

    Flesch reading ease 57 (fairly easy), about 5 words per sentence.

  • ✓

    Topic focushigh

    7 of 7 title keywords appear in the main content.

  • !

    H1 headingcritical

    61 H1 headings – one clear H1 is best practice.

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

    On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.

  • ✗

    Heading structuremedium

    293 headings for 12837 words.

    60 skipped level(s), e.g. H2 → H4.

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

  • ✓

    Text-to-code ratiolow

    18% of the HTML is visible text.

AI search readiness 50%

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

    6 heading(s) phrased as questions, e.g. “Design for GitOps: What have we learned from Everything-as-code at sca”.

  • ✗

    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.

  • ✗

    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 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 0%

Machine-readable facts for rich results and AI.

Performance 33%

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

  • ✓

    Server response (TTFB)high

    218 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

    459 kB of HTML – heavy for phones.

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

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

    11 blocking script(s) and 17 stylesheet(s) in <head>.

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

  • ✗

    Scripts & third partiesmedium

    31 script tag(s); files loaded from 5 other domain(s): fonts.googleapis.com, facebook.com, 2021.java2days.com, youtube.com, java2days.com.

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

  • ✗

    Imagesmedium

    314 image(s).

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

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

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

    On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.

  • ✗

    Cachinglow

    No Cache-Control header.

    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 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=15768000

  • ✗

    Security headerslow

    Present: none.

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

  • ✓

    Server fingerprintlow

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

Mobile & accessibility 70%

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

  • ✓

    Mobile viewportcritical

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

  • ✗

    Image alt textmedium

    120 of 314 images have no alt attribute.

    Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

    On WordPress: Media → Library: click each image and fill in Alternative Text. For images already on a page, select the image block and fill in Alternative text in the sidebar.

  • ✓

    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.