Scanned sites / www.shawnessysmiles.ca / 2026-10-04-1532

www.shawnessysmiles.ca scan from 10/4/2026, 3:32:58 PM

Scan 2026-10-04-1532

Scanned 10/4/2026, 3:32:58 PM, finished 10/4/2026, 3:43:44 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.

92/ 100Excellent

On October 4, 2026 the Site Spider crawled 30 pages and 503 assets of www.shawnessysmiles.ca, starting from https://www.shawnessysmiles.ca/. It scored 92 out of 100, an excellent result. 5 of 23 checks found something to fix, led by heavy assets (5), title tags (6), meta descriptions (6); 14 checks passed. Most of the points went to heavy assets (−3), title tags (−2.1), meta descriptions (−1.7). 4 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, 1 low and 1 info findings. See the security findings ↓

Pages crawled
30
Assets fetched
503
Status
Completed
Checks with issues
5 of 23
CoverageComplete crawl

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 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 sites2 issues
    2 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 8 destinations checked.
    −0.8 points
  • 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 assets5 issues
    5 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 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

2062 sites, median 79%, average 78%

www.shawnessysmiles.ca scores 92%, higher than 93% of the 2062 scanned sites. See the full ranking.

0531050%: 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%: 1 site36%: 2 sites37%: 2 sites38%: 3 sites39%: 2 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 0 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 4 sites48%: 4 sites49%: 3 sites50%: 5 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 6 sites55%: 8 sites56%: 5 sites57%: 11 sites58%: 14 sites59%: 8 sites60%: 11 sites61%: 9 sites62%: 18 sites63%: 18 sites64%: 18 sites65%: 36 sites66%: 27 sites67%: 39 sites68%: 33 sites69%: 29 sites70%: 36 sites71%: 59 sites72%: 64 sites73%: 60 sites74%: 59 sites75%: 77 sites76%: 76 sites77%: 81 sites78%: 96 sites79%: 85 sites80%: 105 sites81%: 100 sites82%: 101 sites83%: 87 sites84%: 90 sites85%: 69 sites86%: 70 sites87%: 66 sites88%: 68 sites89%: 48 sites90%: 35 sites91%: 42 sites92%: 24 sites93%: 18 sites94%: 15 sites95%: 7 sites96%: 5 sites97%: 9 sites98%: 2 sites99%: 1 site100%: 56 sites92% 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 site has a strong health score with good SEO practices. A few issues identified include redirects, title tags, meta descriptions, and large assets which need attention. The recommended fixes will enhance your site's performance and user experience.

  1. 1

    Fix Redirects

    Why: Redirects can confuse users and search engines, impacting SEO.

    How: Update links to point to the final URL directly instead of a redirect. Avoid unnecessary redirects to improve loading times.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses can negatively impact user experience and SEO.

    How: Identify and remove or update URLs causing 404 errors, particularly images and assets.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Better titles enhance visibility and attract more clicks.

    How: Revise titles to ensure they are between 30-60 characters, focusing on clarity and relevance.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Effective meta descriptions can increase click-through rates.

    How: Shorten or refine descriptions to stay under the pixel limit, ensuring they accurately represent the content.

    Checks: meta-descriptions

  5. 5

    Optimize Large Assets

    Why: Large files slow down your site, negatively affecting user experience and SEO.

    How: Compress images and PDFs to reduce load times, utilizing formats like JPEG for images when possible.

    Evidence: 586 KB of image, loaded by 2 pages, so every visitor to any of them downloads it.

    2 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

The website has several security vulnerabilities, including missing critical response headers and outdated libraries. Implementing the recommended changes will enhance the site's security against attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing in the address without HTTPS can be intercepted on the first request.

    Fix: Add the header: `Strict-Transport-Security: max-age=31536000; includeSubDomains` to all HTML pages.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, there are no restrictions on where scripts and styles can load from, increasing the risk of XSS attacks.

    Fix: Add the header: `Content-Security-Policy: default-src 'self';` to all HTML pages.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of X-Frame-Options allows pages to be embedded in frames on other sites, risking clickjacking attacks.

    Fix: Add the header: `X-Frame-Options: DENY` to all HTML pages.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery and Bootstrap LibrariesMedium

    Why it matters: Using versions with known vulnerabilities poses security risks that may be exploitable.

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

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposed Google API KeyMedium

    Why it matters: A publicly exposed API key can be misused unless restricted by referrer settings.

    Fix: Restrict the Google API key usage in the Google Cloud console by setting the appropriate application restrictions.

    Evidence: Keys and secrets in page code

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a defined referrer policy, sensitive page addresses are sent to third-party sites.

    Fix: Add the header: `Referrer-Policy: no-referrer` to all HTML pages.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not using a permissions policy leaves browser features open to misuse if an attacker injects a script.

    Fix: Add the header: `Permissions-Policy: geometries=(self)` to all HTML pages.

    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-04-1532 | DIY SEO Hub