Scanned sites / waggytails.ca / 2026-11-01-1346

waggytails.ca scan from 2026-11-01 13:46:22 UTC DR 4

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

Scan 2026-11-01-1346

Scanned 2026-11-01 13:46:22 UTC, finished 2026-11-01 14:29:47 UTC. Found on page 5 of brave web search results

Site: https://waggytails.ca/

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

74/ 100Needs work

On November 1, 2026 the Site Spider crawled 11 pages and 190 assets of waggytails.ca, starting from https://waggytails.ca/. It scored 74 out of 100, a result that needs work. 6 of 33 checks found something to fix, led by title tags (8), heavy assets (11), meta descriptions (6); 19 checks passed. Most of the points went to title tags (−10), meta descriptions (−6), heavy assets (−6). 8 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: Medium3 medium and 4 low findings. See the security findings ↓

Pages crawled
11
Assets fetched
190
Status
Completed
Checks with issues
6 of 33
CoverageComplete crawl

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

  • Title tags8 issues
    8 of 8 pages have title issues.
    −10 points
  • Meta descriptions6 issues
    6 of 8 pages have meta description issues.
    −6 points
  • HeadingsOK
    0 of 8 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites21 noted
    0 destinations answered with an error, 4 could not be determined (timeouts, rate limits or refusals), of 4 destinations checked.
  • Redirects1 issue
    4 redirecting URLs, 0 of them chained.
    −0.5 points
  • Non-200 responses5 noted
    5 URLs did not return a 2xx response. 3 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 8 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 7 image references have no alt attribute.
  • Heavy assets11 issues
    11 assets larger than 500 KB among 190 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage2 issues
    3 sitemaps listing 10 URLs: 0 crawled pages missing, 2 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −1.5 points
  • Internal link countsOK
    Internal link counts for 8 pages; none is a dead end or buried.
  • Thin content2 issues
    2 of 8 pages have fewer than 200 words.
    −2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 11 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 8 pages have a canonical worth checking.
  • Robots directives8 noted
    8 pages carry a robots directive; 0 carry none.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 8 pages could use the title, heading and snippet space better.
  • Image weight and alt length4 noted
    4 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationOK
    All 8 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    8 of 8 indexable pages carry structured data: BreadcrumbList (8), ListItem (8), WebSite (8), Organization (8), WebPage (8). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 8 pages with enough text to compare.
  • Soft 404sOK
    None of 8 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 positions1 noted
    1 of 8 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 14 response headers recorded across 201 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 8 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.
  • Spelling1 noted
    1 word an English dictionary does not know, on 1 page. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2488 sites, median 80%, average 78%

waggytails.ca scores 74%, higher than 28% of the 2488 scanned sites. See the full ranking.

0591180%: 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%: 1 site40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 5 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 28 sites64%: 21 sites65%: 31 sites66%: 36 sites67%: 36 sites68%: 36 sites69%: 49 sites70%: 48 sites71%: 73 sites72%: 72 sites73%: 73 sites74%: 72 sites75%: 75 sites76%: 88 sites77%: 99 sites78%: 112 sites79%: 97 sites80%: 118 sites81%: 111 sites82%: 112 sites83%: 112 sites84%: 115 sites85%: 94 sites86%: 77 sites87%: 84 sites88%: 60 sites89%: 70 sites90%: 45 sites91%: 52 sites92%: 40 sites93%: 27 sites94%: 21 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites74% 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

