Scanned sites / danceforks.ca / 2026-10-03-1303

danceforks.ca scan from 10/3/2026, 1:03:03 PM

Scan 2026-10-03-1303

Scanned 10/3/2026, 1:03:03 PM, finished 10/3/2026, 3:29:35 PM. Found on page 5 of brave web search results

Site: https://danceforks.ca/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

73/ 100Needs work

On October 3, 2026 the Site Spider crawled 82 pages and 657 assets of danceforks.ca, starting from https://danceforks.ca/. It scored 73 out of 100, a result that needs work. 12 of 16 checks found something to fix, led by meta descriptions (63), heavy assets (13), sitemap coverage (37); 3 checks passed. Most of the points went to meta descriptions (−7.6), heavy assets (−6), sitemap coverage (−3.4). 1 check 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: Medium6 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
82
Assets fetched
657
Status
Completed
Checks with issues
12 of 16
CoverageComplete crawl

739 of 744 discovered URLs were fetched, 5 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 31 link destinations on other sites were checked.

  • Title tags9 issues
    9 of 63 pages have title issues. 3 noindex or canonicalized pages excluded.
    −1.4 points
  • Meta descriptions63 issues
    63 of 63 pages have meta description issues. 3 noindex or canonicalized pages excluded.
    −7.6 points
  • Headings3 issues
    3 of 63 pages have heading issues. 3 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken links5 issues
    5 internal links point at 5 broken URLs.
    −1.5 points
  • Links to other sites2 issues
    2 destinations answered with an error, 15 could not be determined (timeouts, rate limits or refusals), of 31 destinations checked.
    −0.8 points
  • Redirects11 issues
    12 redirecting URLs, 0 of them chained.
    −0.7 points
  • Non-200 responses5 issues
    29 URLs did not return a 2xx response. 16 of them are pages, 5 with an error status; the rest are assets or redirects.
    −0.8 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability8 issues
    8 of 64 indexable pages have indexability warnings. 2 pages noindex by design.
    −1.2 points
  • Image alt textOK
    0 of 406 image references have no alt attribute. 142 use an empty alt (decorative), which is fine.
  • Heavy assets13 issues
    13 assets larger than 500 KB among 657 fetched assets.
    −6 points
  • Orphan pages31 issues
    31 pages have no internal links pointing at them.
    −1.9 points
  • Sitemap coverage37 issues
    5 sitemaps listing 57 URLs: 6 crawled pages missing, 0 listed URLs broken or redirecting, 31 reachable only via the sitemap.
    −3.4 points
  • Internal link countsOK
    Internal link counts for 66 pages.
  • Thin content18 issues
    18 of 63 pages have fewer than 200 words. 3 noindex or canonicalized pages excluded.
    −2.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

2008 sites, median 80%, average 79%

danceforks.ca scores 73%, higher than 23% of the 2008 scanned sites. See the full ranking.

0571140%: 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%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 5 sites56%: 7 sites57%: 7 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 13 sites65%: 23 sites66%: 24 sites67%: 37 sites68%: 33 sites69%: 28 sites70%: 41 sites71%: 46 sites72%: 59 sites73%: 56 sites74%: 51 sites75%: 65 sites76%: 79 sites77%: 77 sites78%: 94 sites79%: 73 sites80%: 96 sites81%: 114 sites82%: 89 sites83%: 90 sites84%: 91 sites85%: 72 sites86%: 75 sites87%: 70 sites88%: 66 sites89%: 56 sites90%: 38 sites91%: 42 sites92%: 32 sites93%: 17 sites94%: 12 sites95%: 13 sites96%: 8 sites97%: 9 sites98%: 2 sites99%: 2 sites100%: 55 sites73% 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 improvements for better SEO performance. Focus on broken links, meta descriptions, and optimizing asset sizes.

  1. 1

    Fix Broken Links

    Why: Broken links can harm user experience and SEO.

    How: Update or remove the 5 broken URLs listed in your internal links.

    Checks: broken-links

  2. 2

    Add Meta Descriptions

    Why: Meta descriptions are crucial for CTR and search visibility.

    How: Create descriptive meta descriptions for all 63 pages without one.

    Checks: meta-descriptions

  3. 3

    Optimize Heavy Assets

    Why: Reducing asset size improves site speed and user experience.

    How: Shrinking identified heavy assets will enhance performance.

    Checks: heavy-assets

  4. 4

    Resolve Non-200 Responses

    Why: Fixing non-200 responses enhances crawlability and user access.

    How: Address the 29 URLs that currently return invalid responses.

    Checks: status-codes

  5. 5

    Improve Title Tags

    Why: Optimized titles help with search rankings.

    How: Revise the 9 title tags with issues to be concise and unique.

    Checks: titles

  6. 6

    Address Orphan Pages

    Why: Linking orphaned pages improves their SEO value and navigation.

    How: Internal links to these 31 orphan pages will increase 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 crawl

