Scanned sites / www.smilesourcespokane.com / 2026-10-05-0751

www.smilesourcespokane.com scan from 10/5/2026, 7:51:43 AM

Scan 2026-10-05-0751

Scanned 10/5/2026, 7:51:43 AM, finished 10/5/2026, 8:06:03 AM. Found with openstreetmap overpass

Site: https://www.smilesourcespokane.com/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

78/ 100Good

On October 5, 2026 the Site Spider crawled 261 pages and 699 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 78 out of 100, a good result. 9 of 22 checks found something to fix, led by meta descriptions (120), heavy assets (24), redirects (232); 4 checks passed. Most of the points went to meta descriptions (−7.4), heavy assets (−6), redirects (−4). 9 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 2 info findings. See the security findings ↓

Pages crawled
261
Assets fetched
699
Status
Completed
Checks with issues
9 of 22
CoverageComplete crawl

960 of 1,018 discovered URLs were fetched, 58 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 47 link destinations on other sites have not been checked.

  • Title tags25 issues
    25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.
    −1.9 points
  • Meta descriptions120 issues
    120 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.
    −7.4 points
  • Headings6 issues
    6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.
    −0.3 points
  • 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.
  • Redirects232 issues
    137 redirecting URLs, 103 of them chained.
    −4 points
  • Non-200 responses137 noted
    137 URLs did not return a 2xx response. 132 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 126 indexable pages have indexability warnings. 3 pages noindex by design.
  • Image alt text83 issues
    83 of 1199 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.
    −0.4 points
  • Heavy assets24 issues
    24 assets larger than 500 KB among 699 fetched assets.
    −6 points
  • Orphan pages25 issues
    25 pages have no internal links pointing at them.
    −0.8 points
  • Sitemap coverage25 issues
    15 sitemaps listing 126 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 25 reachable only via the sitemap.
    −1.2 points
  • Internal link counts22 noted
    Internal link counts for 129 pages; 22 worth a look.
  • Thin content5 issues
    5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
    −0.3 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format106 noted
    106 of 261 page URLs are harder to read, share or cache than they need to be.
  • Canonicals3 noted
    3 of 129 pages have a canonical worth checking.
  • Robots directives129 noted
    129 pages carry a robots directive; 0 carry none.
  • Anchor text184 noted
    184 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure73 noted
    73 of 126 pages could use the title, heading and snippet space better. 3 noindex or canonicalized pages excluded.
  • Image weight and alt length38 noted
    38 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.

Where this scan sits among all scanned sites

2073 sites, median 79%, average 78%

www.smilesourcespokane.com scores 78%, higher than 43% of the 2073 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%: 2 sites36%: 2 sites37%: 1 site38%: 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%: 9 sites53%: 7 sites54%: 8 sites55%: 7 sites56%: 6 sites57%: 10 sites58%: 16 sites59%: 6 sites60%: 12 sites61%: 10 sites62%: 20 sites63%: 21 sites64%: 15 sites65%: 38 sites66%: 27 sites67%: 35 sites68%: 34 sites69%: 34 sites70%: 34 sites71%: 62 sites72%: 67 sites73%: 55 sites74%: 60 sites75%: 77 sites76%: 78 sites77%: 92 sites78%: 91 sites79%: 85 sites80%: 97 sites81%: 102 sites82%: 105 sites83%: 90 sites84%: 90 sites85%: 67 sites86%: 67 sites87%: 61 sites88%: 66 sites89%: 51 sites90%: 33 sites91%: 42 sites92%: 24 sites93%: 19 sites94%: 15 sites95%: 7 sites96%: 4 sites97%: 10 sites98%: 2 sites99%: 1 site100%: 57 sites78% 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

