SEO report for developerstroop.com

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

  Declared in robots.txt.

  Most recent lastmod: 2026-10-22T20:27:42+00:00.

• ✓

  Canonical URLhigh

  Canonical: https://developerstroop.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.developerstroop.com redirects to developerstroop.com.

Search snippet & sharing 46%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  “DevelopersTroop - Website, App, SEO & Software Development Company”

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

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  230 characters, ~1425px 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.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

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

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

• ✓

  Word countmedium

  3,445 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 45 (fairly difficult), about 11 words per sentence.

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

  Read the guide: how to write SEO content

• ✓

  Topic focushigh

  6 of 6 title keywords appear in the main content.

• !

  H1 headingcritical

  “Pricing Packages”

  The H1 shares no keywords with the title.

  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

  93 headings for 3445 words – a lot for the amount of text.

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

  1 empty heading(s).

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

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

  7 heading(s) phrased as questions, e.g. “Why Trust DevelopersTroop ?”.

• ✓

  Entity clarityhigh

  Identified as: Organization, Person.

  2 official profile link(s) (sameAs).

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• ✓

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

  Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): Place, PostalAddress, Organization, ContactPoint, WebSite, SearchAction, ImageObject, WebPage, Person, BlogPosting.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

  Recommended but missing: Organization.logo.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  76 internal and 14 external links.

• ✗

  Anchor text qualitymedium

  No link text points to two different pages.

  3 link(s) with no text at all.

  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.

Performance 47%

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

• ✓

  Server response (TTFB)high

  248 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

  374 kB of HTML.

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

• ✓

  Compressionmedium

  Compressed with br.

• ✗

  Render-blocking resourceshigh

  4 blocking script(s) and 52 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

  65 script tag(s); files loaded from 5 other domain(s): fonts.googleapis.com, googletagmanager.com, maps.google.com, youtube.com, cdn-reach.hostinger.com.

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  74 image(s).

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

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

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

  Read the guide: image SEO

• !

  Cachinglow

  Cache-Control: no-store, no-cache, must-revalidate

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• ✓

  HTTP/3low

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

Security 46%

Visitor safety signals that browsers and Google check.

• !

  HTTPScritical

  2 file(s) load over insecure http:// (mixed content) – browsers may block them.

  Fix: Serve everything over HTTPS and update http:// file links.

  On WordPress: Ask your host to turn on a free SSL certificate, then in Settings → General change both addresses to start with https://.

  Read the guide: fixing a "Not secure" warning

• ✓

  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: CSP.

  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

  X-Powered-By reveals “PHP/8.3.36”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

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 74 images have alt text.

• ✗

  Form labelsmedium

  2 of 14 form field(s) have no label.

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

• ✗

  Link nameslow

  3 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✓

  Tap-to-contactmedium

  One-tap contact: phone and email.

Local SEO 50%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  On WordPress: Make the code with our free schema generator, then paste it into your site header with a free plugin such as WPCode.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✓

  Map & directionslow

  Links to or embeds a map.