Scanned sites / www.lubecity.ca / 2026-09-16-0053
www.lubecity.ca scan from 9/16/2026, 12:53:39 AM
A newer scan exists. See the latest report for www.lubecity.ca.
Scan 2026-09-16-0053
Scanned 9/16/2026, 12:53:39 AM, finished 9/16/2026, 1:21:55 AM. Found with openstreetmap overpass
Site: https://www.lubecity.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 16, 2026 the Site Spider crawled 207 pages and 826 assets of www.lubecity.ca, starting from https://www.lubecity.ca/. It scored 74 out of 100, a result that needs work. 11 of 14 checks found something to fix, led by thin content (141), sitemap coverage (119), orphan pages (108); 3 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
- 207
- Assets fetched
- 826
- Status
- Completed
- Checks with issues
- 11 of 14
- Title tags93 issues93 of 187 pages have title issues. 13 noindex or canonicalized pages excluded.
- Meta descriptions72 issues72 of 187 pages have meta description issues. 13 noindex or canonicalized pages excluded.
- Headings19 issues19 of 187 pages have heading issues. 13 noindex or canonicalized pages excluded.
- Broken links1 issue1 internal link point at 1 broken URL.
- Redirects6 issues7 redirecting URLs, 1 of them chained.
- Non-200 responses1 issue11 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability10 issues10 of 197 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt textOK0 of 1181 image references have no alt attribute. 104 use an empty alt (decorative), which is fine.
- Heavy assets22 issues22 assets larger than 500 KB among the 100 heaviest.
- Orphan pages108 issues108 pages have no internal links pointing at them.
- Sitemap coverage119 issues5 sitemaps listing 186 URLs: 11 crawled pages missing, 0 listed URLs broken or redirecting, 108 reachable only via the sitemap.
- Thin content141 issues141 of 187 pages have fewer than 200 words. 13 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1039 sites, median 82%, average 80%
www.lubecity.ca scores 74%, higher than 21% of the 1039 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 findingsYour site requires attention on broken links, redirects, and SEO elements like title tags and meta descriptions. Implementing these high-impact fixes can significantly improve both user experience and search engine performance.
- 1
Fix Broken Links
Why: Broken links harm user experience and SEO.
How: Update the internal link pointing to the broken URL or remove it.
Checks: broken-links
- 2
Clean Up Redirects
Why: Too many redirects slow down page loading and hurt SEO.
How: Eliminate unnecessary redirects, focusing especially on the chained one.
Checks: redirects
- 3
Resolve Non-200 Responses
Why: Pages returning errors can damage your site's credibility.
How: Fix the 11 non-200 status URLs by redirecting or restoring their content.
Checks: status-codes
- 4
Optimize Title Tags
Why: 93 title tags have issues that affect click-through rates.
How: Adjust titles to be unique, relevant, and within the 60-character limit.
Checks: titles
- 5
Address Meta Description Issues
Why: 72 meta descriptions need improvement for better search visibility.
How: Revise duplicates and ensure unique meta descriptions for each page.
Checks: meta-descriptions
- 6
Enhance Headings Structure
Why: Proper heading structure improves SEO and readability.
How: Add H1 tags to the pages missing them.
Checks: headings
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 crawlThe website lacks crucial security headers, making it vulnerable to attacks. Implementing HTTP Strict Transport Security and Content Security Policy is essential to protect against man-in-the-middle attacks and script injection. Additionally, sensitive API keys should be restricted. Address these findings promptly to enhance overall security.
- 0 high
- 4 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted on initial requests when typing the URL without HTTPS.
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 a CSP allows unrestricted loading of scripts and frames, increasing the risk of XSS attacks.
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, the site can be embedded in frames on other sites, risking clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Leaked Google API KeyMedium
Why it matters: Exposing an API key can lead to unauthorized usage unless properly restricted.
Fix: Restrict the API key in the Google Cloud console based on HTTP referrer.
Evidence: Keys and secrets in page code
- 5
Missing X-Content-Type-OptionsLow
Why it matters: Without this header, browsers might incorrectly interpret files based on their content, potentially executing harmful scripts.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 6
Missing Referrer PolicyLow
Why it matters: Absence of a Referrer-Policy may expose the full URLs of visited pages to external sites.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 7
Missing Permissions PolicyInfo
Why it matters: Without this policy, browser features such as camera and geolocation could be exploited if a script is injected.
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.lubecity.ca/ → no strict-transport-security
- https://www.lubecity.ca/alberta-oil-change-locations/ → no strict-transport-security
- https://www.lubecity.ca/coupons/ → no strict-transport-security
- https://www.lubecity.ca/gift-cards/ → no strict-transport-security
- https://www.lubecity.ca/tires/ → no strict-transport-security
- https://www.lubecity.ca/caa-battery-service/ → no strict-transport-security
- https://www.lubecity.ca/services/ → no strict-transport-security
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no strict-transport-security
- https://www.lubecity.ca/careers/ → no strict-transport-security
- https://www.lubecity.ca/blog/ → no strict-transport-security
- https://www.lubecity.ca/about/ → no strict-transport-security
- https://www.lubecity.ca/contact/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 200 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.lubecity.ca/ → no content-security-policy
- https://www.lubecity.ca/alberta-oil-change-locations/ → no content-security-policy
- https://www.lubecity.ca/coupons/ → no content-security-policy
- https://www.lubecity.ca/gift-cards/ → no content-security-policy
- https://www.lubecity.ca/tires/ → no content-security-policy
- https://www.lubecity.ca/caa-battery-service/ → no content-security-policy
- https://www.lubecity.ca/services/ → no content-security-policy
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no content-security-policy
- https://www.lubecity.ca/careers/ → no content-security-policy
- https://www.lubecity.ca/blog/ → no content-security-policy
- https://www.lubecity.ca/about/ → no content-security-policy
- https://www.lubecity.ca/contact/ → 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.lubecity.ca/ → no x-frame-options
- https://www.lubecity.ca/alberta-oil-change-locations/ → no x-frame-options
- https://www.lubecity.ca/coupons/ → no x-frame-options
- https://www.lubecity.ca/gift-cards/ → no x-frame-options
- https://www.lubecity.ca/tires/ → no x-frame-options
- https://www.lubecity.ca/caa-battery-service/ → no x-frame-options
- https://www.lubecity.ca/services/ → no x-frame-options
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no x-frame-options
- https://www.lubecity.ca/careers/ → no x-frame-options
- https://www.lubecity.ca/blog/ → no x-frame-options
- https://www.lubecity.ca/about/ → no x-frame-options
- https://www.lubecity.ca/contact/ → 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.lubecity.ca/ → no x-content-type-options
- https://www.lubecity.ca/alberta-oil-change-locations/ → no x-content-type-options
- https://www.lubecity.ca/coupons/ → no x-content-type-options
- https://www.lubecity.ca/gift-cards/ → no x-content-type-options
- https://www.lubecity.ca/tires/ → no x-content-type-options
- https://www.lubecity.ca/caa-battery-service/ → no x-content-type-options
- https://www.lubecity.ca/services/ → no x-content-type-options
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no x-content-type-options
- https://www.lubecity.ca/careers/ → no x-content-type-options
- https://www.lubecity.ca/blog/ → no x-content-type-options
- https://www.lubecity.ca/about/ → no x-content-type-options
- https://www.lubecity.ca/contact/ → 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.lubecity.ca/ → no referrer-policy
- https://www.lubecity.ca/alberta-oil-change-locations/ → no referrer-policy
- https://www.lubecity.ca/coupons/ → no referrer-policy
- https://www.lubecity.ca/gift-cards/ → no referrer-policy
- https://www.lubecity.ca/tires/ → no referrer-policy
- https://www.lubecity.ca/caa-battery-service/ → no referrer-policy
- https://www.lubecity.ca/services/ → no referrer-policy
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no referrer-policy
- https://www.lubecity.ca/careers/ → no referrer-policy
- https://www.lubecity.ca/blog/ → no referrer-policy
- https://www.lubecity.ca/about/ → no referrer-policy
- https://www.lubecity.ca/contact/ → 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.lubecity.ca/ → no permissions-policy
- https://www.lubecity.ca/alberta-oil-change-locations/ → no permissions-policy
- https://www.lubecity.ca/coupons/ → no permissions-policy
- https://www.lubecity.ca/gift-cards/ → no permissions-policy
- https://www.lubecity.ca/tires/ → no permissions-policy
- https://www.lubecity.ca/caa-battery-service/ → no permissions-policy
- https://www.lubecity.ca/services/ → no permissions-policy
- https://www.lubecity.ca/fleet-vehicle-maintenance-alberta/ → no permissions-policy
- https://www.lubecity.ca/careers/ → no permissions-policy
- https://www.lubecity.ca/blog/ → no permissions-policy
- https://www.lubecity.ca/about/ → no permissions-policy
- https://www.lubecity.ca/contact/ → no permissions-policy
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…ZA (39 chars) in https://www.lubecity.ca/alberta-oil-change-locations/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
- NoteThird-party scripts
Scripts run from 5 other domains 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.)
- www.googletagmanager.com (80 script tags)
- cdn.nicejob.co (2 script tags)
- maps.google.com (23 script tags)
- app.tireconnect.ca (1 script tag)
- www.google.com (4 script tags)
7 checks passed, 1 not applicable
- OKHTTPS
All 200 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.
- OKForms over HTTPS
5 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
1 library version recognised, none with known vulnerabilities.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
- Not applicableCookie flags
The crawl set no cookies, so there are no cookie flags to check.
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.lubecity.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.