Scanned sites / www.ostationcafe.ca / 2026-09-18-1537

www.ostationcafe.ca scan from 9/18/2026, 3:37:13 PM

Scan 2026-09-18-1537

Scanned 9/18/2026, 3:37:13 PM, finished 9/18/2026, 3:40:32 PM. Found with openstreetmap overpass

Site: https://www.ostationcafe.ca/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

71/ 100Needs work

On September 18, 2026 the Site Spider crawled 2 pages and 226 assets of www.ostationcafe.ca, starting from https://www.ostationcafe.ca/. It scored 71 out of 100, a result that needs work. 7 of 14 checks found something to fix, led by meta descriptions (2), headings (2), heavy assets (2); 7 checks passed. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
2
Assets fetched
226
Status
Completed
Checks with issues
7 of 14
  • Title tagsOK
    0 of 2 pages have title issues.
  • Meta descriptions2 issues
    2 of 2 pages have meta description issues.
  • Headings2 issues
    2 of 2 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • RedirectsOK
    1 redirecting URL, 0 of them chained.
  • Non-200 responsesOK
    3 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 2 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 12 image references have no alt attribute.
  • Heavy assets2 issues
    2 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage1 issue
    3 sitemaps listing 2 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
  • Thin content1 issue
    1 of 2 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1089 sites, median 82%, average 80%

www.ostationcafe.ca scores 71%, higher than 15% of the 1089 scanned sites. See the full ranking.

028550%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 0 sites48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 9 sites66%: 7 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 22 sites71%: 22 sites72%: 24 sites73%: 24 sites74%: 30 sites75%: 26 sites76%: 38 sites77%: 38 sites78%: 34 sites79%: 31 sites80%: 42 sites81%: 53 sites82%: 49 sites83%: 45 sites84%: 54 sites85%: 47 sites86%: 46 sites87%: 46 sites88%: 55 sites89%: 39 sites90%: 52 sites91%: 36 sites92%: 25 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 10 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 12 sites71% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your website has several SEO issues that need addressing to improve its health score. Key areas include meta descriptions, missing headings, and handling of non-200 responses. Implement the fixes below for better visibility and performance.

  1. 1

    Fix Non-200 Responses

    Why: 404 errors can hurt user experience and SEO.

    How: Identify why the assets are returning 404, and either remove the links or replace with correct URLs.

    Checks: status-codes

  2. 2

    Add Unique Meta Descriptions

    Why: Duplicate meta descriptions dilute relevance for search engines.

    How: Create unique descriptions for each page that accurately reflect their content.

    Checks: meta-descriptions

  3. 3

    Add Missing H1 Tags

    Why: H1 tags are critical for SEO and user navigation.

    How: Include a clear and concise H1 heading on both pages.

    Checks: headings

  4. 4

    Handle Redirects

    Why: Redirects can create confusion and slow down the user experience.

    How: Update the sitemap to directly link to the final URL without redirection.

    Checks: redirects

  5. 5

    Decrease Size of Heavy Assets

    Why: Larger assets slow page load which affects user experience.

    How: Optimize images and scripts such as compressing images or minifying CSS/JS.

    Checks: heavy-assets

  6. 6

    Address Orphan Page Issue

    Why: Orphan pages are hard for users to discover and may be ignored by search engines.

    How: Introduce internal links to the orphan page from relevant content across your site.

    Checks: orphan-pages

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

Your website has several security issues that need addressing, including missing critical headers for transport security and content security. Additionally, a vulnerable JavaScript library is in use, which could pose risks depending on its implementation. Immediate action on these findings will enhance visitor protection and overall security posture.

  • 0 high
  • 4 medium
  • 2 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS) HeaderMedium

    Why it matters: Without HSTS, users can be intercepted when accessing your site via HTTP.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP) HeaderMedium

    Why it matters: Without CSP, your site is vulnerable to various attacks as it allows arbitrary content to be loaded.

    Fix: Add the header: Content-Security-Policy: default-src 'self'.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows your site to be embedded in iframes, risking clickjacking attacks.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: jQuery 2.0.2 has known vulnerabilities which could be exploited.

    Fix: Upgrade jQuery to at least version 3.5.0 to patch existing vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This absence allows browsers to execute files based on their contents, which can be unsafe.

    Fix: Add the header: X-Content-Type-Options: nosniff.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: Without this header, sensitive URL information can be leaked to other sites when users navigate away.

    Fix: Add the header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

  7. 7

    Missing Permissions Policy HeaderInfo

    Why it matters: Not using this policy exposes your site to unnecessary browser feature access risks from injected scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=()

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.ostationcafe.ca/ → no strict-transport-security
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 2 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.

    • https://www.ostationcafe.ca/ → no content-security-policy
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no content-security-policy
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://www.ostationcafe.ca/ → no x-frame-options
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://www.ostationcafe.ca/ → no x-content-type-options
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no x-content-type-options
  • FoundReferrer policyLow

    No HTML page sends referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://www.ostationcafe.ca/ → no referrer-policy
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no referrer-policy
  • FoundPermissions policyInfo

    No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.

    • https://www.ostationcafe.ca/ → no permissions-policy
    • https://www.ostationcafe.ca/slides-category/home-slider/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 2.0.2. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 2.0.2 in https://www.ostationcafe.ca/wp-content/themes/bridge/js/plugins.js?ver=7.1.1: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 1 other domain without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • maps.googleapis.com (2 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 6 paths that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /admin/
    • Disallow: /includes/
    • Disallow: /config/
    • Disallow: /backup/
    • Disallow: /wp-admin/
    • Disallow: /wp-includes/
5 checks passed, 2 not applicable
  • OKHTTPS

    All 2 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

This report was produced by the DIY SEO Hub Site Spider crawling www.ostationcafe.ca from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

www.ostationcafe.ca scan 2026-09-18-1537 | DIY SEO Hub