Scanned sites / www.shawnessysmiles.ca / 2026-09-27-1849
www.shawnessysmiles.ca scan from 9/27/2026, 6:49:58 PM
Scan 2026-09-27-1849
Scanned 9/27/2026, 6:49:58 PM, finished 9/27/2026, 6:58:41 PM. Found with openstreetmap overpass
Site: https://www.shawnessysmiles.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 27, 2026 the Site Spider crawled 30 pages and 503 assets of www.shawnessysmiles.ca, starting from https://www.shawnessysmiles.ca/. It scored 93 out of 100, an excellent result. 5 of 16 checks found something to fix, led by heavy assets (5), title tags (6), meta descriptions (6); 9 checks passed. Most of the points went to heavy assets (−3), title tags (−2.1), meta descriptions (−1.7). 2 checks found something the score does not count, listed as noted. 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: Medium5 medium and 1 low findings. See the security findings ↓
- Pages crawled
- 30
- Assets fetched
- 503
- Status
- Completed
- Checks with issues
- 5 of 16
533 of 547 discovered URLs were fetched, 14 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 8 link destinations on other sites were checked.
- Title tags6 issues6 of 29 pages have title issues.−2.1 points
- Meta descriptions6 issues6 of 29 pages have meta description issues.−1.7 points
- HeadingsOK0 of 29 pages have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites2 issues2 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 8 destinations checked.−0.8 points
- Redirects1 issue2 redirecting URLs, 0 of them chained.−0.1 points
- Non-200 responses9 noted9 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 29 indexable pages have indexability warnings.
- Image alt textOK0 of 342 image references have no alt attribute.
- Heavy assets5 issues5 assets larger than 500 KB among 503 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.−3 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverageOK3 sitemaps listing 29 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Internal link countsOKInternal link counts for 29 pages.
- Thin contentOK0 of 29 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1315 sites, median 80%, average 79%
www.shawnessysmiles.ca scores 93%, higher than 94% of the 1315 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 has a strong health score, but there are several key improvements needed for SEO. Focus on fixing redirect issues, optimizing titles and meta descriptions, and reducing the size of heavy assets for better performance.
- 1
Fix Redirects
Why: Redirects can impact user experience and SEO.
How: Update the configuration to eliminate unnecessary redirects. Direct links to their final destinations.
Checks: redirects
- 2
Address Non-200 Responses
Why: Non-200 responses can lead to loss of traffic and affect rankings.
How: Identify the URLs giving non-200 responses and correct their status codes or remove from links.
Checks: status-codes
- 3
Optimize Title Tags
Why: Titles contribute directly to SEO and click-through rates.
How: Revise titles to avoid being too short or too long, aiming for 50-60 characters.
Checks: titles
- 4
Revise Meta Descriptions
Why: Proper meta descriptions can improve click-through rates from search engines.
How: Adjust meta descriptions to stay within 150-160 characters for better visibility.
Checks: meta-descriptions
- 5
Reduce Heavy Assets
Why: High asset weight can slow down the site, affecting user experience.
How: Optimize or compress large images and documents to improve load speeds.
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 crawlThe website lacks critical security headers, making it vulnerable to various attacks. Immediate improvements such as implementing HTTP Strict Transport Security and a Content Security Policy are essential. Additionally, vulnerabilities in JavaScript libraries and the exposure of a Google API key require urgent attention.
- 0 high
- 5 medium
- 1 low
- 0 info
- 1
Missing HTTP Strict Transport SecurityMedium
Why it matters: Without HSTS, attackers can intercept visitors on their initial request.
Fix: Implement `Strict-Transport-Security: max-age=31536000; includeSubDomains` in your server configuration.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security PolicyMedium
Why it matters: Absence of a CSP allows unrestricted script and style loading, increasing XSS risks.
Fix: Add `Content-Security-Policy: default-src 'self';` to your server headers.
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without this header, your pages can be embedded into frames, leading to clickjacking attacks.
Fix: Set `X-Frame-Options: DENY` in your server configuration.
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript LibrariesMedium
Why it matters: Using outdated libraries exposes the site to known vulnerabilities.
Fix: Upgrade jQuery to at least 3.5.0 and Bootstrap to at least 3.4.1.
Evidence: Vulnerable JavaScript libraries
- 5
Leaked Google API KeyMedium
Why it matters: Exposing the API key may allow unauthorized usage, leading to potential costs or service restrictions.
Fix: Restrict the API key in the Google Cloud console by ensuring it's only accessible from specified HTTP referrers.
Evidence: Keys and secrets in page code
- 6
Missing Referrer-PolicyLow
Why it matters: Without this header, full URLs can be sent to third-party sites, revealing sensitive information.
Fix: Include `Referrer-Policy: no-referrer` in your server headers.
Evidence: Referrer 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.shawnessysmiles.ca/ → no strict-transport-security
- https://www.shawnessysmiles.ca/request-appointment/ → no strict-transport-security
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/ → no strict-transport-security
- https://www.shawnessysmiles.ca/about-shawnessy-smiles-dental/ → no strict-transport-security
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/policies/ → no strict-transport-security
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/insurance-finances/ → no strict-transport-security
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/health-safety/ → no strict-transport-security
- https://www.shawnessysmiles.ca/new-patients/ → no strict-transport-security
- https://www.shawnessysmiles.ca/dental-team/ → no strict-transport-security
- https://www.shawnessysmiles.ca/team/dr-roman-koutsil/ → no strict-transport-security
- https://www.shawnessysmiles.ca/south-calgary-dental-services/ → no strict-transport-security
- https://www.shawnessysmiles.ca/south-calgary-family-dentistry/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 29 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.shawnessysmiles.ca/ → no content-security-policy
- https://www.shawnessysmiles.ca/request-appointment/ → no content-security-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/ → no content-security-policy
- https://www.shawnessysmiles.ca/about-shawnessy-smiles-dental/ → no content-security-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/policies/ → no content-security-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/insurance-finances/ → no content-security-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/health-safety/ → no content-security-policy
- https://www.shawnessysmiles.ca/new-patients/ → no content-security-policy
- https://www.shawnessysmiles.ca/dental-team/ → no content-security-policy
- https://www.shawnessysmiles.ca/team/dr-roman-koutsil/ → no content-security-policy
- https://www.shawnessysmiles.ca/south-calgary-dental-services/ → no content-security-policy
- https://www.shawnessysmiles.ca/south-calgary-family-dentistry/ → 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.shawnessysmiles.ca/ → no x-frame-options
- https://www.shawnessysmiles.ca/request-appointment/ → no x-frame-options
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/ → no x-frame-options
- https://www.shawnessysmiles.ca/about-shawnessy-smiles-dental/ → no x-frame-options
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/policies/ → no x-frame-options
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/insurance-finances/ → no x-frame-options
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/health-safety/ → no x-frame-options
- https://www.shawnessysmiles.ca/new-patients/ → no x-frame-options
- https://www.shawnessysmiles.ca/dental-team/ → no x-frame-options
- https://www.shawnessysmiles.ca/team/dr-roman-koutsil/ → no x-frame-options
- https://www.shawnessysmiles.ca/south-calgary-dental-services/ → no x-frame-options
- https://www.shawnessysmiles.ca/south-calgary-family-dentistry/ → no x-frame-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.shawnessysmiles.ca/ → no referrer-policy
- https://www.shawnessysmiles.ca/request-appointment/ → no referrer-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/ → no referrer-policy
- https://www.shawnessysmiles.ca/about-shawnessy-smiles-dental/ → no referrer-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/policies/ → no referrer-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/insurance-finances/ → no referrer-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/health-safety/ → no referrer-policy
- https://www.shawnessysmiles.ca/new-patients/ → no referrer-policy
- https://www.shawnessysmiles.ca/dental-team/ → no referrer-policy
- https://www.shawnessysmiles.ca/team/dr-roman-koutsil/ → no referrer-policy
- https://www.shawnessysmiles.ca/south-calgary-dental-services/ → no referrer-policy
- https://www.shawnessysmiles.ca/south-calgary-family-dentistry/ → 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.shawnessysmiles.ca/ → no permissions-policy
- https://www.shawnessysmiles.ca/request-appointment/ → no permissions-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/ → no permissions-policy
- https://www.shawnessysmiles.ca/about-shawnessy-smiles-dental/ → no permissions-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/policies/ → no permissions-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/insurance-finances/ → no permissions-policy
- https://www.shawnessysmiles.ca/why-shawnessy-smiles-dental/health-safety/ → no permissions-policy
- https://www.shawnessysmiles.ca/new-patients/ → no permissions-policy
- https://www.shawnessysmiles.ca/dental-team/ → no permissions-policy
- https://www.shawnessysmiles.ca/team/dr-roman-koutsil/ → no permissions-policy
- https://www.shawnessysmiles.ca/south-calgary-dental-services/ → no permissions-policy
- https://www.shawnessysmiles.ca/south-calgary-family-dentistry/ → no permissions-policy
- FoundVulnerable JavaScript librariesMedium
3 libraries with published vulnerabilities: jQuery 3.2.1, jQuery 3.1.2, Bootstrap 3.3.7. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 3.2.1 in https://www.shawnessysmiles.ca/wp-content/cache/min/1/ajax/libs/jquery/3.2.1/jq…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- jQuery 3.1.2 in https://www.shawnessysmiles.ca/wp-content/plugins/gravityforms/js/placeholders.…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- Bootstrap 3.3.7 in https://www.shawnessysmiles.ca/wp-content/themes/cpm-theme-base2/assets/bootstr…: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…wU (39 chars) in https://www.shawnessysmiles.ca/: 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 2 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.)
- maps.google.com (29 script tags)
- www.google.com (3 script tags)
- NoteSensitive paths in robots.txt
robots.txt lists 1 path 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: /cgi-bin
7 checks passed
- OKHTTPS
All 29 crawled pages were served over HTTPS.
- OKMIME sniffing protection
x-content-type-options is set on all 29 HTML pages.
- OKSoftware version disclosure
The Server header names a product without a version, and there is no X-Powered-By header.
- OKCookie flags
All 1 cookie carry Secure, HttpOnly and SameSite flags.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
3 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
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.shawnessysmiles.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- westernhvac.com94/100 · rank 67 · 3,406 pages
- ajfurnace.ca94/100 · rank 67 · 22 pages
- calgaryoptometry.com94/100 · rank 67 · 170 pages
- freedomlaw.ca93/100 · rank 77 · 649 pages
- www.patriotairnd.com93/100 · rank 77 · 83 pages
- ndscs.edu93/100 · rank 77 · 5,000 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.shawnessysmiles.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own www.shawnessysmiles.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.shawnessysmiles.ca. Removal needs no account and no proof of purchase.