Scanned sites / weaverfamilyfarms.com / 2026-09-27-0100

weaverfamilyfarms.com scan from 9/27/2026, 1:00:01 AM

Scan 2026-09-27-0100

Scanned 9/27/2026, 1:00:01 AM, finished 9/27/2026, 3:46:56 PM. Found on page 1 of chatgpt for browser (api usage) results

Site: https://weaverfamilyfarms.com/

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

81/ 100Good

On September 27, 2026 the Site Spider crawled 104 pages and 459 assets of weaverfamilyfarms.com, starting from https://weaverfamilyfarms.com/. It scored 81 out of 100, a good result. 6 of 16 checks found something to fix, led by meta descriptions (82), heavy assets (117), title tags (55); 7 checks passed. Most of the points went to meta descriptions (−6.3), heavy assets (−6), title tags (−5.3). 3 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: Medium2 medium and 3 low findings. See the security findings ↓

Pages crawled
104
Assets fetched
459
Status
Completed
Checks with issues
6 of 16
CoverageComplete crawl

563 of 563 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 186 left unchecked.

  • Title tags55 issues
    55 of 98 pages have title issues. 6 noindex or canonicalized pages excluded.
    −5.3 points
  • Meta descriptions82 issues
    82 of 98 pages have meta description issues. 6 noindex or canonicalized pages excluded.
    −6.3 points
  • Headings11 issues
    11 of 98 pages have heading issues. 6 noindex or canonicalized pages excluded.
    −0.6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites26 issues
    26 destinations answered with an error, 95 could not be determined (timeouts, rate limits or refusals), 186 were left unchecked by the per-scan cap, of 300 destinations checked.
    −4 points
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses1 noted
    1 URL did not return a 2xx response. 0 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 98 indexable pages have indexability warnings. 6 pages noindex by design.
  • Image alt textOK
    0 of 2220 image references have no alt attribute. 367 use an empty alt (decorative), which is fine.
  • Heavy assets117 issues
    117 assets larger than 500 KB among 459 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage14 issues
    4 sitemaps listing 84 URLs: 14 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −0.8 points
  • Internal link countsOK
    Internal link counts for 104 pages.
  • Thin contentOK
    0 of 98 pages have fewer than 200 words. 6 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1315 sites, median 80%, average 79%

weaverfamilyfarms.com scores 81%, higher than 51% of the 1315 scanned sites. See the full ranking.

