Scanned sites / plainsfire.ca / 2026-11-01-1511

plainsfire.ca scan from 2026-11-01 15:11:49 UTC DR 0

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

Scan 2026-11-01-1511

Scanned 2026-11-01 15:11:49 UTC, finished 2026-11-01 18:52:15 UTC. Found on page 3 of brave web search results

Site: https://plainsfire.ca/

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

76/ 100Good

On November 1, 2026 the Site Spider crawled 284 pages and 1002 assets of plainsfire.ca, starting from https://plainsfire.ca/. It scored 76 out of 100, a good result. 11 of 33 checks found something to fix, led by heavy assets (50), sitemap coverage (262), meta descriptions (192); 8 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−5.8), meta descriptions (−5.7). 14 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, 4 low and 1 info findings. See the security findings ↓

Pages crawled
284
Assets fetched
1002
Status
Completed
Checks with issues
11 of 33
CoverageJob finished, partial coverage

1,286 of 1,286 discovered URLs were fetched, 269 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 18 link destinations on other sites were checked.

  • Title tags124 issues
    124 of 262 pages have title issues. 8 noindex or canonicalized pages excluded.
    −4.6 points
  • Meta descriptions192 issues
    192 of 262 pages have meta description issues. 8 noindex or canonicalized pages excluded.
    −5.7 points
  • Headings1 issue
    1 of 262 pages have heading issues. 8 noindex or canonicalized pages excluded.
  • Broken links9 issues
    46 internal links point at 9 broken URLs.
    −0.7 points
  • Links to other sites1 issue
    1 destination answered with an error, 8 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
    −0.1 points
  • Redirects5 issues
    6 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses9 issues
    16 URLs did not return a 2xx response. 14 of them are pages, 9 with an error status; the rest are assets or redirects.
    −0.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 270 indexable pages have indexability warnings.
  • Image alt text92 issues
    92 of 2458 image references have no alt attribute. 193 use an empty alt (decorative), which is fine.
    −0.2 points
  • Heavy assets50 issues
    50 assets larger than 500 KB among 1002 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage262 issues
    1 sitemap listing 0 URLs: 262 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.8 points
  • Internal link counts49 noted
    Internal link counts for 270 pages; 49 worth a look.
  • Thin contentOK
    0 of 262 pages have fewer than 200 words. 8 noindex or canonicalized pages excluded.
  • Duplicate content9 issues
    1 group of pages with identical HTML.
    −0.3 points
  • URL format20 noted
    20 of 284 page URLs are harder to read, share or cache than they need to be.
  • Canonicals8 noted
    8 of 270 pages have a canonical worth checking.
  • Robots directives270 noted
    270 pages carry a robots directive; 0 carry none.
  • Anchor text216 noted
    216 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure48 noted
    48 of 262 pages could use the title, heading and snippet space better. 8 noindex or canonicalized pages excluded.
  • Image weight and alt length32 noted
    32 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies3 noted
    3 URLs answered in a way worth looking at.
  • HTML and head validation197 noted
    197 of 270 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data200 noted
    270 of 262 indexable pages carry structured data: Organization (270), WebSite (270), ImageObject (212), Product (200), ItemPage (200). 200 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 262 pages with enough text to compare.
  • 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 positions1 noted
    1 of 262 linked pages are linked only from the template, never from another page's content.
  • Pagination8 noted
    13 pages in pagination sequences; 8 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 1286 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 270 pages; 194 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.
  • Spelling39 noted
    39 words an English dictionary does not know, on 70 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2549 sites, median 80%, average 78%

