SEO report

SEO report for stackby.com

https://stackby.com/ · checked Thu, 05 Nov 2026 00:32 GMT

✓ 27 Passed! 6 Warnings✗ 13 FailedAI readiness 63%

Fix these first

  1. H1 headingcritical

    No H1 heading.

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

    See the details

  2. Topic focushigh

    0 of 5 title keywords appear in the main content (missing: code, online, spreadsheet, databases, work).

    Fix: Use your main title phrases naturally in the opening paragraph and headings.

    See the details

  3. Render-blocking resourceshigh

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

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

    See the details

  4. Word countmedium

    0 words of main content (menus and footer excluded).

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

    See the details

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

  6. Freshness signalsmedium

    No published/updated date found.

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

    See the details

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

    Links found to contact; missing about 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.

    See the details

  8. HTML sizemedium

    980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

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

    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 stackby.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://stackby.com/sitemap.xml listing 7 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-11-03.

  • ✓

    Canonical URLhigh

    Canonical: https://stackby.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.stackby.com redirects to stackby.com.

  • ✓

    hreflangmedium

    1 hreflang link(s).

    All language codes are valid.

Search snippet & sharing 88%

How the page looks in Google results and when shared.

  • ✓

    Title tagcritical

    “No-code online spreadsheet and databases for work | Stackby”

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

  • !

    Meta descriptionhigh

    163 characters, ~1033px 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.

  • ✓

    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"

Content quality 8%

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

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

    /llms.txt found.

  • ✗

    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, SoftwareApplication.

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

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): Organization, SoftwareApplication, Offer, ImageObject, WebSite, SearchAction, EntryPoint.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 43%

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

  • !

    Server response (TTFB)high

    1167 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

    980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

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

  • ✓

    Compressionmedium

    Compressed with gzip.

  • ✗

    Render-blocking resourceshigh

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

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

  • !

    Scripts & third partiesmedium

    16 script tag(s); files loaded from 11 other domain(s): stackbybucketprod.s3-ap-southeast-1.amazonaws.com, use.fontawesome.com, fonts.googleapis.com, fonts.bunny.net, stackpath.bootstrapcdn.com, code.jquery.com….

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

  • ✓

    Imagesmedium

    1 image(s).

    All images reserve their space.

    0 use WebP/AVIF or responsive srcset.

  • ✗

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

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: nosniff, Referrer-Policy, clickjacking protection.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✗

    Server fingerprintlow

    X-Powered-By reveals “Express”.

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

Mobile & accessibility 80%

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

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1, shrink-to-fit=no

  • ✓

    Image alt textmedium

    All 1 images have alt text.

  • ✗

    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.