Scanned sites / www.shawnessysmiles.ca / 2026-10-19-0228
www.shawnessysmiles.ca scan from 2026-10-19 02:28:06 UTC DR 0
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-10-19-0228
Scanned 2026-10-19 02:28:06 UTC, finished 2026-10-19 02:30:13 UTC. 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 October 19, 2026 the Site Spider crawled 30 pages and 299 assets of www.shawnessysmiles.ca, starting from https://www.shawnessysmiles.ca/. It scored 94 out of 100, an excellent result. 4 of 33 checks found something to fix, led by heavy assets (4), title tags (6), meta descriptions (6); 22 checks passed. Most of the points went to heavy assets (−2.4), title tags (−2.1), meta descriptions (−1.7). 7 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: Medium5 medium, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 30
- Assets fetched
- 299
- Status
- Completed
- Checks with issues
- 4 of 33
329 of 343 discovered URLs were fetched, 14 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 6 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 sites42 noted0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 6 destinations checked.
- 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 assets4 issues4 assets larger than 500 KB among 299 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.−2.4 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; none is a dead end or buried.
- Thin contentOK0 of 29 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL formatOKAll 30 page URLs are plain lowercase addresses without parameters.
- CanonicalsOK0 of 29 pages have a canonical worth checking.
- Robots directives29 noted29 pages carry a robots directive; 0 carry none.
- Anchor text1 noted1 destination are linked without useful anchor text, or with nofollow.
- Title and heading structureOK0 of 29 pages could use the title, heading and snippet space better.
- Image weight and alt length17 noted17 images over 100 KB; 0 with alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationOKAll 29 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured data1 noted29 of 29 indexable pages carry structured data: BreadcrumbList (29), ListItem (29), WebSite (29), Organization (29), WebPage (29). 1 page with errors a rich result would fail on.
- Near duplicatesOKNo near duplicates among 29 pages with enough text to compare.
- Soft 404sOKNone of 29 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsOK0 of 29 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookiesOK1 cookie set by the site; 13 response headers recorded across 329 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 29 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling5 noted5 words an English dictionary does not know, on 29 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2283 sites, median 79%, average 78%
www.shawnessysmiles.ca scores 94%, higher than 95% of the 2283 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 website has a health score of 94/100. There are a few issues to address, particularly with redirects, non-200 responses, title tags, and meta descriptions. Here is a priority fix plan.
- 1
Fix Redirects
Why: Redirects can slow down page load times and confuse users.
How: Update the sitemap.xml URL to point directly to sitemap_index.xml without a redirect. Remove the unnecessary redirect at the South Calgary partial dentures page.
Checks: redirects
- 2
Address Non-200 Responses
Why: Non-200 responses can harm user experience and SEO.
How: Fix the 404 errors by providing valid content or removing the references to the missing assets.
Checks: status-codes
- 3
Optimize Title Tags
Why: Title tags directly affect rankings and click-through rates.
How: Revise the short title tags to exceed 30 characters and shorten the long ones to be within 60 characters.
Checks: titles
- 4
Improve Meta Descriptions
Why: Meta descriptions influence click rates from search results.
How: Shorten meta descriptions to within 160 characters to avoid truncation in search results.
Checks: meta-descriptions
- 5
Reduce Heavy Assets
Why: Large assets can slow page load speed and affect user experience.
How: Compress images and stylesheets that exceed 500 KB to improve site performance.
Evidence: 436 KB of stylesheet, loaded by 29 pages, so every visitor to any of them downloads it.
29 pages affected
Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.
Checks: heavy-assets
- 6
Consistently Optimize All Heavy Assets
Why: Each large asset affects loading times, impacting UX.
How: Ensure all identified large assets are optimized or replaced with smaller variants.
Evidence: 307 KB of script, loaded by 29 pages, so every visitor to any of them downloads it.
29 pages affected
Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.
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 features, including headers for transport security and content policy, which can expose users to risk. Several JavaScript libraries are outdated and vulnerable. Additionally, a private API key is publicly visible in the code. Immediate action is required to implement these security measures.
- 0 high
- 5 medium
- 1 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Lacking HSTS allows interception of initial HTTP requests, compromising user security.
Fix: Add the following header: `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload`.
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Absence of a CSP permits loading of malicious scripts or resources.
Fix: Add a Content-Security-Policy header, for example: `Content-Security-Policy: default-src 'self';`.
Evidence: Content Security Policy
- 3
Missing Clickjacking Protection (X-Frame-Options)Medium
Why it matters: Without this header, the site can be embedded in frames, risking clickjacking.
Fix: Include `X-Frame-Options: DENY` or `X-Frame-Options: SAMEORIGIN`.
Evidence: Clickjacking protection
- 4
Outdated and Vulnerable JavaScript LibrariesMedium
Why it matters: Using outdated libraries exposes known vulnerabilities that could be exploited.
Fix: Upgrade jQuery to version 3.5.0 or higher and Bootstrap to version 3.4.1 or higher.
Evidence: Vulnerable JavaScript libraries
- 5
Leaked API Key in CodeMedium
Why it matters: Exposure of an API key can lead to unauthorized access and abuse.
Fix: Restrict the Google API key by defining an HTTP referrer and managing settings in Google Cloud Console.
Evidence: Keys and secrets in page code
- 6
Missing Referrer PolicyLow
Why it matters: Not defining a referrer policy can expose sensitive URL information.
Fix: Add a header: `Referrer-Policy: no-referrer-when-downgrade`.
Evidence: Referrer policy
- 7
Missing Permissions PolicyInfo
Why it matters: A permissions policy could limit unnecessary browser feature usage.
Fix: Add a header: `Permissions-Policy: geolocation=(self)`.
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.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.3, 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.3 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.
- mcglassonfarms.comDR 1395/100 · rank 93 · 12 pages
- colzelectric.comDR 1495/100 · rank 93 · 40 pages
- sublimeelectricid.netDR 1095/100 · rank 93 · 289 pages
- www.donsdaledental.comDR 194/100 · rank 103 · 52 pages
- www.finedetailplumbing.com.auDR 094/100 · rank 103 · 41 pages
- www.dousevicz.netDR 194/100 · rank 103 · 10 pages
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.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.