Scanned sites / lawnco.net

SEO report for lawnco.net

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

Latest scan

Scanned 10/1/2026, 4:31:05 AM, finished 10/1/2026, 5:59:00 AM. Found on page 3 of brave web search results

Site: https://lawnco.net/

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

79/ 100Good

On October 1, 2026 the Site Spider crawled 36 pages and 380 assets of lawnco.net, starting from https://lawnco.net/. It scored 79 out of 100, a good result. 7 of 16 checks found something to fix, led by heavy assets (12), meta descriptions (13), title tags (8); 7 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−5.8), title tags (−4.4). 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: Medium3 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
36
Assets fetched
380
Status
Completed
Checks with issues
7 of 16
CoverageComplete crawl

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

  • Title tags8 issues
    8 of 18 pages have title issues.
    −4.4 points
  • Meta descriptions13 issues
    13 of 18 pages have meta description issues.
    −5.8 points
  • HeadingsOK
    0 of 18 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 13 destinations checked.
    −0.4 points
  • Redirects16 issues
    20 redirecting URLs, 0 of them chained.
    −3.6 points
  • Non-200 responses20 noted
    20 URLs did not return a 2xx response. 18 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 18 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 108 image references have no alt attribute.
  • Heavy assets12 issues
    12 assets larger than 500 KB among 380 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage4 issues
    4 sitemaps listing 20 URLs: 0 crawled pages missing, 2 listed URLs broken or redirecting, 2 reachable only via the sitemap.
    −1.3 points
  • Internal link countsOK
    Internal link counts for 18 pages.
  • Thin contentOK
    0 of 18 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1754 sites, median 80%, average 79%

lawnco.net scores 79%, higher than 44% of the 1754 scanned sites. See the full ranking.

0511020%: 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%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 12 sites65%: 20 sites66%: 19 sites67%: 34 sites68%: 27 sites69%: 25 sites70%: 39 sites71%: 37 sites72%: 49 sites73%: 49 sites74%: 48 sites75%: 57 sites76%: 71 sites77%: 63 sites78%: 83 sites79%: 60 sites80%: 85 sites81%: 102 sites82%: 82 sites83%: 82 sites84%: 77 sites85%: 59 sites86%: 64 sites87%: 55 sites88%: 60 sites89%: 53 sites90%: 32 sites91%: 34 sites92%: 24 sites93%: 14 sites94%: 12 sites95%: 10 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites79% 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

