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

www.crownautobody.ca scan from 10/4/2026, 5:47:51 AM

Scan 2026-10-04-0547

Scanned 10/4/2026, 5:47:51 AM, finished 10/4/2026, 6:11:37 AM. 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 16 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). 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: 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 16
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 countsOK
    Internal link counts for 63 pages.
  • 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.

Where this scan sits among all scanned sites

2051 sites, median 80%, average 78%

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

0521040%: 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%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 3 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 14 sites62%: 16 sites63%: 19 sites64%: 16 sites65%: 28 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 24 sites70%: 46 sites71%: 48 sites72%: 64 sites73%: 57 sites74%: 57 sites75%: 73 sites76%: 83 sites77%: 76 sites78%: 96 sites79%: 78 sites80%: 104 sites81%: 102 sites82%: 99 sites83%: 91 sites84%: 87 sites85%: 74 sites86%: 76 sites87%: 66 sites88%: 67 sites89%: 52 sites90%: 39 sites91%: 39 sites92%: 32 sites93%: 18 sites94%: 14 sites95%: 10 sites96%: 6 sites97%: 9 sites98%: 1 site99%: 2 sites100%: 56 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 site needs several improvements, particularly addressing broken links and enhancing titles and meta descriptions. Prioritize fixing issues for a better user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links can hurt user experience and SEO. They lead to 404 errors which frustrate users and degrade site authority.

    How: Identify broken links in your content and either update them to point to correct URLs or remove them.

    Checks: broken-links

  2. 2

    Review Non-200 Responses

    Why: Non-200 responses indicate URL issues that can deter users. Correcting these will enhance site accessibility and trust.

    How: Check URLs returning non-200 responses and correct their statuses: either fix broken pages or update redirects as necessary.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improper title lengths can affect search engine visibility. Titles over 60 characters may get truncated in search results.

    How: Revise the titles to be under 60 characters, ensuring they are clear and contain primary keywords.

    Checks: titles

  4. 4

    Address Meta Description Issues

    Why: Missing or long meta descriptions limit click-through rates from search results. Optimizing them enhances their effectiveness.

    How: Create unique meta descriptions for pages missing them and ensure existing ones don't exceed the recommended length of 160 characters.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Proper headings improve content structure and assist with SEO. Missing or multiple H1 tags confuse search engines and users.

    How: Ensure each page contains one H1 tag and use proper hierarchy for H2 and H3 headings where necessary.

    Checks: headings

  6. 6

    Reduce Heavy Assets

    Why: Large assets can slow down your site, affecting performance and user experience. Shrinking these can improve load times.

    How: Compress images and scripts over 500KB or find alternative ways to serve them, such as using more efficient formats or CDN.

    Checks: heavy-assets

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 important security headers and is using an outdated JavaScript library, which could expose it to potential attacks. It is recommended to implement strict transport security, Content Security Policy, and other headers to enhance security. Updating the JavaScript library is also crucial.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users could be intercepted on their first HTTP request.

    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: Lacking a CSP allows unrestricted loading of scripts and resources.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header makes the site vulnerable to clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: The library, jQuery 1.9.1, contains vulnerabilities that could be exploited.

    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: Not having this header may allow browsers to incorrectly interpret files.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer Policy HeaderLow

    Why it matters: Without this, URLs of visited pages are fully exposed to third parties.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Revealing server versions helps attackers target known vulnerabilities.

    Fix: Remove the Server and X-Powered-By headers or configure to not disclose versions.

    Evidence: Software version disclosure

  8. 8

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Third-party scripts could be compromised, altering site behavior.

    Fix: Implement a Content Security Policy to specify trusted sources.

    Evidence: Third-party scripts

  9. 9

    Missing Permissions Policy HeaderInfo

    Why it matters: A Permissions Policy controls access to features that could be misused.

    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-0547 | DIY SEO Hub