Scanned sites / www.crownautobody.ca / 2026-10-04-1544

www.crownautobody.ca scan from 10/4/2026, 3:44:15 PM

A newer scan exists. See the latest report for www.crownautobody.ca.

Scan 2026-10-04-1544

Scanned 10/4/2026, 3:44:15 PM, finished 10/4/2026, 4:01:01 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.

51/ 100Needs work

On October 4, 2026 the Site Spider crawled 131 pages and 486 assets of www.crownautobody.ca, starting from https://www.crownautobody.ca/. It scored 51 out of 100, a result that needs work. 9 of 23 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). 9 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: Medium4 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
131
Assets fetched
486
Status
Completed
Checks with issues
9 of 23
CoverageComplete crawl

617 of 617 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 19 link destinations on other sites were checked.

  • Title tags22 issues
    22 of 59 pages have title issues. 4 noindex or canonicalized pages excluded.
    −3.5 points
  • Meta descriptions50 issues
    50 of 59 pages have meta description issues. 4 noindex or canonicalized pages excluded.
    −6.3 points
  • Headings8 issues
    8 of 59 pages have heading issues. 4 noindex or canonicalized pages excluded.
    −0.8 points
  • Broken links65 issues
    65 internal links point at 65 broken URLs.
    −20 points
  • Links to other sites69 noted
    0 destinations answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 19 destinations checked.
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses65 issues
    69 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 limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 59 indexable pages have indexability warnings. 4 pages noindex by design.
  • Image alt textOK
    0 of 554 image references have no alt attribute. 248 use an empty alt (decorative), which is fine.
  • Heavy assets14 issues
    14 assets larger than 500 KB among 486 fetched assets.
    −6 points
  • Orphan pages16 issues
    16 pages have no internal links pointing at them.
    −1 points
  • Sitemap coverage16 issues
    4 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 noted
    Internal link counts for 63 pages; 4 worth a look.
  • Thin contentOK
    0 of 59 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format6 noted
    6 of 131 page URLs are harder to read, share or cache than they need to be.
  • Canonicals4 noted
    4 of 63 pages have a canonical worth checking.
  • Robots directives63 noted
    63 pages carry a robots directive; 0 carry none.
  • Anchor text30 noted
    30 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure42 noted
    42 of 59 pages could use the title, heading and snippet space better. 4 noindex or canonicalized pages excluded.
  • Image weight and alt length18 noted
    18 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.

Where this scan sits among all scanned sites

2064 sites, median 79%, average 78%

www.crownautobody.ca scores 51%, higher than 2% of the 2064 scanned sites. See the full ranking.

0521030%: 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%: 1 site36%: 2 sites37%: 2 sites38%: 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%: 8 sites53%: 6 sites54%: 7 sites55%: 7 sites56%: 5 sites57%: 11 sites58%: 15 sites59%: 7 sites60%: 11 sites61%: 9 sites62%: 19 sites63%: 18 sites64%: 18 sites65%: 37 sites66%: 25 sites67%: 39 sites68%: 34 sites69%: 28 sites70%: 36 sites71%: 61 sites72%: 64 sites73%: 59 sites74%: 60 sites75%: 76 sites76%: 76 sites77%: 83 sites78%: 94 sites79%: 86 sites80%: 103 sites81%: 101 sites82%: 98 sites83%: 88 sites84%: 93 sites85%: 69 sites86%: 70 sites87%: 68 sites88%: 65 sites89%: 48 sites90%: 36 sites91%: 41 sites92%: 23 sites93%: 20 sites94%: 14 sites95%: 7 sites96%: 4 sites97%: 10 sites98%: 2 sites99%: 1 site100%: 57 sites51% 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 website has several issues that need attention, including broken links, title tag optimization, and missing meta descriptions. Addressing these will enhance your SEO and user experience.

  1. 1

    Fix Broken Links

    Why: 65 broken internal links can harm user experience and SEO.

    How: Update or remove links pointing to non-existent pages, like '[email protected]'.

    Checks: broken-links

  2. 2

    Optimize Title Tags

    Why: 22 pages with title issues impact search visibility.

    How: Shorten titles longer than 60 characters, e.g., 'Winnipeg Auto Body & Collision Repair' to 60 characters or less.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 50 pages lack proper meta descriptions, affecting click-through rates.

    How: Create concise meta descriptions (max 160 characters) for all pages missing them.

    Checks: meta-descriptions

  4. 4

    Add Missing H1 Headings

    Why: 8 pages are missing H1 headings, which can affect content structure.

    How: Ensure each page has a relevant H1 to improve relevance and hierarchy.

    Checks: headings

  5. 5

    Shrink Heavy Assets

    Why: Reducing large assets can improve loading times.

    How: Optimize or compress heavy assets over 500 KB, such as images from plugins.

    Checks: heavy-assets

  6. 6

    Link Orphan Pages Internally

    Why: 16 orphan pages cannot be found by users easily, impacting user experience.

    How: Add internal links to orphan pages from relevant locations 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 lacks several critical security headers and has outdated libraries, which could expose it to various security threats. Immediate action is needed to strengthen protection against attacks like XSS and information leakage. Implementing best practices will enhance the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users accessing the site over HTTP can be subject to man-in-the-middle attacks.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows for potential cross-site scripting (XSS) attacks as scripts can load from any source.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of X-Frame-Options makes the site vulnerable to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 1.9.1 exposes the site to known vulnerabilities including XSS.

    Fix: Upgrade jQuery to at least version 3.5.0

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, attackers may exploit MIME-type confusion issues.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Not specifying a referrer policy can lead to unnecessary data exposure when users navigate away from the site.

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

    Evidence: Referrer policy

  7. 7

    Server Banner DisclosureLow

    Why it matters: Revealing server versions can assist attackers in targeting known vulnerabilities effectively.

    Fix: Remove or obfuscate header: Server; Remove header: X-Powered-By

    Evidence: Software version disclosure

  8. 8

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Absence of SRI means that any compromise of third-party sites can affect your site.

    Fix: Implement Subresource Integrity in script tags or add a Content-Security-Policy specifying trusted sources.

    Evidence: Third-party scripts

  9. 9

    Missing Permissions PolicyInfo

    Why it matters: A Permissions-Policy can limit the functionalities available to unauthorized scripts.

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

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.
www.crownautobody.ca scan 2026-10-04-1544 | DIY SEO Hub