Scanned sites / www.projectlandscape.ca / 2026-10-02-2047

www.projectlandscape.ca scan from 10/2/2026, 8:47:18 PM

Scan 2026-10-02-2047

Scanned 10/2/2026, 8:47:18 PM, finished 10/2/2026, 11:46:26 PM. Found on page 1 of brave web search results

Site: https://www.projectlandscape.ca/

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

82/ 100Good

On October 2, 2026 the Site Spider crawled 270 pages and 1079 assets of www.projectlandscape.ca, starting from https://www.projectlandscape.ca/. It scored 82 out of 100, a good result. 8 of 16 checks found something to fix, led by heavy assets (19), sitemap coverage (226), title tags (90); 6 checks passed. Most of the points went to heavy assets (−6), sitemap coverage (−5.6), title tags (−3.7). 2 checks 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: Medium1 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
270
Assets fetched
1079
Status
Completed
Checks with issues
8 of 16
CoverageJob finished, partial coverage

1,349 of 1,350 discovered URLs were fetched, 2,323 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. 120 link destinations on other sites were checked.

  • Title tags90 issues
    90 of 226 pages have title issues. 15 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions38 issues
    38 of 226 pages have meta description issues. 15 noindex or canonicalized pages excluded.
    −1.3 points
  • Headings14 issues
    14 of 226 pages have heading issues. 15 noindex or canonicalized pages excluded.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites9 issues
    9 destinations answered with an error, 29 could not be determined (timeouts, rate limits or refusals), of 120 destinations checked.
    −1.5 points
  • Redirects29 issues
    30 redirecting URLs, 0 of them chained.
    −0.5 points
  • Non-200 responses30 noted
    30 URLs did not return a 2xx response. 29 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.
  • Indexability5 issues
    5 of 230 indexable pages have indexability warnings. 11 pages noindex by design.
    −0.2 points
  • Image alt textOK
    0 of 514 image references have no alt attribute. 2 use an empty alt (decorative), which is fine.
  • Heavy assets19 issues
    19 assets larger than 500 KB among 1079 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage226 issues
    1 sitemap listing 0 URLs: 226 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.6 points
  • Internal link countsOK
    Internal link counts for 241 pages.
  • Thin contentOK
    0 of 226 pages have fewer than 200 words. 15 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1878 sites, median 80%, average 79%

www.projectlandscape.ca scores 82%, higher than 58% of the 1878 scanned sites. See the full ranking.

0541070%: 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%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 13 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 16 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 20 sites67%: 36 sites68%: 30 sites69%: 26 sites70%: 38 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 60 sites76%: 73 sites77%: 72 sites78%: 88 sites79%: 68 sites80%: 91 sites81%: 107 sites82%: 85 sites83%: 86 sites84%: 86 sites85%: 63 sites86%: 73 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 35 sites91%: 36 sites92%: 28 sites93%: 15 sites94%: 13 sites95%: 12 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 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

Your website has good health but needs some improvements. Focus on fixing redirect issues, enhancing titles, improving meta descriptions, addressing heading problems, and fixing sitemap coverage.

  1. 1

    Fix Redirects

    Why: 30 URLs redirect, potentially affecting user experience and SEO.

    How: Update links to direct to the final URL instead of the redirected ones.

    Checks: redirects

  2. 2

    Enhance Title Tags

    Why: 90 pages have title issues, impacting CTR and SEO ranking.

    How: Revise titles to keep under 60 characters and ensure they are descriptive.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 38 pages have issues, limiting search visibility.

    How: Rewrite meta descriptions to be concise and under 155 characters.

    Checks: meta-descriptions

  4. 4

    Add Missing Headings

    Why: 14 pages lack H1 tags, affecting SEO and content hierarchy.

    How: Add appropriate H1 tags to the affected pages to improve structure.

    Checks: headings

  5. 5

    Update Sitemap Coverage

    Why: 226 pages are not listed in the sitemap, reducing indexability.

    How: Generate an updated sitemap including all crawled and indexable pages.

    Checks: sitemap-coverage

  6. 6

    Compress Heavy Assets

    Why: 19 assets are larger than 500 KB, slowing page load times.

    How: Optimize images using compression tools or reconsider their usage on pages.

    Checks: heavy-assets

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 site lacks critical security headers that protect against various attacks, including script injection. It also discloses server software versions, which can aid attackers. Immediate implementation of security headers and version hiding is recommended for better protection.

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

    Missing Content Security PolicyMedium

    Why it matters: No Content Security Policy adds risk of XSS attacks, as scripts can load from any source.

    Fix: Add a 'Content-Security-Policy' header with a restrictive policy, e.g., "default-src 'self'; script-src 'self';".

    Evidence: Content Security Policy

  2. 2

    Missing Referrer PolicyLow

    Why it matters: Absence of referrer policy exposes full URLs to external sites, risking data leakage.

    Fix: Set a 'Referrer-Policy' header, e.g., 'no-referrer'.

    Evidence: Referrer policy

  3. 3

    Server Version DisclosureLow

    Why it matters: Revealing server versions may help attackers exploit known vulnerabilities.

    Fix: Remove or change 'X-Powered-By' header to hide version info, or set it to a generic value.

    Evidence: Software version disclosure

  4. 4

    Missing Permissions PolicyInfo

    Why it matters: Not using a Permissions Policy can allow attackers to misuse browser APIs if they inject scripts.

    Fix: Include a 'Permissions-Policy' header, e.g., 'geolocation=(self)' to restrict API access.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 241 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://www.projectlandscape.ca/ → no content-security-policy
    • https://www.projectlandscape.ca/contact/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no content-security-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no content-security-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no content-security-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no content-security-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no content-security-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → no content-security-policy
  • 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://www.projectlandscape.ca/ → no referrer-policy
    • https://www.projectlandscape.ca/contact/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no referrer-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no referrer-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no referrer-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no referrer-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no referrer-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → 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://www.projectlandscape.ca/ → no permissions-policy
    • https://www.projectlandscape.ca/contact/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/patio-surfaces/ → no permissions-policy
    • https://www.projectlandscape.ca/paver-sealing-refresh-program/ → no permissions-policy
    • https://www.projectlandscape.ca/retaining-walls/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/outdoor-living/garden-walls/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/garden-bed-edging/ → no permissions-policy
    • https://www.projectlandscape.ca/concrete-curbing/ → no permissions-policy
    • https://www.projectlandscape.ca/staircases-stepping-stones/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/landscape-construction/seating/ → no permissions-policy
    • https://www.projectlandscape.ca/residential-services/hardscaping/water-management/ → 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.

    • x-powered-by: PHP/7.4.33 (272 responses)
    • x-powered-by: WP Rocket/3.18.1.3 (1 response)
  • 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.googletagmanager.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 2 paths 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/
    • Disallow: /login/
9 checks passed, 1 not applicable
  • OKHTTPS

    All 241 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 241 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 241 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 241 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

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

Own www.projectlandscape.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 www.projectlandscape.ca. Removal needs no account and no proof of purchase.
www.projectlandscape.ca scan 2026-10-02-2047 | DIY SEO Hub