Several key issues need fixing, including redirects, title tags, and meta descriptions. Addressing these will improve your site's SEO performance significantly. Here’s a prioritized fix plan.

  1. 1

    Fix Redirects

    Why: Redirects can confuse search engines and users, impacting usability.

    How: Update the URLs to remove unnecessary redirects. Ensure all pages resolve directly to their final URLs instead of redirecting.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Pages returning non-200 status codes may harm user experience and SEO.

    How: Ensure the listed pages return a 200 status code by either correcting links or removing dead assets.

    Checks: status-codes

  3. 3

    Shorten Title Tags

    Why: Long title tags can get cut off in search results, reducing click-through rates.

    How: Revise title tags to be under 60 characters while retaining relevance to the content.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Long meta descriptions lose visibility in search results, affecting click-through rates.

    How: Shorten descriptions to under 160 characters, focusing on enticing keywords.

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: Large assets can slow page load times, impacting user experience.

    How: Shrink or replace heavy assets identified in the crawl, optimizing images and scripts.

    Checks: heavy-assets

  6. 6

    Enhance Thin Content

    Why: Thin content may affect search rankings; enhancing it can improve SEO.

    How: Expand the content on the thin pages to over 200 words, adding valuable information.

    Checks: thin-content

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 waggytails.ca lacks several important security headers that protect against various attacks, including interception, clickjacking, and content type issues. Implementing these headers is crucial for improving the site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the URL may be intercepted on their first request.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your HTTP headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows unrestricted loading of scripts, styles, and frames, increasing XSS risks.

    Fix: Add 'Content-Security-Policy: default-src 'self';' to your HTTP headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site is vulnerable to clickjacking attacks.

    Fix: Add 'X-Frame-Options: DENY' to your HTTP headers.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, users may be at risk of content-type confusion attacks.

    Fix: Add 'X-Content-Type-Options: nosniff' to your HTTP headers.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Without this header, sensitive referral information can be leaked to third-party sites.

    Fix: Add 'Referrer-Policy: no-referrer' to your HTTP headers.

    Evidence: Referrer policy

  6. 6

    Server Banner Reveals Version InformationLow

    Why it matters: Disclosing server version info allows attackers to target known vulnerabilities.

    Fix: Configure your server to hide version information; for Apache, use 'ServerTokens Prod' and 'ServerSignature Off'.

    Evidence: Software version disclosure

  7. 7

    Mixed Content IssueLow

    Why it matters: Loading HTTP resources over HTTPS can lead to security vulnerabilities.

    Fix: Ensure all resources are loaded over HTTPS to secure the content.

    Evidence: Mixed content

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://waggytails.ca/ → no strict-transport-security
    • https://waggytails.ca/dog-daycare/ → no strict-transport-security
    • https://waggytails.ca/private-enclosure-dog-boarding/ → no strict-transport-security
    • https://waggytails.ca/grooming/ → no strict-transport-security
    • https://waggytails.ca/training/ → no strict-transport-security
    • https://waggytails.ca/treats-and-eats/ → no strict-transport-security
    • https://waggytails.ca/about-us/ → no strict-transport-security
    • https://waggytails.ca/registration/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 8 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://waggytails.ca/ → no content-security-policy
    • https://waggytails.ca/dog-daycare/ → no content-security-policy
    • https://waggytails.ca/private-enclosure-dog-boarding/ → no content-security-policy
    • https://waggytails.ca/grooming/ → no content-security-policy
    • https://waggytails.ca/training/ → no content-security-policy
    • https://waggytails.ca/treats-and-eats/ → no content-security-policy
    • https://waggytails.ca/about-us/ → no content-security-policy
    • https://waggytails.ca/registration/ → 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://waggytails.ca/ → no x-frame-options
    • https://waggytails.ca/dog-daycare/ → no x-frame-options
    • https://waggytails.ca/private-enclosure-dog-boarding/ → no x-frame-options
    • https://waggytails.ca/grooming/ → no x-frame-options
    • https://waggytails.ca/training/ → no x-frame-options
    • https://waggytails.ca/treats-and-eats/ → no x-frame-options
    • https://waggytails.ca/about-us/ → no x-frame-options
    • https://waggytails.ca/registration/ → 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://waggytails.ca/ → no x-content-type-options
    • https://waggytails.ca/dog-daycare/ → no x-content-type-options
    • https://waggytails.ca/private-enclosure-dog-boarding/ → no x-content-type-options
    • https://waggytails.ca/grooming/ → no x-content-type-options
    • https://waggytails.ca/training/ → no x-content-type-options
    • https://waggytails.ca/treats-and-eats/ → no x-content-type-options
    • https://waggytails.ca/about-us/ → no x-content-type-options
    • https://waggytails.ca/registration/ → 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://waggytails.ca/ → no referrer-policy
    • https://waggytails.ca/dog-daycare/ → no referrer-policy
    • https://waggytails.ca/private-enclosure-dog-boarding/ → no referrer-policy
    • https://waggytails.ca/grooming/ → no referrer-policy
    • https://waggytails.ca/training/ → no referrer-policy
    • https://waggytails.ca/treats-and-eats/ → no referrer-policy
    • https://waggytails.ca/about-us/ → no referrer-policy
    • https://waggytails.ca/registration/ → no referrer-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 (201 responses)
    • x-powered-by: PHP/8.2.35 (17 responses)
  • FoundMixed contentLow

    1 resource on HTTPS pages are loaded over plain HTTP.

    • https://waggytails.ca/treats-and-eats/ loads image http://u40.efb.mytemp.website/wp-content/uploads/2024/10/blob-5b05e36.png
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • img1.wsimg.com (8 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 8 crawled pages were served over HTTPS.

  • OKPermissions policy

    permissions-policy is set on all 8 HTML pages.

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

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

Own waggytails.ca?