Scanned sites / www.smilesourcespokane.com / 2026-10-04-0923
www.smilesourcespokane.com scan from 10/4/2026, 9:23:06 AM
A newer scan exists. See the latest report for www.smilesourcespokane.com.
Scan 2026-10-04-0923
Scanned 10/4/2026, 9:23:06 AM, finished 10/4/2026, 9:44:15 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.
On October 4, 2026 the Site Spider crawled 261 pages and 699 assets of www.smilesourcespokane.com, starting from https://www.smilesourcespokane.com/. It scored 77 out of 100, a good result. 10 of 16 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). 2 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, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 261
- Assets fetched
- 699
- Status
- Completed
- Checks with issues
- 10 of 16
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. 52 link destinations on other sites were checked.
- Title tags25 issues25 of 126 pages have title issues. 3 noindex or canonicalized pages excluded.−1.9 points
- Meta descriptions120 issues120 of 126 pages have meta description issues. 3 noindex or canonicalized pages excluded.−7.4 points
- Headings6 issues6 of 126 pages have heading issues. 3 noindex or canonicalized pages excluded.−0.3 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites1 issue1 destination answered with an error, 17 could not be determined (timeouts, rate limits or refusals), of 52 destinations checked.−0.3 points
- Redirects232 issues137 redirecting URLs, 103 of them chained.−4 points
- Non-200 responses137 noted137 URLs did not return a 2xx response. 132 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 126 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt text83 issues83 of 1199 image references have no alt attribute. 989 use an empty alt (decorative), which is fine.−0.4 points
- Heavy assets24 issues24 assets larger than 500 KB among 699 fetched assets.−6 points
- Orphan pages25 issues25 pages have no internal links pointing at them.−0.8 points
- Sitemap coverage25 issues15 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 countsOKInternal link counts for 129 pages.
- Thin content5 issues5 of 126 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.−0.3 points
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
2057 sites, median 80%, average 78%
www.smilesourcespokane.com scores 77%, higher than 37% of the 2057 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 findingsThe website has several areas needing improvement, particularly in redirects, meta descriptions, and heading structure. Implementing these changes will enhance search visibility and performance.
- 1
Fix Chained Redirects
Why: Chained redirects can negatively impact loading speed and user experience.
How: Identify and remove or simplify chained redirects to ensure a direct link to the final destination.
Checks: redirects
- 2
Add Missing Meta Descriptions
Why: Missing meta descriptions can reduce click-through rates from search results.
How: Create compelling meta descriptions for 119 pages where they're missing to improve visibility.
Evidence: 119 pages have no meta description at all.
119 pages affected
Checks: meta-descriptions
- 3
Add H1 Tags
Why: Missing H1 tags can hurt SEO and make content less discoverable.
How: Add a relevant H1 tag to the 6 pages currently missing one to improve structure and SEO.
Evidence: 6 pages: missing h1.
6 pages affected
- https://www.smilesourcespokane.com/
- https://www.smilesourcespokane.com/north-side-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/south-hill-wa/home-2/
- https://www.smilesourcespokane.com/south-hill-wa/new-patients/special-offers/
- https://www.smilesourcespokane.com/spokane-valley-wa/new-patients/special-offers/
Checks: headings
- 4
Shrink Heavy Assets
Why: Large assets slow down page load times, impacting user experience.
How: Compress or optimize the specified large media files to improve loading times.
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
- 5
Link to Orphan Pages
Why: Orphan pages lack internal links and may not be indexed effectively.
How: Create internal links within the site to the 25 orphan pages to improve discoverability.
Checks: orphan-pages
- 6
Improve Thin Content
Why: Pages with thin content may rank poorly in search engines.
How: Enhance content on the 5 pages with fewer than 200 words to provide more value to users.
Checks: thin-content
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 crawlYour website has several security vulnerabilities that need addressing, particularly around HTTP headers and a vulnerable JavaScript library. Key measures like HTTP Strict Transport Security and Content Security Policy are missing, leaving the site susceptible to various attacks. Immediate action is recommended to enhance your site's security posture.
- 0 high
- 5 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted when accessing the site via HTTP.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: A lack of CSP enables unrestricted loading of scripts and resources, increasing XSS risks.
Fix: Add the header: Content-Security-Policy: default-src 'self'
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without this header, your site is vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Vulnerable JavaScript Library DetectedMedium
Why it matters: jQuery 3.3.1 has known vulnerabilities that could be exploited.
Fix: Upgrade jQuery to version 3.5.0 or later.
Evidence: Vulnerable JavaScript libraries
- 5
Exposed Google API Key in Page CodeMedium
Why it matters: An exposed key may lead to unauthorized access and usage of your API.
Fix: Restrict the API key usage via HTTP referrer in the Google Cloud console.
Evidence: Keys and secrets in page code
- 6
Server Banner Revealing Exact VersionLow
Why it matters: Disclosing server versions allows attackers to exploit known vulnerabilities.
Fix: Configure the server to hide or modify the 'Server' response header.
Evidence: Software version disclosure
- 7
Third-Party Scripts without Subresource Integrity (SRI)Low
Why it matters: Absence of SRI means changes to third-party scripts may compromise your site.
Fix: Consider implementing a Content-Security-Policy that whitelists trusted hosts.
Evidence: Third-party scripts
- 8
Missing Permissions-Policy HeaderInfo
Why it matters: This header limits browser features, reducing the impact of potential script injection.
Fix: Add the header: Permissions-Policy: interest-cohort=()
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.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.
- myconceptdentistry.com78/100 · rank 1121 · 36 pages
- subzerotechnical.com78/100 · rank 1121 · 43 pages
- maidensail.com78/100 · rank 1121 · 200 pages
- www.petetheplumber.com77/100 · rank 1216 · 166 pages
- www.aestheticdentalstudio.ca77/100 · rank 1216 · 233 pages
- www.bvcvet.ca77/100 · rank 1216 · 24 pages
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.