plainsfire.ca scores 76%, higher than 34% of the 2549 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%: 76 sites74%: 76 sites75%: 77 sites76%: 92 sites77%: 102 sites78%: 115 sites79%: 102 sites80%: 119 sites81%: 113 sites82%: 115 sites83%: 115 sites84%: 118 sites85%: 95 sites86%: 79 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 sites76% 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 several areas needing attention, especially broken links and missing sitemap entries. Addressing these will improve user experience and SEO. Here are the priorities:

  1. 1

    Fix Broken Internal Links

    Why: 46 links lead to broken URLs, causing user frustration.

    How: Identify broken links and either update or remove them. Focus on the specific URLs provided in the report.

    Evidence: https://plainsfire.ca/product-category/fire-detection-alarm… answers 503, and 12 pages link to it with anchor text such as "400 Series (11)".

    12 pages affected

    Depends on: If the destination was deleted on purpose, remove the links rather than redirecting to an unrelated page.

    Checks: broken-links

  2. 2

    Update Sitemap Coverage

    Why: Your sitemap currently lists 0 URLs while there are 262 pages crawled that should be indexed.

    How: Generate a new sitemap that includes all 262 pages, and submit it to Google Search Console.

    Evidence: 262 URLs: not in sitemap.

    262 pages affected

    Checks: sitemap-coverage

  3. 3

    Correct Title Tag Issues

    Why: 124 pages have title problems, impacting SEO.

    How: Review each affected title for uniqueness and appropriate length; optimize them accordingly.

    Checks: titles

  4. 4

    Add Meta Descriptions

    Why: 192 pages lack meta descriptions, which affects click-through rates.

    How: Write unique meta descriptions for these pages based on their content to improve visibility.

    Evidence: 50 pages have no meta description at all.

    50 pages affected

    Checks: meta-descriptions

  5. 5

    Optimize Heavy Assets

    Why: 50 assets exceed optimal size, slowing load times.

    How: Compress images and scripts to reduce load time without sacrificing quality; consider offloading large files.

    Evidence: 467 KB of script, loaded by 200 pages, so every visitor to any of them downloads it.

    200 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

    Address Duplicate Content

    Why: Identical HTML in multiple pages can harm SEO rankings.

    How: Review the duplicate pages and implement canonical tags or merge content where applicable.

    Checks: duplicate-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

