SEO report

SEO report for programresource.net

https://programresource.net/ · checked Wed, 11 Nov 2026 01:53 GMT

✓ 23 Passed! 8 Warnings✗ 16 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

    “Program Resource | 開発者向け各種コード、アルゴリズム、リソース情報ライブラリ もしくはねふぁの覚え書き”

    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. H1 headingcritical

    15 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

  3. Mobile viewportcritical

    No viewport meta tag – the page won't fit phones.

    Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

    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. Server response (TTFB)high

    1869 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

  7. Render-blocking resourceshigh

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

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

    See the details

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

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 programresource.net…

Indexing & crawling 94%

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://programresource.net/sitemap.xml listing 3 sitemaps.

    Not declared in robots.txt.

    Most recent lastmod: 2025-06-12T13:37:47+00:00.

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

    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://programresource.net/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.programresource.net isn't in use (HTTP 526).

  • ✓

    hreflangmedium

    3 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 46%

How the page looks in Google results and when shared.

  • ✗

    Title tagcritical

    “Program Resource | 開発者向け各種コード、アルゴリズム、リソース情報ライブラリ もしくはねふぁの覚え書き”

    About 646px 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

    34 characters, ~198px 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.

    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 and image set.

    No twitter:card tag.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="ja"

Content quality 42%

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

  • !

    Word countmedium

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

    Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  • i

    Readabilitymedium

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

  • ✓

    Topic focushigh

    5 of 6 title keywords appear in the main content (missing: program).

  • ✗

    H1 headingcritical

    15 H1 headings – one clear H1 is best practice.

    The H1 is empty.

    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

    22 headings for 357 words – a lot for the amount of text.

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

    1 empty heading(s).

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

  • !

    Text-to-code ratiolow

    6% of the HTML is visible text.

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

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

    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

    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

    The page shows when it was published or last updated.

  • ✗

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

    Links found to about; missing contact and privacy.

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

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

  • ✗

    Server response (TTFB)high

    1869 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

    76 kB of HTML.

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

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

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

  • !

    Scripts & third partiesmedium

    18 script tag(s); files loaded from 1 other domain(s): stats.wp.com.

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

  • !

    Imagesmedium

    22 image(s).

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

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

  • ✗

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

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

  • ✗

    Mobile viewportcritical

    No viewport meta tag – the page won't fit phones.

    Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  • ✓

    Image alt textmedium

    All 22 images have alt text.

  • ✓

    Form labelsmedium

    All 3 form fields are labelled.

  • ✗

    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.