The site has a good health score but requires fixes to redirect issues, title and meta description improvements, heavy asset reductions, and accessibility of orphan pages. Prioritize these actions to enhance site performance and SEO.

  1. 1

    Fix Redirects

    Why: 20 URLs redirect, which can slow down user experience and SEO.

    How: Identify and update the source URLs to point directly to the final destination without a redirect.

    Checks: redirects

  2. 2

    Improve Title Tags

    Why: 8 pages have short title tags, which affect search visibility.

    How: Revise the titles to be more descriptive and ensure they exceed 30 characters for better engagement.

    Checks: titles

  3. 3

    Address Missing Meta Descriptions

    Why: A missing meta description negatively impacts click-through rates.

    How: Create and add a relevant meta description for the blog page, ensuring it's concise and under 160 characters.

    Checks: meta-descriptions

  4. 4

    Optimize Heavy Assets

    Why: 12 assets over 500 KB can slow down loading times.

    How: Compress or optimize the large asset files, focusing on those used across multiple pages.

    Checks: heavy-assets

  5. 5

    Link Orphan Page

    Why: The blog page lacks internal links, making it hard for users and search engines to find it.

    How: Add links to the blog from other relevant pages to improve its visibility and accessibility.

    Checks: orphan-pages

  6. 6

    Fix Sitemap Issues

    Why: 2 URLs in the sitemap are broken or redirecting, affecting site indexability.

    How: Ensure all URLs listed in the sitemap are valid and reachable without redirects, and update the sitemap accordingly.

    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 lawnco.net lacks several important security headers, exposing it to risks such as traffic interception and clickjacking. Implementing recommended headers can significantly enhance security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request if they omit 'https://'.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows scripts, styles, and frames to load from any source, increasing risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

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

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this, browsers may misinterpret files as executable scripts.

    Fix: Set 'X-Content-Type-Options: nosniff' in your response headers.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Not setting a referrer policy may expose user navigation details.

    Fix: Add 'Referrer-Policy: no-referrer' in your response headers.

    Evidence: Referrer policy

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: Lack of permissions policy may allow unauthorized use of sensitive features like geolocation.

    Fix: Implement 'Permissions-Policy: interest-cohort=()'

    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://lawnco.net/ → no strict-transport-security
    • https://lawnco.net/about-us → no strict-transport-security
    • https://lawnco.net/residential-landscaping-design-construction → no strict-transport-security
    • https://lawnco.net/plant-health-lawn-care → no strict-transport-security
    • https://lawnco.net/lawn-maintenance → no strict-transport-security
    • https://lawnco.net/tree-care-service → no strict-transport-security
    • https://lawnco.net/irrigation-management → no strict-transport-security
    • https://lawnco.net/commercial-landscaping-maintenance → no strict-transport-security
    • https://lawnco.net/subdivision-landscape-management → no strict-transport-security
    • https://lawnco.net/commercial-industrial-landscape-management → no strict-transport-security
    • https://lawnco.net/ice-snow-management → no strict-transport-security
    • https://lawnco.net/holiday-lighting → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 18 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://lawnco.net/ → no content-security-policy
    • https://lawnco.net/about-us → no content-security-policy
    • https://lawnco.net/residential-landscaping-design-construction → no content-security-policy
    • https://lawnco.net/plant-health-lawn-care → no content-security-policy
    • https://lawnco.net/lawn-maintenance → no content-security-policy
    • https://lawnco.net/tree-care-service → no content-security-policy
    • https://lawnco.net/irrigation-management → no content-security-policy
    • https://lawnco.net/commercial-landscaping-maintenance → no content-security-policy
    • https://lawnco.net/subdivision-landscape-management → no content-security-policy
    • https://lawnco.net/commercial-industrial-landscape-management → no content-security-policy
    • https://lawnco.net/ice-snow-management → no content-security-policy
    • https://lawnco.net/holiday-lighting → 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://lawnco.net/ → no x-frame-options
    • https://lawnco.net/about-us → no x-frame-options
    • https://lawnco.net/residential-landscaping-design-construction → no x-frame-options
    • https://lawnco.net/plant-health-lawn-care → no x-frame-options
    • https://lawnco.net/lawn-maintenance → no x-frame-options
    • https://lawnco.net/tree-care-service → no x-frame-options
    • https://lawnco.net/irrigation-management → no x-frame-options
    • https://lawnco.net/commercial-landscaping-maintenance → no x-frame-options
    • https://lawnco.net/subdivision-landscape-management → no x-frame-options
    • https://lawnco.net/commercial-industrial-landscape-management → no x-frame-options
    • https://lawnco.net/ice-snow-management → no x-frame-options
    • https://lawnco.net/holiday-lighting → 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://lawnco.net/ → no x-content-type-options
    • https://lawnco.net/about-us → no x-content-type-options
    • https://lawnco.net/residential-landscaping-design-construction → no x-content-type-options
    • https://lawnco.net/plant-health-lawn-care → no x-content-type-options
    • https://lawnco.net/lawn-maintenance → no x-content-type-options
    • https://lawnco.net/tree-care-service → no x-content-type-options
    • https://lawnco.net/irrigation-management → no x-content-type-options
    • https://lawnco.net/commercial-landscaping-maintenance → no x-content-type-options
    • https://lawnco.net/subdivision-landscape-management → no x-content-type-options
    • https://lawnco.net/commercial-industrial-landscape-management → no x-content-type-options
    • https://lawnco.net/ice-snow-management → no x-content-type-options
    • https://lawnco.net/holiday-lighting → 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://lawnco.net/ → no referrer-policy
    • https://lawnco.net/about-us → no referrer-policy
    • https://lawnco.net/residential-landscaping-design-construction → no referrer-policy
    • https://lawnco.net/plant-health-lawn-care → no referrer-policy
    • https://lawnco.net/lawn-maintenance → no referrer-policy
    • https://lawnco.net/tree-care-service → no referrer-policy
    • https://lawnco.net/irrigation-management → no referrer-policy
    • https://lawnco.net/commercial-landscaping-maintenance → no referrer-policy
    • https://lawnco.net/subdivision-landscape-management → no referrer-policy
    • https://lawnco.net/commercial-industrial-landscape-management → no referrer-policy
    • https://lawnco.net/ice-snow-management → no referrer-policy
    • https://lawnco.net/holiday-lighting → 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://lawnco.net/ → no permissions-policy
    • https://lawnco.net/about-us → no permissions-policy
    • https://lawnco.net/residential-landscaping-design-construction → no permissions-policy
    • https://lawnco.net/plant-health-lawn-care → no permissions-policy
    • https://lawnco.net/lawn-maintenance → no permissions-policy
    • https://lawnco.net/tree-care-service → no permissions-policy
    • https://lawnco.net/irrigation-management → no permissions-policy
    • https://lawnco.net/commercial-landscaping-maintenance → no permissions-policy
    • https://lawnco.net/subdivision-landscape-management → no permissions-policy
    • https://lawnco.net/commercial-industrial-landscape-management → no permissions-policy
    • https://lawnco.net/ice-snow-management → no permissions-policy
    • https://lawnco.net/holiday-lighting → no permissions-policy
  • 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 (18 script tags)
    • kit.fontawesome.com (18 script tags)
    • www.google.com (1 script tag)
  • 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: /wp-login.php
7 checks passed, 1 not applicable
  • OKHTTPS

    All 18 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.

  • OKMixed content

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

  • OKForms over HTTPS

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

Earlier scans of lawnco.net

No other scans of this site yet.

Sites scoring near lawnco.net

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

Own lawnco.net?

lawnco.net SEO report | DIY SEO Hub