Your website has several security headers missing, which could expose it to various risks such as clickjacking and interception of requests. Implementing the recommended headers and fixing the mixed-content issue will enhance security and protect user data.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on initial requests if they do not use HTTPS.

    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: Lack of CSP allows unrestricted loading of scripts, potentially leading to cross-site scripting attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header allows clickjacking vulnerabilities, enabling potentially malicious framing of pages.

    Fix: Implement 'X-Frame-Options: DENY' or use a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may execute files as scripts based on their contents, leading to risks.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Lack of a referrer policy exposes full URLs, which may leak sensitive information.

    Fix: Introduce the header 'Referrer-Policy: no-referrer'.

    Evidence: Referrer policy

  6. 6

    Server Information DisclosureLow

    Why it matters: Exposing server versions may help attackers identify and exploit known vulnerabilities.

    Fix: Remove or modify headers that reveal these details, especially 'Server' and 'X-Powered-By'.

    Evidence: Software version disclosure

  7. 7

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on secure HTTPS pages can expose user data.

    Fix: Change URL to 'https://development.mircom.com/wp-content/uploads/products/c-ul-us_listed.png'.

    Evidence: Mixed content

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: This header restricts browser features that could be leveraged by injected scripts.

    Fix: Add the header 'Permissions-Policy: camera=(), microphone=(), 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://plainsfire.ca/ → no strict-transport-security
    • https://plainsfire.ca/about/ → no strict-transport-security
    • https://plainsfire.ca/products/ → no strict-transport-security
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no strict-transport-security
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no strict-transport-security
    • https://plainsfire.ca/product-category/security-access-control/ → no strict-transport-security
    • https://plainsfire.ca/product-category/emergency-lighting/ → no strict-transport-security
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no strict-transport-security
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no strict-transport-security
    • https://plainsfire.ca/emergency-lighting-inspection/ → no strict-transport-security
    • https://plainsfire.ca/sprinkler-system-inspection/ → no strict-transport-security
    • https://plainsfire.ca/electrical-service-regina/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 270 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://plainsfire.ca/ → no content-security-policy
    • https://plainsfire.ca/about/ → no content-security-policy
    • https://plainsfire.ca/products/ → no content-security-policy
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no content-security-policy
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no content-security-policy
    • https://plainsfire.ca/product-category/security-access-control/ → no content-security-policy
    • https://plainsfire.ca/product-category/emergency-lighting/ → no content-security-policy
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no content-security-policy
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no content-security-policy
    • https://plainsfire.ca/emergency-lighting-inspection/ → no content-security-policy
    • https://plainsfire.ca/sprinkler-system-inspection/ → no content-security-policy
    • https://plainsfire.ca/electrical-service-regina/ → 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://plainsfire.ca/ → no x-frame-options
    • https://plainsfire.ca/about/ → no x-frame-options
    • https://plainsfire.ca/products/ → no x-frame-options
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no x-frame-options
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no x-frame-options
    • https://plainsfire.ca/product-category/security-access-control/ → no x-frame-options
    • https://plainsfire.ca/product-category/emergency-lighting/ → no x-frame-options
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no x-frame-options
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no x-frame-options
    • https://plainsfire.ca/emergency-lighting-inspection/ → no x-frame-options
    • https://plainsfire.ca/sprinkler-system-inspection/ → no x-frame-options
    • https://plainsfire.ca/electrical-service-regina/ → 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://plainsfire.ca/ → no x-content-type-options
    • https://plainsfire.ca/about/ → no x-content-type-options
    • https://plainsfire.ca/products/ → no x-content-type-options
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no x-content-type-options
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no x-content-type-options
    • https://plainsfire.ca/product-category/security-access-control/ → no x-content-type-options
    • https://plainsfire.ca/product-category/emergency-lighting/ → no x-content-type-options
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no x-content-type-options
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no x-content-type-options
    • https://plainsfire.ca/emergency-lighting-inspection/ → no x-content-type-options
    • https://plainsfire.ca/sprinkler-system-inspection/ → no x-content-type-options
    • https://plainsfire.ca/electrical-service-regina/ → 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://plainsfire.ca/ → no referrer-policy
    • https://plainsfire.ca/about/ → no referrer-policy
    • https://plainsfire.ca/products/ → no referrer-policy
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no referrer-policy
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no referrer-policy
    • https://plainsfire.ca/product-category/security-access-control/ → no referrer-policy
    • https://plainsfire.ca/product-category/emergency-lighting/ → no referrer-policy
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no referrer-policy
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no referrer-policy
    • https://plainsfire.ca/emergency-lighting-inspection/ → no referrer-policy
    • https://plainsfire.ca/sprinkler-system-inspection/ → no referrer-policy
    • https://plainsfire.ca/electrical-service-regina/ → 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://plainsfire.ca/ → no permissions-policy
    • https://plainsfire.ca/about/ → no permissions-policy
    • https://plainsfire.ca/products/ → no permissions-policy
    • https://plainsfire.ca/product-category/fire-detection-alarm/ → no permissions-policy
    • https://plainsfire.ca/product-category/communication-voice-entry/ → no permissions-policy
    • https://plainsfire.ca/product-category/security-access-control/ → no permissions-policy
    • https://plainsfire.ca/product-category/emergency-lighting/ → no permissions-policy
    • https://plainsfire.ca/fire-alarm-life-safety-inspection/ → no permissions-policy
    • https://plainsfire.ca/fire-extinguisher-inspection/ → no permissions-policy
    • https://plainsfire.ca/emergency-lighting-inspection/ → no permissions-policy
    • https://plainsfire.ca/sprinkler-system-inspection/ → no permissions-policy
    • https://plainsfire.ca/electrical-service-regina/ → 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 (1285 responses)
    • x-powered-by: PHP/8.2.35 (278 responses)
    • server: nginx (1 response)
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://plainsfire.ca/product/el-7030a-universal-1-5w-led-emergency-r… loads image http://development.mircom.com/wp-content/uploads/products/c-ul-us_listed.png
    • https://plainsfire.ca/product/el-7030a-universal-1-5w-led-emergency-r… loads image http://development.mircom.com/wp-content/uploads/products/c-ul-us_listed.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.)

    • www.google.com (33 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/
5 checks passed, 1 not applicable
  • OKHTTPS

    All 270 crawled pages were served over HTTPS.

  • OKForms over HTTPS

    81 forms 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.

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

Own plainsfire.ca?