Scanned sites / www.cresteyecare.com / 2026-09-11-1847
www.cresteyecare.com scan from 2026-09-11 18:47:04 UTC DR 11
A newer scan exists. See the latest report for www.cresteyecare.com.
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-09-11-1847
Scanned 2026-09-11 18:47:04 UTC, finished 2026-09-11 18:55:54 UTC
Site: https://www.cresteyecare.com/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On September 11, 2026 the Site Spider crawled 174 pages and 166 assets of www.cresteyecare.com, starting from https://www.cresteyecare.com/. It scored 87 out of 100, a good result. 8 of 27 checks found something to fix, led by title tags (48), meta descriptions (54), sitemap coverage (56); 7 checks passed. Most of the points went to title tags (−3.4), meta descriptions (−3.1), heavy assets (−2.4). 12 checks found something the score does not count, listed as noted. 10 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: Medium2 medium, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 174
- Assets fetched
- 166
- Status
- Completed
- Checks with issues
- 8 of 27
340 of 340 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 21 link destinations on other sites were checked.
- Title tags48 issues48 of 135 pages have title issues. 5 noindex or canonicalized pages excluded.−3.4 points
- Meta descriptions54 issues54 of 135 pages have meta description issues. 5 noindex or canonicalized pages excluded.−3.1 points
- HeadingsOK0 of 135 pages have heading issues. 5 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites703 noted0 destinations answered with an error, 8 could not be determined (timeouts, rate limits or refusals), of 19 destinations checked.
- Redirects37 issues38 redirecting URLs, 10 of them chained.−1.1 points
- Non-200 responses38 noted38 URLs did not return a 2xx response. 34 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability2 issues2 of 137 indexable pages have indexability warnings. 3 pages noindex by design.−0.1 points
- Image alt text49 issues49 of 970 image references have no alt attribute. 10 use an empty alt (decorative), which is fine.−0.3 points
- Heavy assets4 issues4 assets larger than 500 KB among 166 fetched assets.−2.4 points
- Orphan pages19 issues19 pages have no internal links pointing at them.−0.5 points
- Sitemap coverage56 issues1 sitemap listing 98 URLs: 37 crawled pages missing, 0 listed URLs broken or redirecting, 19 reachable only via the sitemap.−2.4 points
- Internal link counts4 notedInternal link counts for 140 pages; 4 worth a look.
- Thin contentOK0 of 135 pages have fewer than 200 words. 5 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format11 noted11 of 174 page URLs are harder to read, share or cache than they need to be.
- Canonicals4 noted4 of 140 pages have a canonical worth checking.
- Robots directives37 noted37 pages carry a robots directive; 103 carry none.
- Anchor text8 noted8 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure21 noted21 of 135 pages could use the title, heading and snippet space better. 5 noindex or canonicalized pages excluded.
- Image weight and alt length1 noted0 images over 100 KB; 1 with alt text over 100 characters.
- Response anomalies4 noted4 URLs answered in a way worth looking at.
- HTML and head validationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- hreflangNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Structured dataNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Near duplicatesNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Soft 404s2 noted2 pages answer 200 but say they are not there.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Headers and cookiesOK0 cookies set by the site; 14 response headers recorded across 340 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 140 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 Insights5 notedMobile performance 66 on average across 5 pages; 5 below Google's good thresholds.
- SpellingNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
Where this scan sits among all scanned sites
2325 sites, median 79%, average 78%
www.cresteyecare.com scores 87%, higher than 80% of the 2325 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...
Security review
Written by gpt-4o-mini from 16 checks over the crawlThe site has security vulnerabilities that need addressing, including missing security headers and exposed API keys. Implementing strict transport security and securing API keys are crucial to prevent potential interception and misuse.
- 0 high
- 2 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors using HTTP may be intercepted on their first request.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.
Evidence: HTTP Strict Transport Security
- 2
Exposed Google API KeyMedium
Why it matters: An exposed API key can be misused, leading to increased costs or data exposure.
Fix: Restrict the API key in the Google Cloud console by HTTP referrer and remove it from public access.
Evidence: Keys and secrets in page code
- 3
Server Version DisclosureLow
Why it matters: Revealing server version allows attackers to exploit known vulnerabilities.
Fix: Configure the server to hide the version details, e.g., set 'server_tokens off' in nginx.
Evidence: Software version disclosure
- 4
Missing Subresource Integrity on Third-Party ScriptsLow
Why it matters: Scripts from external sources can change if those sources are compromised.
Fix: Use Subresource Integrity (SRI) attributes with the script tags or add a Content-Security-Policy to restrict sources.
Evidence: Third-party scripts
- 5
Sensitive Paths in robots.txtInfo
Why it matters: Public paths may reveal sensitive areas of the site, aiding malicious probing.
Fix: Implement access controls on /wp-admin/ and /wp-login.php instead of relying on robots.txt.
Evidence: Sensitive paths in robots.txt
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.cresteyecare.com/ → no strict-transport-security
- https://www.cresteyecare.com/hours-location/ → no strict-transport-security
- https://www.cresteyecare.com/hours-location/pembina/ → no strict-transport-security
- https://www.cresteyecare.com/hours-location/regent-ave/ → no strict-transport-security
- https://www.cresteyecare.com/our-eye-doctors/ → no strict-transport-security
- https://www.cresteyecare.com/team/tavleen-singh/ → no strict-transport-security
- https://www.cresteyecare.com/team/dr-louis-crust/ → no strict-transport-security
- https://www.cresteyecare.com/team/dr-tola-opejin/ → no strict-transport-security
- https://www.cresteyecare.com/eye-care-services/ → no strict-transport-security
- https://www.cresteyecare.com/eye-care-services/dry-eye-disease-and-treatment/ → no strict-transport-security
- https://www.cresteyecare.com/eyeglasses/ → no strict-transport-security
- https://www.cresteyecare.com/eyeglasses/designer-frames/ → no strict-transport-security
- FoundSoftware version disclosureLow
Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.
- server: nginx/1.26.3 (340 responses)
- FoundKeys and secrets in page codeMedium
1 credential-like value found in code served to every visitor: Google API key.
- Google API key AIzaSy…uY (39 chars) in https://www.cresteyecare.com/hours-location/: 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.)
- www.googletagmanager.com (40 script tags)
- www.googleadservices.com (40 script tags)
- NoteSensitive paths in robots.txt
robots.txt lists 2 paths 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: /wp-admin/
- Disallow: /wp-login.php
8 checks passed, 3 not applicable
- OKHTTPS
All 140 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set.
- OKClickjacking protection
x-frame-options is set on all 140 HTML pages.
- OKMIME sniffing protection
x-content-type-options is set on all 140 HTML pages.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
143 forms found, all on HTTPS pages posting to HTTPS addresses.
- OKVulnerable JavaScript libraries
2 library versions recognised, none with known vulnerabilities.
- OKExposed files and listings
None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.
- Not applicableReferrer policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicablePermissions policy
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
- Not applicableCookie flags
This scan predates the crawler recording the headers this check needs. Rescan the site to check it.
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.cresteyecare.com
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- apolloplumbing.caDR 1087/100 · rank 387 · 49 pages
- www.saskatoondowntowndentist.caDR 787/100 · rank 387 · 36 pages
- sheyennedental.comDR 087/100 · rank 387 · 52 pages
- optixgallery.comDR 1987/100 · rank 387 · 84 pages
- www.crosscountrymechanical.caDR 987/100 · rank 387 · 81 pages
- drstom.ruDR 387/100 · rank 387 · 70 pages
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.cresteyecare.com from its pages as published, the way a search engine does. It shows summary figures only.
Own www.cresteyecare.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.cresteyecare.com. Removal needs no account and no proof of purchase.