SEO report

SEO report for www.fittingtributefunerals.com

https://www.fittingtributefunerals.com/ · checked Wed, 11 Nov 2026 06:33 GMT

✓ 28 Passed! 8 Warnings✗ 15 FailedAI readiness 63%Built with Squarespace

Fix these first

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

  1. Title tagcritical

    “Fitting Tribute: Green Burials, Home Funerals, Cremations at Green-Wood”

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

    On Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO title.

    See the details

  2. Mobile viewportcritical

    viewport: initial-scale=1

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

    See the details

  3. Render-blocking resourceshigh

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

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

    See the details

  4. HTTP → HTTPS redirecthigh

    http:// does not redirect to https://.

    Fix: 301-redirect all http:// requests to https://.

    See the details

  5. H1 headingcritical

    “Get in Touch”

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

    On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.

    See the details

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

  7. Freshness signalsmedium

    No published/updated date found.

    Fix: Show a 'last updated' date and add dateModified to your structured data.

    See the details

  8. Anchor text qualitymedium

    No link text points to two different pages.

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

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

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 found at http://www.fittingtributefunerals.com/sitemap.xml with 153 URLs.

    Declared in robots.txt.

    This page is NOT listed in it.

    Most recent lastmod: 2026-11-05.

  • !

    Canonical URLhigh

    Canonical: http://www.fittingtributefunerals.com

    Points to a DIFFERENT address – Google will probably index that one instead of this page.

    The canonical uses http:// although the page is on https://.

    Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  • ✓

    Redirectshigh

    1 redirect before the page loaded.

    https://fittingtributefunerals.com/ → https://www.fittingtributefunerals.com/

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

  • ✓

    www / non-wwwmedium

    fittingtributefunerals.com redirects to www.fittingtributefunerals.com.

Search snippet & sharing 46%

How the page looks in Google results and when shared.

  • ✗

    Title tagcritical

    “Fitting Tribute: Green Burials, Home Funerals, Cremations at Green-Wood”

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

    Repeated words: green.

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

    On Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO title.

  • !

    Meta descriptionhigh

    395 characters, ~2452px 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 Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO description.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    Twitter/X card: summary.

  • ✓

    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

    453 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 53 (fairly easy), about 15 words per sentence.

  • ✓

    Topic focushigh

    8 of 8 title keywords appear in the main content.

  • !

    H1 headingcritical

    “Get in Touch”

    The H1 shares no keywords with the title.

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

    On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.

  • !

    Heading structuremedium

    16 headings for 453 words – a lot for the amount of text.

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

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

  • ✗

    Text-to-code ratiolow

    2% of the HTML is visible text.

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

AI search readiness 63%

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

    Identified as: Organization, LocalBusiness.

    3 official profile link(s) (sameAs).

  • ✗

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

    3 JSON-LD block(s): WebSite, Organization, LocalBusiness.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

    Recommended but missing: Organization.name, Organization.url, Organization.logo, LocalBusiness.telephone, LocalBusiness.url.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 40%

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

  • ✓

    Server response (TTFB)high

    326 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

    190 kB of HTML.

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

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

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

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

  • ✗

    Scripts & third partiesmedium

    33 script tag(s); files loaded from 5 other domain(s): images.squarespace-cdn.com, use.typekit.net, assets.squarespace.com, definitions.sqspcdn.com, static1.squarespace.com.

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

  • ✗

    Imagesmedium

    20 image(s).

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

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

    The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.

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

  • ✗

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

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✗

    HTTP → HTTPS redirecthigh

    http:// does not redirect to https://.

    Fix: 301-redirect all http:// requests to https://.

  • ✗

    HSTSmedium

    HSTS: max-age=0

    max-age is under 6 months – browsers will forget it quickly.

    Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  • ✗

    Security headerslow

    Present: nosniff.

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

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

  • ✗

    Mobile viewportcritical

    viewport: initial-scale=1

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

  • ✓

    Image alt textmedium

    All 20 images have alt text.

  • ✓

    Form labelsmedium

    All 1 form fields are labelled.

  • ✓

    Tap-to-contactmedium

    One-tap contact: phone and email.

Local SEO 75%

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

  • !

    LocalBusiness markuphigh

    LocalBusiness markup includes: address, openingHoursSpecification.

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

    On Squarespace: Fill in Settings → Business information. For full markup, paste our schema generator's code into Settings → Advanced → Code Injection → Header (Core plan and above).

  • ✓

    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.

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.