The website has several critical security shortcomings, including the absence of headers that protect against common threats such as data interception, clickjacking, and content injection. Additionally, there are outdated libraries with known vulnerabilities and exposure of sensitive API keys. Immediate remedial actions are advised.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: HSTS prevents interception of users' first requests when they access the site via HTTP.

    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: Without CSP, there's no restriction on where scripts and styles may load from, risking XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, attackers can embed your pages and overlay them with malicious controls.

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

    Evidence: Clickjacking protection

  4. 4

    Cookie Flags MissingMedium

    Why it matters: Cookies lacking protective flags may be read by scripts or transmitted in insecure contexts.

    Fix: Set the cookie with HttpOnly, Secure, and SameSite attributes.

    Evidence: Cookie flags

  5. 5

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated libraries with known vulnerabilities can be exploited based on site usage.

    Fix: Upgrade jQuery to at least 3.5.0, jQuery UI to at least 1.13.2, and Bootstrap to at least 4.3.1.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Leaked Google API KeyMedium

    Why it matters: Exposing API keys in public code poses risks if not properly restricted.

    Fix: Restrict the API key by HTTP referrer in Google Cloud console.

    Evidence: Keys and secrets in page code

  7. 7

    Missing X-Content-Type-Options HeaderLow

    Why it matters: This omission can allow browsers to execute files as scripts based on their contents.

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

    Evidence: MIME sniffing protection

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: This policy limits browser features, reducing risk if an attacker injects a script.

    Fix: Add the header: Permissions-Policy: geolocation=(self).

    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://danceforks.ca/ → no strict-transport-security
    • https://danceforks.ca/faculty-staff/ → no strict-transport-security
    • https://danceforks.ca/program-info/ → no strict-transport-security
    • https://danceforks.ca/schedule/ → no strict-transport-security
    • https://danceforks.ca/bright-minds-happy-feet/ → no strict-transport-security
    • https://danceforks.ca/bright-minds-happy-feet/our-programs-bright-minds-happy-feet/ → no strict-transport-security
    • https://danceforks.ca/bright-minds-happy-feet/parent-policy-handbook/ → no strict-transport-security
    • https://danceforks.ca/category/the-dancediaries-blog/ → no strict-transport-security
    • https://danceforks.ca/contact/ → no strict-transport-security
    • https://danceforks.ca/faculty-staff/kendra-blake-director/ → no strict-transport-security
    • https://danceforks.ca/faculty-staff/carla-hawkins-office-manager/ → no strict-transport-security
    • https://danceforks.ca/faculty-staff/taryn-bennett/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 66 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://danceforks.ca/ → no content-security-policy
    • https://danceforks.ca/faculty-staff/ → no content-security-policy
    • https://danceforks.ca/program-info/ → no content-security-policy
    • https://danceforks.ca/schedule/ → no content-security-policy
    • https://danceforks.ca/bright-minds-happy-feet/ → no content-security-policy
    • https://danceforks.ca/bright-minds-happy-feet/our-programs-bright-minds-happy-feet/ → no content-security-policy
    • https://danceforks.ca/bright-minds-happy-feet/parent-policy-handbook/ → no content-security-policy
    • https://danceforks.ca/category/the-dancediaries-blog/ → no content-security-policy
    • https://danceforks.ca/contact/ → no content-security-policy
    • https://danceforks.ca/faculty-staff/kendra-blake-director/ → no content-security-policy
    • https://danceforks.ca/faculty-staff/carla-hawkins-office-manager/ → no content-security-policy
    • https://danceforks.ca/faculty-staff/taryn-bennett/ → no content-security-policy
  • FoundClickjacking protectionMedium

    2 of 66 HTML pages send 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://danceforks.ca/ → no x-frame-options
    • https://danceforks.ca/faculty-staff/ → no x-frame-options
    • https://danceforks.ca/program-info/ → no x-frame-options
    • https://danceforks.ca/schedule/ → no x-frame-options
    • https://danceforks.ca/bright-minds-happy-feet/ → no x-frame-options
    • https://danceforks.ca/bright-minds-happy-feet/our-programs-bright-minds-happy-feet/ → no x-frame-options
    • https://danceforks.ca/bright-minds-happy-feet/parent-policy-handbook/ → no x-frame-options
    • https://danceforks.ca/category/the-dancediaries-blog/ → no x-frame-options
    • https://danceforks.ca/contact/ → no x-frame-options
    • https://danceforks.ca/faculty-staff/kendra-blake-director/ → no x-frame-options
    • https://danceforks.ca/faculty-staff/carla-hawkins-office-manager/ → no x-frame-options
    • https://danceforks.ca/faculty-staff/taryn-bennett/ → 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://danceforks.ca/ → no x-content-type-options
    • https://danceforks.ca/faculty-staff/ → no x-content-type-options
    • https://danceforks.ca/program-info/ → no x-content-type-options
    • https://danceforks.ca/schedule/ → no x-content-type-options
    • https://danceforks.ca/bright-minds-happy-feet/ → no x-content-type-options
    • https://danceforks.ca/bright-minds-happy-feet/our-programs-bright-minds-happy-feet/ → no x-content-type-options
    • https://danceforks.ca/bright-minds-happy-feet/parent-policy-handbook/ → no x-content-type-options
    • https://danceforks.ca/category/the-dancediaries-blog/ → no x-content-type-options
    • https://danceforks.ca/contact/ → no x-content-type-options
    • https://danceforks.ca/faculty-staff/kendra-blake-director/ → no x-content-type-options
    • https://danceforks.ca/faculty-staff/carla-hawkins-office-manager/ → no x-content-type-options
    • https://danceforks.ca/faculty-staff/taryn-bennett/ → no x-content-type-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://danceforks.ca/ → no permissions-policy
    • https://danceforks.ca/faculty-staff/ → no permissions-policy
    • https://danceforks.ca/program-info/ → no permissions-policy
    • https://danceforks.ca/schedule/ → no permissions-policy
    • https://danceforks.ca/bright-minds-happy-feet/ → no permissions-policy
    • https://danceforks.ca/bright-minds-happy-feet/our-programs-bright-minds-happy-feet/ → no permissions-policy
    • https://danceforks.ca/bright-minds-happy-feet/parent-policy-handbook/ → no permissions-policy
    • https://danceforks.ca/category/the-dancediaries-blog/ → no permissions-policy
    • https://danceforks.ca/contact/ → no permissions-policy
    • https://danceforks.ca/faculty-staff/kendra-blake-director/ → no permissions-policy
    • https://danceforks.ca/faculty-staff/carla-hawkins-office-manager/ → no permissions-policy
    • https://danceforks.ca/faculty-staff/taryn-bennett/ → no permissions-policy
  • FoundCookie flagsMedium

    1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.

    • wordpress_test_cookie (set by https://danceforks.ca/wp-login.php) lacks HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

    3 libraries with published vulnerabilities: jQuery 1.9.1, jQuery UI 1.13.1, Bootstrap 4.0.0. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://danceforks.ca/wp-content/themes/atelier/js/lib/bootstrap.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
    • jQuery UI 1.13.1 in https://danceforks.ca/wp-includes/js/jquery/ui/core.min.js?ver=1.13.1: CVE-2022-31160 (checkboxradio XSS); fixed in 1.13.2
    • Bootstrap 4.0.0 in https://danceforks.ca/wp-content/themes/atelier/js/lib/bootstrap.min.js: CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 4.3.1
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…5U (39 chars) in https://danceforks.ca/: 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 5 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.)

    • cdnjs.cloudflare.com (39 script tags)
    • widgets.leadconnectorhq.com (39 script tags)
    • maps.google.com (39 script tags)
    • www.google.com (39 script tags)
    • app.jackrabbitclass.com (27 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path 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/
6 checks passed
  • OKHTTPS

    All 66 crawled pages were served over HTTPS.

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    41 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

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 danceforks.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 danceforks.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own danceforks.ca?

danceforks.ca scan 2026-10-03-1303 | DIY SEO Hub