Scanned sites / fbc.ca

SEO report for fbc.ca DR 40

The latest Site Spider scan of fbc.ca, with 1 scan on record. Each scan is at its own address, for example /domain/fbc-ca/2026-10-01-0021.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-10-01 00:21:14 UTC, finished 2026-10-01 06:42:48 UTC. Found on page 5 of brave web search results

Site: https://fbc.ca/

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

82/ 100Good

On October 1, 2026 the Site Spider crawled 1058 pages and 963 assets of fbc.ca, starting from https://fbc.ca/. It scored 82 out of 100, a good result. 8 of 27 checks found something to fix, led by heavy assets (25), meta descriptions (637), title tags (244); 9 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−5.8), title tags (−2.8). 10 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: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
1058
Assets fetched
963
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

2,021 of 2,034 discovered URLs were fetched, 13 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 433 left unchecked.

  • Title tags244 issues
    244 of 871 pages have title issues. 2 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions637 issues
    637 of 871 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −5.8 points
  • Headings50 issues
    50 of 871 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites13 issues
    13 destinations answered with an error, 125 could not be determined (timeouts, rate limits or refusals), 433 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.6 points
  • Redirects190 issues
    185 redirecting URLs, 35 of them chained.
    −0.9 points
  • Non-200 responses185 noted
    185 URLs did not return a 2xx response. 185 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 871 indexable pages have indexability warnings. 2 pages noindex by design.
  • Image alt textOK
    0 of 43 image references have no alt attribute.
  • Heavy assets25 issues
    25 assets larger than 500 KB among 963 fetched assets. 2 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages72 issues
    72 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage248 issues
    1 sitemap listing 714 URLs: 168 crawled pages missing, 11 listed URLs broken or redirecting, 69 reachable only via the sitemap.
    −1.7 points
  • Internal link counts108 noted
    Internal link counts for 500 pages; 108 worth a look.
  • Thin contentOK
    0 of 871 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format2 noted
    2 of 1058 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2 noted
    2 of 873 pages have a canonical worth checking.
  • Robots directives873 noted
    873 pages carry a robots directive; 0 carry none.
  • Anchor text43 noted
    43 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure391 noted
    391 of 871 pages could use the title, heading and snippet space better. 2 noindex or canonicalized pages excluded.
  • Image weight and alt length6 noted
    4 images over 100 KB; 2 with alt text over 100 characters.
  • Response anomalies28 noted
    28 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 873 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    1 cookie set by the site; 13 response headers recorded across 2021 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 873 pages; 813 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not 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 noted
    Mobile performance 47 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2909 sites, median 80%, average 79%

fbc.ca scores 82%, higher than 56% of the 2909 scanned sites. See the full ranking.

0761520%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites82% 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

Written from an earlier version of the analysis (rules v4). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

The site has a good health score, but there are several key issues to address for improved SEO. Focus on fixing redirects, title tags, meta descriptions, and managing heavy assets for a significant impact.

  1. 1

    Fix Redirects

    Why: Reducing redirects improves user experience and enhances crawl efficiency.

    How: Update the links to point directly to the final destination instead of redirect chains.

    Checks: redirects, status-codes

  2. 2

    Update Title Tags

    Why: Accurate and well-structured title tags enhance visibility and click-through rates.

    How: Revise long (>60 characters) and short (<30 characters) titles to meet best practices.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: Unique and concise meta descriptions boost search rankings and user engagement.

    How: Create unique meta descriptions for the identified pages, avoiding excessive length.

    Checks: meta-descriptions

  4. 4

    Optimize Headings

    Why: Proper heading structures enhance content organization and SEO.

    How: Ensure each page has a single H1 tag corresponding to the main topic and appropriate H2 tags.

    Checks: headings

  5. 5

    Reduce Heavy Assets

    Why: Lighter assets improve loading times and enhance user experience.

    How: Optimize or replace large assets over 500 KB to decrease page load times.

    Evidence: 499 KB of image, loaded by 27 pages, so every visitor to any of them downloads it.

    27 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  6. 6

    Fix Orphan Pages

    Why: Connecting orphan pages increases their visibility and SEO potential.

    How: Add internal links to orphan pages from relevant content across the 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

