Scanned sites / www.shawnessysmiles.ca / 2026-10-05-0623

www.shawnessysmiles.ca scan from 10/5/2026, 6:23:17 AM

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

Scan 2026-10-05-0623

Scanned 10/5/2026, 6:23:17 AM, finished 10/5/2026, 6:30:52 AM. 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.

94/ 100Excellent

On October 5, 2026 the Site Spider crawled 30 pages and 300 assets of www.shawnessysmiles.ca, starting from https://www.shawnessysmiles.ca/. It scored 94 out of 100, an excellent result. 4 of 22 checks found something to fix, led by title tags (6), heavy assets (3), meta descriptions (6); 14 checks passed. Most of the points went to title tags (−2.1), heavy assets (−1.8), meta descriptions (−1.7). 4 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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
300
Status
Completed
Checks with issues
4 of 22
CoverageComplete crawl

330 of 344 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 have not been checked.

  • Title tags6 issues
    6 of 29 pages have title issues.
    −2.1 points
  • Meta descriptions6 issues
    6 of 29 pages have meta description issues.
    −1.7 points
  • HeadingsOK
    0 of 29 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses9 noted
    9 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 limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 29 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 342 image references have no alt attribute.
  • Heavy assets3 issues
    3 assets larger than 500 KB among 300 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −1.8 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    3 sitemaps listing 29 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 29 pages; none is a dead end or buried.
  • Thin contentOK
    0 of 29 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 30 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 29 pages have a canonical worth checking.
  • Robots directives29 noted
    29 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 29 pages could use the title, heading and snippet space better.
  • Image weight and alt length17 noted
    17 images 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.

Where this scan sits among all scanned sites

2095 sites, median 79%, average 78%

www.shawnessysmiles.ca scores 94%, higher than 95% of the 2095 scanned sites. See the full ranking.

0541070%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 1 site28%: 0 sites29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 2 sites44%: 1 site45%: 4 sites46%: 4 sites47%: 4 sites48%: 4 sites49%: 4 sites50%: 4 sites51%: 5 sites52%: 9 sites53%: 7 sites54%: 8 sites55%: 8 sites56%: 7 sites57%: 11 sites58%: 16 sites59%: 6 sites60%: 13 sites61%: 12 sites62%: 20 sites63%: 23 sites64%: 16 sites65%: 37 sites66%: 29 sites67%: 31 sites68%: 33 sites69%: 36 sites70%: 40 sites71%: 65 sites72%: 70 sites73%: 64 sites74%: 56 sites75%: 73 sites76%: 78 sites77%: 89 sites78%: 96 sites79%: 86 sites80%: 94 sites81%: 101 sites82%: 107 sites83%: 89 sites84%: 96 sites85%: 70 sites86%: 63 sites87%: 60 sites88%: 61 sites89%: 51 sites90%: 32 sites91%: 41 sites92%: 27 sites93%: 21 sites94%: 12 sites95%: 7 sites96%: 4 sites97%: 11 sites98%: 2 sites99%: 1 site100%: 58 sites94% 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 website has a high health score, but there are some critical SEO fixes needed for optimal performance. Prioritize resolving redirect issues, addressing title and meta description problems, and optimizing large assets.

  1. 1

    Fix Redirects

    Why: Redirects can cause confusion for search engines and affect SEO rankings.

    How: Update the sitemap URL to point directly to the final sitemap index without redirection. Adjust the page URL to eliminate unnecessary redirects.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: These can prevent users and search engines from accessing your site resources.

    How: Fix the 404 errors for assets by removing references or restoring these resources to ensure all links are functional.

    Checks: status-codes

  3. 3

    Revise Title Tags

    Why: Effective titles improve click-through rates and rankings.

    How: For long titles, shorten them below 60 characters while maintaining essential keywords. For the short title, extend it using relevant keywords.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Well-crafted meta descriptions encourage clicks from search engine results.

    How: Optimize descriptions to remain under 160 characters, ensuring they are descriptive and compelling to improve visibility.

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: Reducing asset size improves loading speed, enhancing user experience and SEO.

    How: Compress and optimize the identified images and scripts to reduce their file sizes to below 500 KB if possible.

    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

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

Your website lacks essential security measures, including HTTP Strict Transport Security and Content Security Policy, which can expose users to risks. Additionally, outdated libraries and leaked keys increase vulnerability. Implementing recommended headers and updating libraries will significantly enhance your site's security.

  • 0 high
  • 5 medium
  • 1 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted if they access the site via HTTP.

    Fix: Add a response header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP means scripts and styles can load from any source, increasing XSS risk.

    Fix: Add a response header: Content-Security-Policy: default-src 'self';.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Absence of X-Frame-Options allows embedding your site in harmful frames.

    Fix: Add a response header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibrariesMedium

    Why it matters: Vulnerabilities in jQuery and Bootstrap can be exploited if improperly used.

    Fix: Upgrade jQuery to at least 3.5.0 and Bootstrap to at least 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: Exposed keys can lead to unauthorized usage if not restricted.

    Fix: Restrict Google API key usage by referrer in the Google Cloud console.

    Evidence: Keys and secrets in page code

  6. 6

    Missing Referrer PolicyLow

    Why it matters: No referrer policy can expose users' visited pages to other sites.

    Fix: Add a response header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: This policy limits what injected scripts can access from the browser.

    Fix: Add a response header: Permissions-Policy: fullscreen=(self), 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.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.

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.
www.shawnessysmiles.ca scan 2026-10-05-0623 | DIY SEO Hub