Scanned sites / www.shawnessysmiles.ca / 2026-10-25-0103

www.shawnessysmiles.ca scan from 2026-10-25 01:03:08 UTC DR 0

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-25-0103

Scanned 2026-10-25 01:03:08 UTC, finished 2026-10-25 01:04:53 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.

94/ 100Excellent

On October 25, 2026 the Site Spider crawled 30 pages and 316 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 title tags (6), heavy assets (3), meta descriptions (6); 22 checks passed. Most of the points went to title tags (−2.1), heavy assets (−1.8), 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
316
Status
Completed
Checks with issues
4 of 33
CoverageComplete crawl

346 of 360 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 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 sites42 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 6 destinations checked.
  • 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 316 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.
  • HTML and head validationOK
    All 29 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data1 noted
    29 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 duplicatesOK
    No near duplicates among 29 pages with enough text to compare.
  • Soft 404sOK
    None of 29 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsOK
    0 of 29 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    1 cookie set by the site; 13 response headers recorded across 346 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 29 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not 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 checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling5 noted
    5 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

2315 sites, median 79%, average 78%

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

0571140%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 69 sites75%: 71 sites76%: 86 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 106 sites81%: 105 sites82%: 114 sites83%: 98 sites84%: 108 sites85%: 86 sites86%: 69 sites87%: 73 sites88%: 59 sites89%: 63 sites90%: 33 sites91%: 44 sites92%: 37 sites93%: 23 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 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 site has a great health score, but there are several priority fixes needed related to redirects, status codes, title tags, meta descriptions, and heavy assets. Implementing these will improve user experience and SEO.

  1. 1

    Fix Redirects

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

    How: Update the existing redirects to ensure they point directly to the correct URLs without interim steps.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: 404 errors can frustrate visitors and harm SEO.

    How: Remove or fix the broken links to asset URLs and ensure they return a 200 status.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: Improperly formatted title tags can mislead users and risk lower rankings.

    How: Revise long titles (over 60 characters) and short titles (under 30 characters) to ensure they meet optimal length guidelines.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Meta descriptions that are too long may be cut off in search results, reducing click-through rates.

    How: Shorten meta descriptions to around 150-160 characters while maintaining key information.

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: Large assets can slow page load times, impacting user experience.

    How: Compress the large assets or optimize formats to reduce file sizes without compromising quality.

    Evidence: 436 KB of stylesheet, loaded by 28 pages, so every visitor to any of them downloads it.

    28 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 multiple vulnerabilities related to security headers and outdated libraries. Implementing proper headers and updating libraries will significantly improve security against common attacks.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors may be intercepted on their first connection without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=63072000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of CSP allows unrestricted script and resource loading, increasing XSS risks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, pages can be embedded in frames, exposing users to clickjacking.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Using outdated libraries with known vulnerabilities could allow for exploitation.

    Fix: Update jQuery to version 3.5.0 and Bootstrap to version 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: Having an unrestricted Google API key may lead to unauthorized use of resources.

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

    Evidence: Keys and secrets in page code

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive information may be shared with other sites.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not configuring Permissions-Policy may leave browser features accessible to injected scripts.

    Fix: Add the header: Permissions-Policy: geolocation=(self), 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.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.2.0, 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.2.0 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 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.)

    • ajax.googleapis.com (1 script tag)
    • maps.google.com (29 script tags)
    • www.google.com (3 script tags)
    • static.elfsight.com (1 script tag)
    • cdnjs.cloudflare.com (1 script tag)
  • 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.

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.