Scanned sites / www.ostationcafe.ca / 2026-10-23-2323

www.ostationcafe.ca scan from 2026-10-23 23:23:47 UTC DR 7

A newer scan exists. See the latest report for www.ostationcafe.ca.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-23-2323

Scanned 2026-10-23 23:23:47 UTC, finished 2026-10-24 00:37:01 UTC. 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 October 23, 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 33 checks found something to fix, led by meta descriptions (2), headings (2), indexability (1); 18 checks passed. Most of the points went to meta descriptions (−8), headings (−6), indexability (−5). 8 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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 33
CoverageComplete crawl

228 of 270 discovered URLs were fetched, 42 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 1 link destination on other sites was checked.

  • Title tagsOK
    0 of 2 pages have title issues.
  • Meta descriptions2 issues
    2 of 2 pages have meta description issues.
    −8 points
  • Headings2 issues
    2 of 2 pages have heading issues.
    −6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesOK
    0 destinations answered with an error, of 1 destination checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses3 noted
    3 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 2 indexable pages have indexability warnings.
    −5 points
  • Image alt textOK
    0 of 12 image references have no alt attribute.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 226 fetched assets.
    −1.2 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −2 points
  • Sitemap coverage1 issue
    3 sitemaps listing 2 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −3 points
  • Internal link countsOK
    Internal link counts for 2 pages; none is a dead end or buried.
  • Thin content1 issue
    1 of 2 pages have fewer than 200 words.
    −4 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 2 page URLs are plain lowercase addresses without parameters.
  • Canonicals1 noted
    1 of 2 pages have a canonical worth checking.
  • Robots directives2 noted
    2 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 2 pages could use the title, heading and snippet space better.
  • Image weight and alt length1 noted
    1 image over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 2 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    2 of 2 indexable pages carry structured data: WebPage (2). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 2 pages with enough text to compare.
  • Soft 404sOK
    None of 2 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions1 noted
    1 of 1 linked page are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 228 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 2 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling5 noted
    5 words an English dictionary does not know, on 2 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2344 sites, median 79%, average 78%

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

0581160%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 4 sites52%: 10 sites53%: 7 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 69 sites72%: 71 sites73%: 70 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 106 sites81%: 105 sites82%: 116 sites83%: 102 sites84%: 107 sites85%: 88 sites86%: 70 sites87%: 73 sites88%: 59 sites89%: 65 sites90%: 36 sites91%: 46 sites92%: 39 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 5 sites99%: 2 sites100%: 68 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 site has several technical issues that need attention, including missing meta descriptions and headings, among others. Implementing these recommended fixes will enhance your SEO performance.

  1. 1

    Add H1 Tags

    Why: Missing H1 tags prevent proper content indexing.

    How: Add an H1 tag to each page's HTML structure.

    Checks: headings

  2. 2

    Fix Meta Descriptions

    Why: Duplicate meta descriptions dilute search visibility.

    How: Create unique meta descriptions for each page to reflect its content.

    Checks: meta-descriptions

  3. 3

    Add Canonical Tags

    Why: Missing canonical tags can lead to duplicate content issues.

    How: Include a canonical link in the page header linking to the preferred version.

    Checks: indexability

  4. 4

    Reduce Asset Size

    Why: Large assets slow down page load times and affect user experience.

    How: Optimize or remove large stylesheets and scripts from pages.

    Checks: heavy-assets

  5. 5

    Establish Internal Links

    Why: Orphan pages may not be crawled or indexed properly.

    How: Add internal links pointing to the orphan page from other relevant pages.

    Checks: orphan-pages

  6. 6

    Ensure Sitemap Accessibility

    Why: Sitemap URLs not reachable without internal links may hinder SEO.

    How: Link the sitemap-only URLs within the site structure.

    Checks: sitemap-coverage

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

This review highlights security vulnerabilities related to response headers and outdated libraries on your website. Implementing the recommended changes will improve your site's security posture significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be susceptible to man-in-the-middle attacks by accessing your site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of a CSP allows unrestricted resource loading, increasing XSS risk.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Lack of this header permits clickjacking attacks where your content can be embedded into malicious sites.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibrariesMedium

    Why it matters: Using a vulnerable version (jQuery 2.0.2) may allow attacks like XSS and prototype pollution.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Not using this header can lead browsers to interpret files in unwanted ways, causing potential security risks.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive information in URLs might leak when users navigate away from your site.

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

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not using this header may allow unnecessary access to browser features like camera and microphone.

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

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

Sites scoring near www.ostationcafe.ca

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.ostationcafe.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.ostationcafe.ca?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming www.ostationcafe.ca. Removal needs no account and no proof of purchase.