Scanned sites / www.ostationcafe.ca / 2026-09-19-0657
www.ostationcafe.ca scan from 9/19/2026, 6:57:05 AM
Scan 2026-09-19-0657
Scanned 9/19/2026, 6:57:05 AM, finished 9/19/2026, 7:03:06 AM. 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.
On September 19, 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 tagsOK0 of 2 pages have title issues.
- Meta descriptions2 issues2 of 2 pages have meta description issues.
- Headings2 issues2 of 2 pages have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK1 redirecting URL, 0 of them chained.
- Non-200 responsesOK3 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability1 issue1 of 2 indexable pages have indexability warnings.
- Image alt textOK0 of 12 image references have no alt attribute.
- Heavy assets2 issues2 assets larger than 500 KB among the 100 heaviest.
- Orphan pages1 issue1 page have no internal links pointing at them.
- Sitemap coverage1 issue3 sitemaps listing 2 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
- Thin content1 issue1 of 2 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1101 sites, median 82%, average 80%
www.ostationcafe.ca scores 71%, higher than 15% of the 1101 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site requires immediate attention to improve SEO and user experience. Focus on fixing redirects, non-200 status codes, and meta descriptions for better indexing and content visibility.
- 1
Fix Redirects
Why: One URL is redirecting unnecessarily, affecting user experience.
How: Change the sitemap URL from https://www.ostationcafe.ca/sitemap.xml to point directly to the correct URL without redirection.
Checks: redirects
- 2
Resolve Non-200 Status Codes
Why: Three URLs are returning non-200 responses, causing potential access issues.
How: Remove or replace the 404 URLs: https://www.ostationcafe.ca/wp-content/themes/bridge/css/img/box_image_shadow.png and https://www.ostationcafe.ca/wp-content/themes/bridge/images/prettyPhoto/facebook/default_thumbnail.gif.
Checks: status-codes
- 3
Update Meta Descriptions
Why: Duplicate meta descriptions can harm indexing and search rankings.
How: Create unique meta descriptions for each page instead of using the same one for both.
Checks: meta-descriptions
- 4
Add Heading Tags (H1)
Why: Lack of H1 headings can affect SEO and accessibility.
How: Add a relevant H1 tag on both pages to improve structure.
Checks: headings
- 5
Improve Indexability
Why: The absence of a canonical tag may cause indexing issues.
How: Add a canonical tag to the slides-category/home-slider page to designate the preferred version.
Checks: indexability
- 6
Reduce Heavy Assets
Why: Large assets can slow down page load times, impacting user experience.
How: Optimize the image at https://www.ostationcafe.ca/wp-content/uploads/2018/10/coffee_beans_bg.jpg to reduce its size.
Checks: heavy-assets
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 crawlYour website has several security vulnerabilities that need urgent attention. Implementing the recommended security headers and upgrading vulnerable libraries will help protect your site and its users from potential attacks. These improvements will enhance your site's security posture significantly.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Lack of HSTS allows interception of initial requests over HTTP.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of CSP allows unrestricted loading of scripts and styles, increasing XSS risk.
Fix: Add the header: Content-Security-Policy: default-src 'self';
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without this header, your site is vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: jQuery 2.0.2 contains known vulnerabilities that may be exploited depending on usage.
Fix: Upgrade jQuery to version 3.5.0 or later.
Evidence: Vulnerable JavaScript libraries
- 5
Missing X-Content-Type-OptionsLow
Why it matters: Without this, browsers may incorrectly interpret file types, risking security flaws.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Lack of a referrer policy may expose sensitive URL information.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 7
Missing Permissions PolicyInfo
Why it matters: Without a permissions policy, unnecessary browser features can be exploited.
Fix: Add the header: Permissions-Policy: (camera=(), microphone=(), geolocation=())
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.