038750%: 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%: 1 site36%: 1 site37%: 1 site38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 1 site49%: 2 sites50%: 3 sites51%: 5 sites52%: 5 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 13 sites63%: 11 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 26 sites68%: 25 sites69%: 14 sites70%: 30 sites71%: 29 sites72%: 36 sites73%: 33 sites74%: 41 sites75%: 36 sites76%: 47 sites77%: 44 sites78%: 56 sites79%: 45 sites80%: 66 sites81%: 75 sites82%: 68 sites83%: 58 sites84%: 60 sites85%: 44 sites86%: 51 sites87%: 44 sites88%: 49 sites89%: 36 sites90%: 28 sites91%: 31 sites92%: 18 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 1 site100%: 49 sites81% 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 a solid health score, but there are some important areas for improvement, particularly with meta descriptions, titles, headings, and heavy assets. Addressing these will enhance user experience and SEO performance.

  1. 1

    Fix Missing H1 Tags

    Why: H1 tags are crucial for SEO and help users understand page content.

    How: Add a relevant H1 tag to pages missing one, ensuring each reflects the page's title.

    Checks: headings

  2. 2

    Improve Title Tags

    Why: Many pages share titles or are too short, harming SEO.

    How: Rewrite titles for unique and descriptive tags that are 50-60 characters long.

    Checks: titles

  3. 3

    Optimize Meta Descriptions

    Why: Most pages have issues, which can impact click-through rates.

    How: Create unique meta descriptions for pages without them and limit them to 150-160 characters.

    Checks: meta-descriptions

  4. 4

    Shrink Heavy Assets

    Why: Large assets can slow down page load times and impact user experience.

    How: Compress images identified as large to reduce load times, especially those used on multiple pages.

    Checks: heavy-assets

  5. 5

    Update Sitemap Coverage

    Why: Some crawled pages are not in your sitemap, which can lead to lower visibility.

    How: Ensure all relevant pages, especially blog pagination, are included in the sitemap.

    Checks: sitemap-coverage

  6. 6

    Address Redirects

    Why: Redirects can create a poor user experience and lose link equity.

    How: Review the redirect to the sitemap and remove unnecessary redirects.

    Checks: redirects

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 essential security headers, which can expose it to various risks such as clickjacking and interception of initial requests. Recommendations include adding necessary headers and addressing sensitive paths listed in the robots.txt file.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on the first request if they type the address without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows the page to be embedded in a frame, increasing clickjacking risk.

    Fix: Add the header: X-Frame-Options: DENY or use a CSP directive like frame-ancestors 'none'.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly execute files that are not scripts, due to content type mismatches.

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

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: This absence can expose sensitive URL information to third-party sites when users navigate away.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade.

    Evidence: Referrer policy

  5. 5

    Exposed Server and Framework VersionsLow

    Why it matters: Revealing versions can help attackers find known vulnerabilities that can be exploited.

    Fix: Remove or hide the headers: Server and X-Powered-By.

    Evidence: Software version disclosure

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://weaverfamilyfarms.com/ → no strict-transport-security
    • https://weaverfamilyfarms.com/browse/ → no strict-transport-security
    • https://weaverfamilyfarms.com/about-us/ → no strict-transport-security
    • https://weaverfamilyfarms.com/contact-us/ → no strict-transport-security
    • https://weaverfamilyfarms.com/blog-news/ → no strict-transport-security
    • https://weaverfamilyfarms.com/why-are-my-pumpkins-rotting-on-the-bottom-heres-what-causes-it/ → no strict-transport-security
    • https://weaverfamilyfarms.com/can-you-leave-pumpkins-on-the-vine-too-long-heres-what-i-do/ → no strict-transport-security
    • https://weaverfamilyfarms.com/how-i-cure-homegrown-pumpkins-so-they-last-longer/ → no strict-transport-security
    • https://weaverfamilyfarms.com/how-do-i-know-when-a-pumpkin-is-ready-to-pick-6-signs-i-look-for/ → no strict-transport-security
    • https://weaverfamilyfarms.com/why-is-my-pumpkin-growing-weird-what-caused-these-odd-shapes/ → no strict-transport-security
    • https://weaverfamilyfarms.com/harvesting-our-first-pumpkins-of-the-season-earlier-than-expected/ → no strict-transport-security
    • https://weaverfamilyfarms.com/our-pumpkin-patch-in-mid-august-what-were-seeing-so-far/ → no strict-transport-security
  • 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://weaverfamilyfarms.com/ → no x-frame-options
    • https://weaverfamilyfarms.com/browse/ → no x-frame-options
    • https://weaverfamilyfarms.com/about-us/ → no x-frame-options
    • https://weaverfamilyfarms.com/contact-us/ → no x-frame-options
    • https://weaverfamilyfarms.com/blog-news/ → no x-frame-options
    • https://weaverfamilyfarms.com/why-are-my-pumpkins-rotting-on-the-bottom-heres-what-causes-it/ → no x-frame-options
    • https://weaverfamilyfarms.com/can-you-leave-pumpkins-on-the-vine-too-long-heres-what-i-do/ → no x-frame-options
    • https://weaverfamilyfarms.com/how-i-cure-homegrown-pumpkins-so-they-last-longer/ → no x-frame-options
    • https://weaverfamilyfarms.com/how-do-i-know-when-a-pumpkin-is-ready-to-pick-6-signs-i-look-for/ → no x-frame-options
    • https://weaverfamilyfarms.com/why-is-my-pumpkin-growing-weird-what-caused-these-odd-shapes/ → no x-frame-options
    • https://weaverfamilyfarms.com/harvesting-our-first-pumpkins-of-the-season-earlier-than-expected/ → no x-frame-options
    • https://weaverfamilyfarms.com/our-pumpkin-patch-in-mid-august-what-were-seeing-so-far/ → 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://weaverfamilyfarms.com/ → no x-content-type-options
    • https://weaverfamilyfarms.com/browse/ → no x-content-type-options
    • https://weaverfamilyfarms.com/about-us/ → no x-content-type-options
    • https://weaverfamilyfarms.com/contact-us/ → no x-content-type-options
    • https://weaverfamilyfarms.com/blog-news/ → no x-content-type-options
    • https://weaverfamilyfarms.com/why-are-my-pumpkins-rotting-on-the-bottom-heres-what-causes-it/ → no x-content-type-options
    • https://weaverfamilyfarms.com/can-you-leave-pumpkins-on-the-vine-too-long-heres-what-i-do/ → no x-content-type-options
    • https://weaverfamilyfarms.com/how-i-cure-homegrown-pumpkins-so-they-last-longer/ → no x-content-type-options
    • https://weaverfamilyfarms.com/how-do-i-know-when-a-pumpkin-is-ready-to-pick-6-signs-i-look-for/ → no x-content-type-options
    • https://weaverfamilyfarms.com/why-is-my-pumpkin-growing-weird-what-caused-these-odd-shapes/ → no x-content-type-options
    • https://weaverfamilyfarms.com/harvesting-our-first-pumpkins-of-the-season-earlier-than-expected/ → no x-content-type-options
    • https://weaverfamilyfarms.com/our-pumpkin-patch-in-mid-august-what-were-seeing-so-far/ → 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://weaverfamilyfarms.com/ → no referrer-policy
    • https://weaverfamilyfarms.com/browse/ → no referrer-policy
    • https://weaverfamilyfarms.com/about-us/ → no referrer-policy
    • https://weaverfamilyfarms.com/contact-us/ → no referrer-policy
    • https://weaverfamilyfarms.com/blog-news/ → no referrer-policy
    • https://weaverfamilyfarms.com/why-are-my-pumpkins-rotting-on-the-bottom-heres-what-causes-it/ → no referrer-policy
    • https://weaverfamilyfarms.com/can-you-leave-pumpkins-on-the-vine-too-long-heres-what-i-do/ → no referrer-policy
    • https://weaverfamilyfarms.com/how-i-cure-homegrown-pumpkins-so-they-last-longer/ → no referrer-policy
    • https://weaverfamilyfarms.com/how-do-i-know-when-a-pumpkin-is-ready-to-pick-6-signs-i-look-for/ → no referrer-policy
    • https://weaverfamilyfarms.com/why-is-my-pumpkin-growing-weird-what-caused-these-odd-shapes/ → no referrer-policy
    • https://weaverfamilyfarms.com/harvesting-our-first-pumpkins-of-the-season-earlier-than-expected/ → no referrer-policy
    • https://weaverfamilyfarms.com/our-pumpkin-patch-in-mid-august-what-were-seeing-so-far/ → 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: cloudflare (563 responses)
    • x-powered-by: PHP/8.1.34 (110 responses)
  • 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 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/
8 checks passed, 1 not applicable
  • OKHTTPS

    All 104 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set.

  • OKPermissions policy

    permissions-policy is set on all 104 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

    87 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    1 library version 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 weaverfamilyfarms.com

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

Own weaverfamilyfarms.com?

  • 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 weaverfamilyfarms.com. Removal needs no account and no proof of purchase.
weaverfamilyfarms.com scan 2026-09-27-0100 | DIY SEO Hub