SEO report

SEO report for fiveprogrammers.com

https://fiveprogrammers.com/ · checked Thu, 05 Nov 2026 02:46 GMT

✓ 29 Passed! 6 Warnings✗ 14 FailedAI readiness 69%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. 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

  2. Server response (TTFB)high

    1851 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

  3. Render-blocking resourceshigh

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

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

    See the details

  4. Title tagcritical

    “Five Programmers”

    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

  5. H1 headingcritical

    “”

    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

  6. Readabilitymedium

    Flesch reading ease 24 (difficult), about 16 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

    See the details

  7. Anchor text qualitymedium

    Same text used for different pages: “five programmers”.

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

    See the details

  8. Scripts & third partiesmedium

    55 script tag(s); files loaded from 4 other domain(s): googletagmanager.com, fonts.googleapis.com, devfox.cymolthemes.com, google.com.

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

    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 fiveprogrammers.com…

Indexing & crawling 100%

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://fiveprogrammers.com/sitemap_index.xml listing 10 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-11-04T05:56:27+00:00.

  • ✓

    Canonical URLhigh

    Canonical: https://fiveprogrammers.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.fiveprogrammers.com redirects to fiveprogrammers.com.

Search snippet & sharing 67%

How the page looks in Google results and when shared.

  • !

    Title tagcritical

    “Five Programmers”

    About 164px 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.

    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

    164 characters, ~1044px 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.

    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.

    Twitter/X card: summary_large_image.

  • ✓

    Faviconlow

    Favicon linked (Google shows it next to results).

  • ✓

    Languagelow

    lang="en-US"

Content quality 57%

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

  • ✓

    Word countmedium

    702 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 24 (difficult), about 16 words per sentence.

    Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  • ✓

    Topic focushigh

    2 of 2 title keywords appear in the main content.

  • !

    H1 headingcritical

    “”

    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

    35 headings for 702 words – a lot for the amount of text.

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

    3 empty heading(s).

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

  • ✗

    Text-to-code ratiolow

    3% of the HTML is visible text.

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

AI search readiness 69%

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

    3 heading(s) phrased as questions, e.g. “Want to Develop Apps for your Business ?”.

  • ✗

    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 and contact; missing 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 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 25%

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

  • ✗

    Server response (TTFB)high

    1851 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

    328 kB of HTML.

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

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

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

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

  • ✗

    Scripts & third partiesmedium

    55 script tag(s); files loaded from 4 other domain(s): googletagmanager.com, fonts.googleapis.com, devfox.cymolthemes.com, google.com.

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

  • ✗

    Imagesmedium

    8 image(s).

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

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

    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.

    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.

  • ✓

    HTTP/3low

    Server advertises HTTP/3 (faster on mobile networks).

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: Permissions-Policy.

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

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

  • ✓

    Mobile viewportcritical

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

  • ✓

    Image alt textmedium

    All 8 images have alt text.

  • ✗

    Form labelsmedium

    4 of 5 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✓

    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.