Scanned sites / fatherandsonyyc.ca / 2026-11-01-2221

fatherandsonyyc.ca scan from 2026-11-01 22:21:56 UTC DR 3

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

Scan 2026-11-01-2221

Scanned 2026-11-01 22:21:56 UTC, finished 2026-11-01 23:14:31 UTC. Found on page 2 of brave web search results

Site: https://fatherandsonyyc.ca/

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

63/ 100Needs work

On November 1, 2026 the Site Spider crawled 72 pages and 197 assets of fatherandsonyyc.ca, starting from https://fatherandsonyyc.ca/. It scored 63 out of 100, a result that needs work. 13 of 33 checks found something to fix, led by meta descriptions (57), heavy assets (24), title tags (33); 8 checks passed. Most of the points went to meta descriptions (−8), heavy assets (−6), title tags (−5.8). 12 checks found something the score does not count, listed as noted. 4 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: Medium5 medium, 2 low and 3 info findings. See the security findings ↓

Pages crawled
72
Assets fetched
197
Status
Completed
Checks with issues
13 of 33
CoverageComplete crawl

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

  • Title tags33 issues
    33 of 57 pages have title issues.
    −5.8 points
  • Meta descriptions57 issues
    57 of 57 pages have meta description issues.
    −8 points
  • Headings1 issue
    1 of 57 pages have heading issues.
    −0.1 points
  • Broken links12 issues
    50 internal links point at 12 broken URLs.
    −4.2 points
  • Links to other sites1 issue
    1 destination answered with an error, 31 could not be determined (timeouts, rate limits or refusals), of 41 destinations checked.
    −0.4 points
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses12 issues
    18 URLs did not return a 2xx response. 15 of them are pages, 12 with an error status; the rest are assets or redirects.
    −2.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability16 issues
    16 of 57 indexable pages have indexability warnings.
    −2.8 points
  • Image alt text56 issues
    56 of 655 image references have no alt attribute. 11 use an empty alt (decorative), which is fine.
    −0.5 points
  • Heavy assets24 issues
    24 assets larger than 500 KB among 197 fetched assets.
    −6 points
  • Orphan pages14 issues
    14 pages have no internal links pointing at them.
    −1 points
  • Sitemap coverage29 issues
    8 sitemaps listing 66 URLs: 3 crawled pages missing, 12 listed URLs broken or redirecting, 14 reachable only via the sitemap.
    −3.1 points
  • Internal link counts4 noted
    Internal link counts for 57 pages; 4 worth a look.
  • Thin content22 issues
    22 of 57 pages have fewer than 200 words.
    −3.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format6 noted
    6 of 72 page URLs are harder to read, share or cache than they need to be.
  • Canonicals16 noted
    16 of 57 pages have a canonical worth checking.
  • Robots directives56 noted
    56 pages carry a robots directive; 1 carries none.
  • Anchor text39 noted
    39 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure40 noted
    40 of 57 pages could use the title, heading and snippet space better.
  • Image weight and alt length50 noted
    48 images over 100 KB; 2 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.
  • HTML and head validation1 noted
    1 of 57 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    56 of 57 indexable pages carry structured data: WebPage (56), WPHeader (56), WPFooter (56), BreadcrumbList (33), ListItem (33). 0 pages with errors a rich result would fail on.
  • Near duplicates4 noted
    4 pages in 2 groups read almost the same as another page (95% alike or more).
  • Soft 404s1 noted
    1 page answer 200 but say they are not there.
  • 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 positionsOK
    0 of 43 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    16 pages in pagination sequences; 0 with problems.
  • Headers and cookiesOK
    1 cookie set by the site; 10 response headers recorded across 269 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 57 pages; 0 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling12 noted
    12 words an English dictionary does not know, on 23 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2544 sites, median 80%, average 78%

fatherandsonyyc.ca scores 63%, higher than 7% of the 2544 scanned sites. See the full ranking.

