Scanned sites / www.crownautobody.ca / 2026-10-05-1509
www.crownautobody.ca scan from 10/5/2026, 3:09:18 PM
Scan 2026-10-05-1509
Scanned 10/5/2026, 3:09:18 PM, finished 10/5/2026, 3:19:43 PM. Found with openstreetmap overpass
Site: https://www.crownautobody.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 5, 2026 the Site Spider crawled 131 pages and 390 assets of www.crownautobody.ca, starting from https://www.crownautobody.ca/. It scored 53 out of 100, a result that needs work. 9 of 22 checks found something to fix, led by broken links (65), non-200 responses (65), meta descriptions (50); 5 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), meta descriptions (−6.3). 8 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: Medium4 medium, 3 low and 1 info findings. See the security findings ↓
- Pages crawled
- 131
- Assets fetched
- 390
- Status
- Completed
- Checks with issues
- 9 of 22
521 of 521 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 16 link destinations on other sites have not been checked.
- Title tags22 issues22 of 59 pages have title issues. 4 noindex or canonicalized pages excluded.−3.5 points
- Meta descriptions50 issues50 of 59 pages have meta description issues. 4 noindex or canonicalized pages excluded.−6.3 points
- Headings8 issues8 of 59 pages have heading issues. 4 noindex or canonicalized pages excluded.−0.8 points
- Broken links65 issues65 internal links point at 65 broken URLs.−20 points
- Links to other sitesNot checkedNot checked: the crawl fetched nothing this check can look at.
- Redirects3 issues4 redirecting URLs, 0 of them chained.−0.2 points
- Non-200 responses65 issues69 URLs did not return a 2xx response. 68 of them are pages, 65 with an error status; the rest are assets or redirects.−10 points
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 59 indexable pages have indexability warnings. 4 pages noindex by design.
- Image alt textOK0 of 554 image references have no alt attribute. 248 use an empty alt (decorative), which is fine.
- Heavy assets7 issues7 assets larger than 500 KB among 390 fetched assets.−4.2 points
- Orphan pages16 issues16 pages have no internal links pointing at them.−1 points
- Sitemap coverage16 issues4 sitemaps listing 59 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 16 reachable only via the sitemap.−1.5 points
- Internal link counts4 notedInternal link counts for 63 pages; 4 worth a look.
- Thin contentOK0 of 59 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format6 noted6 of 131 page URLs are harder to read, share or cache than they need to be.
- Canonicals4 noted4 of 63 pages have a canonical worth checking.
- Robots directives63 noted63 pages carry a robots directive; 0 carry none.
- Anchor text30 noted30 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure42 noted42 of 59 pages could use the title, heading and snippet space better. 4 noindex or canonicalized pages excluded.
- Image weight and alt length18 noted18 images over 100 KB; 0 with alt text over 100 characters.
- Response anomalies2 noted2 URLs answered in a way worth looking at.
Where this scan sits among all scanned sites
2080 sites, median 79%, average 78%
www.crownautobody.ca scores 53%, higher than 3% of the 2080 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 findingsYour site has several critical issues affecting SEO performance. Prioritizing fixes for broken links, heavy assets, and title/meta issues will significantly improve your site's health and user experience.
- 1
Fix Broken Links
Why: 65 internal links lead to broken URLs, affecting user experience and SEO.
How: Identify and update or remove broken links using a tool. Refer to task broken-links:rqy4vl for specific URLs.
Checks: broken-links
- 2
Optimize Heavy Assets
Why: Large assets can slow down page loading, affecting user retention and SEO rankings.
How: Compress or optimize assets from the list, prioritizing the largest ones first. Refer to tasks heavy-assets:8tihqx and others for specific assets.
Checks: heavy-assets
- 3
Revise Title Tags
Why: 22 title tags exceed recommended length, reducing search visibility.
How: Shorten titles to 60 characters or less to enhance clarity. Review titles in the list.
Checks: titles
- 4
Create Missing Meta Descriptions
Why: 50 pages lack meta descriptions, diminishing click-through rates from search results.
How: Draft concise meta descriptions for these pages, less than 160 characters. Use task meta-descriptions:cocw75 for guidance.
Checks: meta-descriptions
- 5
Address Heading Issues
Why: 8 pages have missing or multiple H1 tags, impacting content structure and SEO.
How: Ensure each page has a single H1 that accurately represents its content. Review headings as needed.
Checks: headings
- 6
Link Orphan Pages
Why: 16 orphan pages have no internal links, making them hard to discover.
How: Add internal links to these pages from relevant sections of your site to improve their visibility.
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 crawlThe website lacks several important security headers that can expose users to risks such as data interception and clickjacking. Additionally, the use of outdated libraries could lead to vulnerabilities, impacting the site's security. Immediate attention to these issues is recommended.
- 0 high
- 4 medium
- 3 low
- 1 info
- 1
Lack of HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users without HTTPS in the URL are vulnerable to interception.
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: Without CSP, there are no restrictions on where scripts or styles may load from, risking XSS attacks.
Fix: Add a Content-Security-Policy header restricting sources, e.g., Content-Security-Policy: default-src 'self';
Evidence: Content Security Policy
- 3
Missing Clickjacking ProtectionMedium
Why it matters: Lack of X-Frame-Options allows the site to be embedded in frames, posing clickjacking risks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Use of Vulnerable JavaScript LibrariesMedium
Why it matters: jQuery 1.9.1 has multiple known vulnerabilities, increasing the site’s risk profile.
Fix: Upgrade jQuery to version 3.5.0 or later.
Evidence: Vulnerable JavaScript libraries
- 5
Missing MIME Sniffing ProtectionLow
Why it matters: Without X-Content-Type-Options, browsers may incorrectly interpret file types, leading to security issues.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 6
No Referrer PolicyLow
Why it matters: Absence of a Referrer Policy may expose sensitive URL data when users navigate away.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 7
Server and Framework Version DisclosureLow
Why it matters: Revealing server details helps attackers target known vulnerabilities.
Fix: Remove or alter headers: server: Apache and x-powered-by: PHP/7.4.33
Evidence: Software version disclosure
- 8
Missing Permissions PolicyInfo
Why it matters: Not implementing Permissions-Policy may allow injected scripts greater access to user features.
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.crownautobody.ca/ → no strict-transport-security
- https://www.crownautobody.ca/about-us/ → no strict-transport-security
- https://www.crownautobody.ca/why-us/ → no strict-transport-security
- https://www.crownautobody.ca/services/ → no strict-transport-security
- https://www.crownautobody.ca/process/ → no strict-transport-security
- https://www.crownautobody.ca/blogs/ → no strict-transport-security
- https://www.crownautobody.ca/faq/ → no strict-transport-security
- https://www.crownautobody.ca/mpi-direct-repair/ → no strict-transport-security
- https://www.crownautobody.ca/car-rental/ → no strict-transport-security
- https://www.crownautobody.ca/glass-repair/ → no strict-transport-security
- https://www.crownautobody.ca/towing/ → no strict-transport-security
- https://www.crownautobody.ca/in-case-of-accident/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 63 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.crownautobody.ca/ → no content-security-policy
- https://www.crownautobody.ca/about-us/ → no content-security-policy
- https://www.crownautobody.ca/why-us/ → no content-security-policy
- https://www.crownautobody.ca/services/ → no content-security-policy
- https://www.crownautobody.ca/process/ → no content-security-policy
- https://www.crownautobody.ca/blogs/ → no content-security-policy
- https://www.crownautobody.ca/faq/ → no content-security-policy
- https://www.crownautobody.ca/mpi-direct-repair/ → no content-security-policy
- https://www.crownautobody.ca/car-rental/ → no content-security-policy
- https://www.crownautobody.ca/glass-repair/ → no content-security-policy
- https://www.crownautobody.ca/towing/ → no content-security-policy
- https://www.crownautobody.ca/in-case-of-accident/ → 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.crownautobody.ca/ → no x-frame-options
- https://www.crownautobody.ca/about-us/ → no x-frame-options
- https://www.crownautobody.ca/why-us/ → no x-frame-options
- https://www.crownautobody.ca/services/ → no x-frame-options
- https://www.crownautobody.ca/process/ → no x-frame-options
- https://www.crownautobody.ca/blogs/ → no x-frame-options
- https://www.crownautobody.ca/faq/ → no x-frame-options
- https://www.crownautobody.ca/mpi-direct-repair/ → no x-frame-options
- https://www.crownautobody.ca/car-rental/ → no x-frame-options
- https://www.crownautobody.ca/glass-repair/ → no x-frame-options
- https://www.crownautobody.ca/towing/ → no x-frame-options
- https://www.crownautobody.ca/in-case-of-accident/ → no x-frame-options
- FoundMIME sniffing protectionLow
No HTML page sends x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.
- https://www.crownautobody.ca/ → no x-content-type-options
- https://www.crownautobody.ca/about-us/ → no x-content-type-options
- https://www.crownautobody.ca/why-us/ → no x-content-type-options
- https://www.crownautobody.ca/services/ → no x-content-type-options
- https://www.crownautobody.ca/process/ → no x-content-type-options
- https://www.crownautobody.ca/blogs/ → no x-content-type-options
- https://www.crownautobody.ca/faq/ → no x-content-type-options
- https://www.crownautobody.ca/mpi-direct-repair/ → no x-content-type-options
- https://www.crownautobody.ca/car-rental/ → no x-content-type-options
- https://www.crownautobody.ca/glass-repair/ → no x-content-type-options
- https://www.crownautobody.ca/towing/ → no x-content-type-options
- https://www.crownautobody.ca/in-case-of-accident/ → no x-content-type-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.crownautobody.ca/ → no referrer-policy
- https://www.crownautobody.ca/about-us/ → no referrer-policy
- https://www.crownautobody.ca/why-us/ → no referrer-policy
- https://www.crownautobody.ca/services/ → no referrer-policy
- https://www.crownautobody.ca/process/ → no referrer-policy
- https://www.crownautobody.ca/blogs/ → no referrer-policy
- https://www.crownautobody.ca/faq/ → no referrer-policy
- https://www.crownautobody.ca/mpi-direct-repair/ → no referrer-policy
- https://www.crownautobody.ca/car-rental/ → no referrer-policy
- https://www.crownautobody.ca/glass-repair/ → no referrer-policy
- https://www.crownautobody.ca/towing/ → no referrer-policy
- https://www.crownautobody.ca/in-case-of-accident/ → 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.crownautobody.ca/ → no permissions-policy
- https://www.crownautobody.ca/about-us/ → no permissions-policy
- https://www.crownautobody.ca/why-us/ → no permissions-policy
- https://www.crownautobody.ca/services/ → no permissions-policy
- https://www.crownautobody.ca/process/ → no permissions-policy
- https://www.crownautobody.ca/blogs/ → no permissions-policy
- https://www.crownautobody.ca/faq/ → no permissions-policy
- https://www.crownautobody.ca/mpi-direct-repair/ → no permissions-policy
- https://www.crownautobody.ca/car-rental/ → no permissions-policy
- https://www.crownautobody.ca/glass-repair/ → no permissions-policy
- https://www.crownautobody.ca/towing/ → no permissions-policy
- https://www.crownautobody.ca/in-case-of-accident/ → 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: Apache (521 responses)
- x-powered-by: PHP/7.4.33 (137 responses)
- FoundVulnerable JavaScript librariesMedium
1 library with published vulnerabilities: jQuery 1.9.1. Whether they are exploitable depends on how the site uses them, but each has a fixed release.
- jQuery 1.9.1 in https://progisync.progi.com/public/lib_booking_widget/js/jquery-1.9.1.min.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
- 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)
- img1.wsimg.com (40 script tags)
6 checks passed, 1 not applicable
- OKHTTPS
All 63 crawled pages were served over HTTPS.
- 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.
- OKKeys and secrets in page code
No API keys, tokens or private keys were found in the sampled HTML and scripts.
- 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.
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.crownautobody.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.ouder.site54/100 · rank 2009 · 6 pages
- cateyheritage.com54/100 · rank 2009 · 16 pages
- www.fairholmfarm.com54/100 · rank 2009 · 205 pages
- sygnexproduction.com53/100 · rank 2017 · 538 pages
- www.omniva.ee53/100 · rank 2017 · 1,755 pages
- www.highlandparkphysio.ca53/100 · rank 2017 · 52 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.crownautobody.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own www.crownautobody.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.crownautobody.ca. Removal needs no account and no proof of purchase.