SEO report for hubstack.net

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 hubstack.net…

Indexing & crawling 88%

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://rutledge-malloy-2.hubstack.net/sitemap.xml listing 1 sitemap.

  Declared in robots.txt.

  Most recent lastmod: 1970-01-01T00:00:00.000Z.

• ✗

  Canonical URLhigh

  No canonical tag.

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

  Read the guide: duplicate content

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.hubstack.net redirects to www.hubstack.net.

Search snippet & sharing 58%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Hub Stack”

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

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  28 characters, ~176px of ~990px.

  Short – sell the click with a benefit and a call to action.

  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.

  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

  No favicon linked.

  Fix: Add a square favicon at least 48×48px.

• ✓

  Languagelow

  lang="en"

Content quality 47%

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

• ✓

  Word countmedium

  527 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 45 (fairly difficult), about 18 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

  0 of 2 title keywords appear in the main content (missing: hub, stack).

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

  Find the phrases people search with the free keyword generator

  Read the guide: how to write SEO content

• !

  H1 headingcritical

  “What I Learned Selling Comedy Tickets On The Streets Of New York”

  The H1 shares no keywords with the title.

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

• !

  Heading structuremedium

  14 headings for 527 words – a lot for the amount of text.

  Levels are in order.

  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

  5% of the HTML is visible text.

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

AI search readiness 56%

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. “Why Your Team Needs a Weekly Metrics Review”.

  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

  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.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• ✗

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

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

Machine-readable facts for rich results and AI.

• ✗

  JSON-LD present & validhigh

  No JSON-LD structured data.

  Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

  Make valid code with the free schema generator

  Read the guide: schema markup

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 100%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  16 internal and 58 external links.

• ✓

  Anchor text qualitymedium

  No link text points to two different pages.

• ✓

  Broken links (sample)high

  Checked 3 internal link(s).

  No broken links found.

Performance 69%

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

• ✓

  Server response (TTFB)high

  517 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

  66 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

  0 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

  4 script tag(s); files loaded from 2 other domain(s): fonts.googleapis.com, images.unsplash.com.

• ✗

  Imagesmedium

  23 image(s).

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

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

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

  Read the guide: image SEO

• !

  Cachinglow

  Cache-Control: public, max-age=0

  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 “Express”.

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

Mobile & accessibility 83%

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

• ✓

  Mobile viewportcritical

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

• ✓

  Image alt textmedium

  All 23 images have alt text.

• ✓

  Form labelsmedium

  All 1 form fields are labelled.

• ✓

  Link nameslow

  Every link has a readable name.

• ✗

  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.

  Read the guide: mobile-friendly websites

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.