0601190%: 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%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 37 sites67%: 39 sites68%: 38 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 72 sites73%: 74 sites74%: 75 sites75%: 77 sites76%: 92 sites77%: 101 sites78%: 115 sites79%: 102 sites80%: 119 sites81%: 113 sites82%: 115 sites83%: 115 sites84%: 118 sites85%: 95 sites86%: 78 sites87%: 85 sites88%: 67 sites89%: 71 sites90%: 46 sites91%: 56 sites92%: 39 sites93%: 28 sites94%: 20 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites63% 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 has multiple technical issues, including broken links, title and meta description problems, and heavy asset load. Addressing these will improve user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: Broken links hinder user experience and SEO.

    How: Identify and update or remove the 50 broken URLs.

    Checks: broken-links

  2. 2

    Write Meta Descriptions

    Why: Meta descriptions are crucial for click-through rates in search results.

    How: Create engaging meta descriptions for all missing ones on 57 pages.

    Checks: meta-descriptions

  3. 3

    Optimize Title Tags

    Why: Improving title tags enhances SEO and user clarity.

    How: Review and edit the 33 pages with title issues, ensuring relevance and proper length.

    Checks: titles

  4. 4

    Validate Indexability

    Why: Ensuring pages are indexed properly is vital for visibility.

    How: Review the 16 pages with indexability warnings and refine meta tags and attributes as needed.

    Checks: indexability

  5. 5

    Reduce Heavy Assets

    Why: Large assets can slow down the site, affecting both performance and SEO.

    How: Optimize the 24 large assets, reducing their sizes where possible.

    Checks: heavy-assets

  6. 6

    Fix Sitemap Issues

    Why: A functional sitemap is important for search engines to crawl your site effectively.

    How: Ensure all URLs listed in the sitemap return valid responses and fix the 8 missing URLs.

    Checks: sitemap-coverage

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 security issues, primarily related to missing HTTP response headers and outdated libraries. Key recommendations include implementing HTTP Strict Transport Security, a Content Security Policy, and updating vulnerable JavaScript libraries to improve protection against various attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, HTTP connections can be intercepted when users type the URL without 'https://'.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Absence of Content Security Policy (CSP)Medium

    Why it matters: Lack of a CSP allows potentially harmful scripts and resources to be loaded from any origin, increasing risk of XSS attacks.

    Fix: Implement a CSP header, e.g., Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: The absence of X-Frame-Options allows the site to be embedded in frames, exposing it to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

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

    Fix: Update to jQuery version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Outdated Bootstrap LibraryMedium

    Why it matters: Using Bootstrap 4.0.0 introduces vulnerabilities that can lead to XSS attacks.

    Fix: Upgrade to Bootstrap version 4.3.1 or later.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers can misinterpret file types, leading to potential security risks.

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

    Evidence: MIME sniffing protection

  7. 7

    Lack of Referrer PolicyLow

    Why it matters: No referrer policy means sensitive URL information could be sent to other websites when users click links.

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

    Evidence: Referrer policy

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy, the site leaves potentially exploitable features available to scripts that could be injected.

    Fix: Add the header: Permissions-Policy: accelerometer=(), camera=(), microphone=(), geolocation=();

    Evidence: Permissions policy

  9. 9

    Third-Party Scripts without Subresource IntegrityInfo

    Why it matters: Scripts from external domains pose risks if those domains are compromised, as there is no integrity validation.

    Fix: Consider adding a Content-Security-Policy that specifies trusted sources for scripts.

    Evidence: Third-party scripts

  10. 10

    Sensitive Path Listed in robots.txtInfo

    Why it matters: Robots.txt exposes a sensitive directory, making it easier for attackers to probe the site.

    Fix: Implement actual access controls on sensitive directories instead of relying on robots.txt for security.

    Evidence: Sensitive paths in robots.txt

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://fatherandsonyyc.ca/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/landscaping/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/decks/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/fences/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/general-contracting/ → no strict-transport-security
    • https://fatherandsonyyc.ca/services/concrete/ → no strict-transport-security
    • https://fatherandsonyyc.ca/gallery/ → no strict-transport-security
    • https://fatherandsonyyc.ca/blog/ → no strict-transport-security
    • https://fatherandsonyyc.ca/about-us/ → no strict-transport-security
    • https://fatherandsonyyc.ca/contact-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 57 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://fatherandsonyyc.ca/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/landscaping/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/decks/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/fences/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/general-contracting/ → no content-security-policy
    • https://fatherandsonyyc.ca/services/concrete/ → no content-security-policy
    • https://fatherandsonyyc.ca/gallery/ → no content-security-policy
    • https://fatherandsonyyc.ca/blog/ → no content-security-policy
    • https://fatherandsonyyc.ca/about-us/ → no content-security-policy
    • https://fatherandsonyyc.ca/contact-us/ → 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://fatherandsonyyc.ca/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/landscaping/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/decks/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/fences/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/general-contracting/ → no x-frame-options
    • https://fatherandsonyyc.ca/services/concrete/ → no x-frame-options
    • https://fatherandsonyyc.ca/gallery/ → no x-frame-options
    • https://fatherandsonyyc.ca/blog/ → no x-frame-options
    • https://fatherandsonyyc.ca/about-us/ → no x-frame-options
    • https://fatherandsonyyc.ca/contact-us/ → 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://fatherandsonyyc.ca/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/landscaping/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/decks/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/fences/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/general-contracting/ → no x-content-type-options
    • https://fatherandsonyyc.ca/services/concrete/ → no x-content-type-options
    • https://fatherandsonyyc.ca/gallery/ → no x-content-type-options
    • https://fatherandsonyyc.ca/blog/ → no x-content-type-options
    • https://fatherandsonyyc.ca/about-us/ → no x-content-type-options
    • https://fatherandsonyyc.ca/contact-us/ → 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://fatherandsonyyc.ca/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/landscaping/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/decks/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/fences/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/general-contracting/ → no referrer-policy
    • https://fatherandsonyyc.ca/services/concrete/ → no referrer-policy
    • https://fatherandsonyyc.ca/gallery/ → no referrer-policy
    • https://fatherandsonyyc.ca/blog/ → no referrer-policy
    • https://fatherandsonyyc.ca/about-us/ → no referrer-policy
    • https://fatherandsonyyc.ca/contact-us/ → 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://fatherandsonyyc.ca/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/landscaping/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/landscape-cleanup/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/decks/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/fences/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/general-contracting/ → no permissions-policy
    • https://fatherandsonyyc.ca/services/concrete/ → no permissions-policy
    • https://fatherandsonyyc.ca/gallery/ → no permissions-policy
    • https://fatherandsonyyc.ca/blog/ → no permissions-policy
    • https://fatherandsonyyc.ca/about-us/ → no permissions-policy
    • https://fatherandsonyyc.ca/contact-us/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 1.9.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://fatherandsonyyc.ca/wp-content/themes/landscaping/assets/js/main.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
    • Bootstrap 4.0.0 in https://fatherandsonyyc.ca/wp-content/themes/landscaping/assets/js/main.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
  • NoteThird-party scripts

    Scripts run from 3 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)
    • link.msgsndr.com (2 script tags)
    • cdn.trustindex.io (1 script tag)
  • 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/
7 checks passed
  • OKHTTPS

    All 57 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

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

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

Own fatherandsonyyc.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 fatherandsonyyc.ca. Removal needs no account and no proof of purchase.