Your website has several security issues that need attention. These include missing security headers like X-Frame-Options and Content Security Policy, which could leave it vulnerable to attacks. Implementing these protections will help secure both user data and site integrity.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors can be intercepted if they access without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: A lack of CSP means scripts and resources can load from any source, risking cross-site scripting attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this header, pages can be embedded in frames, risking clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may misconstrue file types, potentially executing dangerous files.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-PolicyLow

    Why it matters: Without a Referrer Policy, sensitive URL information may be shared with external sites.

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

    Evidence: Referrer policy

  6. 6

    Mixed Content on HTTPS PagesLow

    Why it matters: Resources loaded over HTTP on secure pages can compromise data integrity.

    Fix: Update the resource URL to HTTPS: https://clicktotweet.com/img/tweet-graphic-1.png

    Evidence: Mixed content

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not using this header means unnecessary browser features may remain active.

    Fix: Add the header: Permissions-Policy: deny camera; deny microphone; deny geolocation;

    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://fbc.ca/ → no strict-transport-security
    • https://fbc.ca/consultation/ → no strict-transport-security
    • https://fbc.ca/services/tax-support/ → no strict-transport-security
    • https://fbc.ca/services/business-support/ → no strict-transport-security
    • https://fbc.ca/services/financial-and-estate-planning/ → no strict-transport-security
    • https://fbc.ca/services/risk-management/ → no strict-transport-security
    • https://fbc.ca/services/wealth-management/ → no strict-transport-security
    • https://fbc.ca/for/farmers/ → no strict-transport-security
    • https://fbc.ca/for/professional-services/ → no strict-transport-security
    • https://fbc.ca/for/trades/ → no strict-transport-security
    • https://fbc.ca/for/health-wellness/ → no strict-transport-security
    • https://fbc.ca/why-fbc/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 873 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://fbc.ca/ → no content-security-policy
    • https://fbc.ca/consultation/ → no content-security-policy
    • https://fbc.ca/services/tax-support/ → no content-security-policy
    • https://fbc.ca/services/business-support/ → no content-security-policy
    • https://fbc.ca/services/financial-and-estate-planning/ → no content-security-policy
    • https://fbc.ca/services/risk-management/ → no content-security-policy
    • https://fbc.ca/services/wealth-management/ → no content-security-policy
    • https://fbc.ca/for/farmers/ → no content-security-policy
    • https://fbc.ca/for/professional-services/ → no content-security-policy
    • https://fbc.ca/for/trades/ → no content-security-policy
    • https://fbc.ca/for/health-wellness/ → no content-security-policy
    • https://fbc.ca/why-fbc/ → 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://fbc.ca/ → no x-frame-options
    • https://fbc.ca/consultation/ → no x-frame-options
    • https://fbc.ca/services/tax-support/ → no x-frame-options
    • https://fbc.ca/services/business-support/ → no x-frame-options
    • https://fbc.ca/services/financial-and-estate-planning/ → no x-frame-options
    • https://fbc.ca/services/risk-management/ → no x-frame-options
    • https://fbc.ca/services/wealth-management/ → no x-frame-options
    • https://fbc.ca/for/farmers/ → no x-frame-options
    • https://fbc.ca/for/professional-services/ → no x-frame-options
    • https://fbc.ca/for/trades/ → no x-frame-options
    • https://fbc.ca/for/health-wellness/ → no x-frame-options
    • https://fbc.ca/why-fbc/ → 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://fbc.ca/ → no x-content-type-options
    • https://fbc.ca/consultation/ → no x-content-type-options
    • https://fbc.ca/services/tax-support/ → no x-content-type-options
    • https://fbc.ca/services/business-support/ → no x-content-type-options
    • https://fbc.ca/services/financial-and-estate-planning/ → no x-content-type-options
    • https://fbc.ca/services/risk-management/ → no x-content-type-options
    • https://fbc.ca/services/wealth-management/ → no x-content-type-options
    • https://fbc.ca/for/farmers/ → no x-content-type-options
    • https://fbc.ca/for/professional-services/ → no x-content-type-options
    • https://fbc.ca/for/trades/ → no x-content-type-options
    • https://fbc.ca/for/health-wellness/ → no x-content-type-options
    • https://fbc.ca/why-fbc/ → 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://fbc.ca/ → no referrer-policy
    • https://fbc.ca/consultation/ → no referrer-policy
    • https://fbc.ca/services/tax-support/ → no referrer-policy
    • https://fbc.ca/services/business-support/ → no referrer-policy
    • https://fbc.ca/services/financial-and-estate-planning/ → no referrer-policy
    • https://fbc.ca/services/risk-management/ → no referrer-policy
    • https://fbc.ca/services/wealth-management/ → no referrer-policy
    • https://fbc.ca/for/farmers/ → no referrer-policy
    • https://fbc.ca/for/professional-services/ → no referrer-policy
    • https://fbc.ca/for/trades/ → no referrer-policy
    • https://fbc.ca/for/health-wellness/ → no referrer-policy
    • https://fbc.ca/why-fbc/ → 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://fbc.ca/ → no permissions-policy
    • https://fbc.ca/consultation/ → no permissions-policy
    • https://fbc.ca/services/tax-support/ → no permissions-policy
    • https://fbc.ca/services/business-support/ → no permissions-policy
    • https://fbc.ca/services/financial-and-estate-planning/ → no permissions-policy
    • https://fbc.ca/services/risk-management/ → no permissions-policy
    • https://fbc.ca/services/wealth-management/ → no permissions-policy
    • https://fbc.ca/for/farmers/ → no permissions-policy
    • https://fbc.ca/for/professional-services/ → no permissions-policy
    • https://fbc.ca/for/trades/ → no permissions-policy
    • https://fbc.ca/for/health-wellness/ → no permissions-policy
    • https://fbc.ca/why-fbc/ → no permissions-policy
  • FoundMixed contentLow

    1 resource on HTTPS pages are loaded over plain HTTP.

    • https://fbc.ca/blog/5-ways-small-business-owners-can-save-money/ loads image http://clicktotweet.com/img/tweet-graphic-1.png
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (2021 responses)
    • x-powered-by: WP Engine (1059 responses)
  • NoteThird-party scripts

    Scripts run from 4 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.)

    • js.hs-scripts.com (40 script tags)
    • js.hsforms.net (9 script tags)
    • cdn07.icims.com (3 script tags)
    • static.hsappstatic.net (2 script tags)
7 checks passed
  • OKHTTPS

    All 873 crawled pages were served over HTTPS.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKForms over HTTPS

    1 form found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    2 library versions recognised, none with known vulnerabilities.

  • 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.

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.

Earlier scans of fbc.ca

No other scans of this site yet.

Sites scoring near fbc.ca

Their neighbours in the SEO rank table, which orders every scanned site by health score.

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

Own fbc.ca?