Several technical SEO improvements are needed to enhance your site’s performance, including address redirects, title and meta description issues, and missing H1 headings. Prioritize these fixes for optimal impact.

  1. 1

    Fix Redirects

    Why: Eliminating 137 redirecting URLs, especially the 103 chained redirects, will enhance page load speed and user experience.

    How: Identify and remove unnecessary redirects to ensure pages load directly without intermediate steps.

    Checks: redirects, status-codes

  2. 2

    Add Missing Meta Descriptions

    Why: 120 pages lack meta descriptions, impacting search visibility and CTR.

    How: Write and implement unique meta descriptions for all affected pages, ensuring they are concise and relevant.

    Evidence: 119 pages have no meta description at all.

    119 pages affected

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: 25 pages have title issues that can affect SEO rankings and user engagement.

    How: Revise titles for affected pages, ensuring they are within optimal length and descriptive.

    Checks: titles

  4. 4

    Add Missing Headings (H1)

    Why: 6 pages are missing H1 headings, crucial for both user experience and SEO.

    How: Add an appropriate H1 heading to each affected page, summarizing the content effectively.

    Evidence: 6 pages: missing h1.

    6 pages affected

    Checks: headings

  5. 5

    Shrink Heavy Assets

    Why: 24 assets are larger than 500 KB, negatively impacting load times.

    How: Optimize and compress large files or consider removing them from the pages if not essential.

    Evidence: 327 KB of document, loaded by 35 pages, so every visitor to any of them downloads it.

    35 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. 6

    Fix Orphan Pages

    Why: 25 pages are not linked internally, making them hard for search engines to discover.

    How: Add internal links to these orphan pages from relevant content on your site.

    Checks: orphan-pages

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 security vulnerabilities mainly due to missing HTTP headers and outdated libraries. Implementing recommended headers will help protect against various attacks and improve security. Immediate action is necessary to mitigate potential risks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS can expose users to potential man-in-the-middle attacks on first requests.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows any outside source to load scripts, risking XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Without proper frame options, your site can be embedded in a frame on harmful pages.

    Fix: Add the header: 'X-Frame-Options: DENY' or use a CSP directive.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

    Why it matters: The current version (3.3.1) has known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to version 3.5.0 or newer.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Exposing Google API KeyMedium

    Why it matters: The API key should be restricted to prevent unauthorized usage.

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

    Evidence: Keys and secrets in page code

  6. 6

    Server Version DisclosureLow

    Why it matters: Revealing server version can aid attackers in finding vulnerabilities.

    Fix: Hide server version information in the response headers.

    Evidence: Software version disclosure

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not restricting permissions can allow scripts to access more browser features than necessary.

    Fix: Add the header: 'Permissions-Policy: geolocation=(), microphone=(), camera=()'

    Evidence: Permissions policy

  8. 8

    Lack of Subresource Integrity on Third-party ScriptsInfo

    Why it matters: Scripts from third-party domains can be tampered with, risking site security.

    Fix: Implement a Content Security Policy that only allows reputable sources.

    Evidence: Third-party scripts

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.smilesourcespokane.com/ → no strict-transport-security
    • https://www.smilesourcespokane.com/dental-implants/ → no strict-transport-security
    • https://www.smilesourcespokane.com/spokane-valley-wa/ → no strict-transport-security
    • https://www.smilesourcespokane.com/north-side-wa/ → no strict-transport-security
    • https://www.smilesourcespokane.com/south-hill-wa/ → no strict-transport-security
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no strict-transport-security
    • https://www.smilesourcespokane.com/terms-conditions/ → no strict-transport-security
    • https://www.smilesourcespokane.com/privacy-policy/ → no strict-transport-security
    • https://www.smilesourcespokane.com/accessibility-commitment/ → no strict-transport-security
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no strict-transport-security
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no strict-transport-security
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 129 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.smilesourcespokane.com/ → no content-security-policy
    • https://www.smilesourcespokane.com/dental-implants/ → no content-security-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/ → no content-security-policy
    • https://www.smilesourcespokane.com/north-side-wa/ → no content-security-policy
    • https://www.smilesourcespokane.com/south-hill-wa/ → no content-security-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no content-security-policy
    • https://www.smilesourcespokane.com/terms-conditions/ → no content-security-policy
    • https://www.smilesourcespokane.com/privacy-policy/ → no content-security-policy
    • https://www.smilesourcespokane.com/accessibility-commitment/ → no content-security-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no content-security-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no content-security-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → 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.smilesourcespokane.com/ → no x-frame-options
    • https://www.smilesourcespokane.com/dental-implants/ → no x-frame-options
    • https://www.smilesourcespokane.com/spokane-valley-wa/ → no x-frame-options
    • https://www.smilesourcespokane.com/north-side-wa/ → no x-frame-options
    • https://www.smilesourcespokane.com/south-hill-wa/ → no x-frame-options
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no x-frame-options
    • https://www.smilesourcespokane.com/terms-conditions/ → no x-frame-options
    • https://www.smilesourcespokane.com/privacy-policy/ → no x-frame-options
    • https://www.smilesourcespokane.com/accessibility-commitment/ → no x-frame-options
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no x-frame-options
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no x-frame-options
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → no x-frame-options
  • 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.smilesourcespokane.com/ → no permissions-policy
    • https://www.smilesourcespokane.com/dental-implants/ → no permissions-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/ → no permissions-policy
    • https://www.smilesourcespokane.com/north-side-wa/ → no permissions-policy
    • https://www.smilesourcespokane.com/south-hill-wa/ → no permissions-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/meet-our-doctors/ → no permissions-policy
    • https://www.smilesourcespokane.com/terms-conditions/ → no permissions-policy
    • https://www.smilesourcespokane.com/privacy-policy/ → no permissions-policy
    • https://www.smilesourcespokane.com/accessibility-commitment/ → no permissions-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/ → no permissions-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/our-technologies/ → no permissions-policy
    • https://www.smilesourcespokane.com/spokane-valley-wa/about-us/office-gallery/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Flywheel/5.1.0 (960 responses)
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 3.3.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 3.3.1 in https://code.jquery.com/jquery-3.3.1.min.js: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…sA (39 chars) in https://www.smilesourcespokane.com/: 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 6 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.)

    • code.jquery.com (40 script tags)
    • www.googletagmanager.com (80 script tags)
    • cdnjs.cloudflare.com (80 script tags)
    • cdn.jsdelivr.net (45 script tags)
    • cdn.userway.org (40 script tags)
    • cdn.trustindex.io (1 script tag)
6 checks passed, 2 not applicable
  • OKHTTPS

    All 129 crawled pages were served over HTTPS.

  • OKMIME sniffing protection

    x-content-type-options is set on all 129 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 129 HTML pages.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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.smilesourcespokane.com

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.smilesourcespokane.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.smilesourcespokane.com?

  • 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.smilesourcespokane.com. Removal needs no account and no proof of purchase.
www.smilesourcespokane.com scan 2026-10-05-0751 | DIY SEO Hub