SEO report for www.loveyourpostcode.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 loveyourpostcode.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://www.loveyourpostcode.com/sitemap_index.xml listing 2 sitemaps.

  Declared in robots.txt.

  Most recent lastmod: 2026-04-28T03:21:01+00:00.

• ✓

  Canonical URLhigh

  Canonical: https://www.loveyourpostcode.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://loveyourpostcode.com/ → https://www.loveyourpostcode.com/

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

• ✓

  www / non-wwwmedium

  loveyourpostcode.com redirects to www.loveyourpostcode.com.

Search snippet & sharing 83%

How the page looks in Google results and when shared.

• ✓

  Title tagcritical

  “Letting & Estate Agents in Birmingham | Love Your Postcode™”

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

• ✓

  Meta descriptionhigh

  111 characters, ~687px of ~990px.

  Good length.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

• !

  Open Graph & social cardsmedium

  Open Graph title or image missing.

  Twitter/X card: summary_large_image.

  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.

  Make the tags with the free Open Graph generator

  Read the guide: does social media help SEO?

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✗

  Languagelow

  No lang attribute on <html>.

  Fix: Add lang="en-GB" (or your language) to the <html> tag.

Content quality 83%

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

• ✓

  Word countmedium

  749 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 47 (fairly difficult), about 19 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

  “Award-Winning Letting & Estate Agents in Birmingham”

• !

  Heading structuremedium

  24 headings for 749 words – a lot for the amount of text.

  Levels are in order.

  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

  6% of the HTML is visible text.

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

AI search readiness 81%

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

  1 heading(s) phrased as questions, e.g. “Traditional or modern?”.

  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

  Identified as: LocalBusiness, RealEstateAgent.

  6 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 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

  6 JSON-LD block(s): WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, realEstateAgent, PostalAddress, RealEstateAgent, GeoCoordinates.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

  Recommended but missing: LocalBusiness.url.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  52 internal and 12 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “selling”, “lettings”.

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

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

Performance 31%

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

• !

  Server response (TTFB)high

  1563 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

  78 kB of HTML.

• i

  Compressionmedium

  Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

• ✗

  Render-blocking resourceshigh

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

  38 script tag(s); files loaded from 11 other domain(s): code.jquery.com, cdnjs.cloudflare.com, unpkg.com, fonts.googleapis.com, use.fontawesome.com, googletagmanager.com….

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  32 image(s).

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

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

  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.

• 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 67%

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

  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/7.4.33, PleskLin”.

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

Mobile & accessibility 46%

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

• !

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1, user-scalable=no – blocks pinch-zoom

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

  Read the guide: mobile-friendly websites

• !

  Image alt textmedium

  1 of 32 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.

  Read the guide: image SEO

• ✗

  Form labelsmedium

  7 of 8 form field(s) have no label.

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

• ✗

  Link nameslow

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

Local SEO 83%

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

• ✓

  LocalBusiness markuphigh

  LocalBusiness markup includes: address, telephone, geo, openingHoursSpecification, url.

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  A UK postcode is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist