Scanned sites / www.eitherorpdx.com / 2026-09-28-0344

www.eitherorpdx.com scan from 9/28/2026, 3:44:10 AM

Scan 2026-09-28-0344

Scanned 9/28/2026, 3:44:10 AM, finished 9/28/2026, 3:52:24 AM. Found with openstreetmap overpass

Site: https://www.eitherorpdx.com/

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

78/ 100Good

On September 28, 2026 the Site Spider crawled 14 pages and 268 assets of www.eitherorpdx.com, starting from https://www.eitherorpdx.com/. It scored 78 out of 100, a good result. 8 of 16 checks found something to fix, led by heavy assets (25), title tags (7), meta descriptions (8); 4 checks passed. Most of the points went to heavy assets (−6), title tags (−5), meta descriptions (−4.6). 4 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, 1 low and 2 info findings. See the security findings ↓

Pages crawled
14
Assets fetched
268
Status
Completed
Checks with issues
8 of 16
CoverageComplete crawl

282 of 283 discovered URLs were fetched, 1 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 18 link destinations on other sites were checked.

  • Title tags7 issues
    7 of 8 pages have title issues. 6 noindex or canonicalized pages excluded.
    −5 points
  • Meta descriptions8 issues
    8 of 8 pages have meta description issues. 6 noindex or canonicalized pages excluded.
    −4.6 points
  • Headings2 issues
    2 of 8 pages have heading issues. 6 noindex or canonicalized pages excluded.
    −0.9 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites32 noted
    0 destinations answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
  • 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.
  • Indexability3 issues
    3 of 11 indexable pages have indexability warnings. 3 pages noindex by design.
    −2.1 points
  • Image alt textOK
    0 of 175 image references have no alt attribute. 161 use an empty alt (decorative), which is fine.
  • Heavy assets25 issues
    25 assets larger than 500 KB among 268 fetched assets.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage1 issue
    5 sitemaps listing 8 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −0.4 points
  • Internal link countsOK
    Internal link counts for 14 pages.
  • Thin content5 issues
    5 of 8 pages have fewer than 200 words. 6 noindex or canonicalized pages excluded.
    −2.9 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1321 sites, median 80%, average 79%

www.eitherorpdx.com scores 78%, higher than 38% of the 1321 scanned sites. See the full ranking.

037740%: 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%: 1 site39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 4 sites52%: 5 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 10 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%: 48 sites77%: 45 sites78%: 57 sites79%: 46 sites80%: 65 sites81%: 74 sites82%: 68 sites83%: 59 sites84%: 59 sites85%: 45 sites86%: 51 sites87%: 44 sites88%: 50 sites89%: 35 sites90%: 28 sites91%: 31 sites92%: 19 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 1 site100%: 49 sites78% 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 important SEO issues require attention, particularly around meta descriptions, redirects, and heavy assets. Addressing these will improve visibility and site performance.

  1. 1

    Fix Meta Descriptions

    Why: All pages lack meta descriptions, impairing click-through rates.

    How: Create relevant meta descriptions for each of the 8 pages; keep them under 160 characters.

    Checks: meta-descriptions

  2. 2

    Resolve Redirects

    Why: One URL is redirecting unnecessarily, which can waste crawl budget and create confusion.

    How: Update links to point directly to the final URL instead of relying on the redirect.

    Checks: redirects

  3. 3

    Address Heavy Assets

    Why: Large assets can slow down page load time, negatively impacting user experience.

    How: Compress or optimize the large images listed to reduce their file sizes.

    Checks: heavy-assets

  4. 4

    Add Missing Headings

    Why: Two pages are missing H1 headings, affecting their SEO structure.

    How: Insert H1 headings on both identified pages to improve SEO and content organization.

    Checks: headings

  5. 5

    Review Thin Content

    Why: Several pages have thin content, which can harm visibility in search results.

    How: Enhance content on these pages to exceed 200 words by adding relevant information.

    Checks: thin-content

  6. 6

    Link to Orphan Page

    Why: One page has no internal links, limiting its discoverability by users and search engines.

    How: Create internal links to this orphan page from other relevant pages.

    Checks: orphan-pages

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 important security headers, specifically a Content Security Policy and Permissions Policy. This can expose it to various web vulnerabilities. Implementing these headers will help restrict sources of content and limit potential damage from compromised scripts.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a CSP, the site is vulnerable to attacks that exploit the loading of malicious scripts or styles.

    Fix: Implement a CSP header like: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  2. 2

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Using external scripts without SRI can compromise the site if those scripts are tampered with.

    Fix: Consider adding Subresource Integrity to scripts from unpkg.com or implementing a CSP.

    Evidence: Third-party scripts

  3. 3

    Missing Permissions PolicyInfo

    Why it matters: No Permissions Policy means potentially vulnerable features (like camera access) cannot be restricted.

    Fix: Add a Permissions-Policy header like: Permissions-Policy: geolocation=(self)

    Evidence: Permissions policy

  4. 4

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt disallows access to /wp-admin/, exposing it as a potential target for attacks.

    Fix: Implement proper access controls to secure sensitive paths or consider removing them from robots.txt.

    Evidence: Sensitive paths in robots.txt

What the checks found

  • FoundContent Security PolicyMedium

    None of the 14 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.eitherorpdx.com/ → no content-security-policy
    • https://eitherorpdx.com/ → no content-security-policy
    • https://eitherorpdx.com/tanglewood/ → no content-security-policy
    • https://eitherorpdx.com/gift/ → no content-security-policy
    • https://eitherorpdx.com/contact-us/ → no content-security-policy
    • https://eitherorpdx.com/contact-us/?reason=event → no content-security-policy
    • https://eitherorpdx.com/contact-us/?reason=catering → no content-security-policy
    • https://eitherorpdx.com/2025/09/22/hello-world/ → no content-security-policy
    • https://eitherorpdx.com/sample-page/ → no content-security-policy
    • https://eitherorpdx.com/category/uncategorized/ → no content-security-policy
    • https://eitherorpdx.com/author/dklongdagiac-com/ → no content-security-policy
    • https://eitherorpdx.com/2025/09/22/hello-world/?replytocom=1 → no content-security-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.eitherorpdx.com/ → no permissions-policy
    • https://eitherorpdx.com/ → no permissions-policy
    • https://eitherorpdx.com/tanglewood/ → no permissions-policy
    • https://eitherorpdx.com/gift/ → no permissions-policy
    • https://eitherorpdx.com/contact-us/ → no permissions-policy
    • https://eitherorpdx.com/contact-us/?reason=event → no permissions-policy
    • https://eitherorpdx.com/contact-us/?reason=catering → no permissions-policy
    • https://eitherorpdx.com/2025/09/22/hello-world/ → no permissions-policy
    • https://eitherorpdx.com/sample-page/ → no permissions-policy
    • https://eitherorpdx.com/category/uncategorized/ → no permissions-policy
    • https://eitherorpdx.com/author/dklongdagiac-com/ → no permissions-policy
    • https://eitherorpdx.com/2025/09/22/hello-world/?replytocom=1 → no permissions-policy
  • 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.)

    • unpkg.com (14 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/
11 checks passed, 1 not applicable
  • OKHTTPS

    All 14 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 14 HTML pages.

  • 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

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

Own www.eitherorpdx.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 www.eitherorpdx.com. Removal needs no account and no proof of purchase.
www.eitherorpdx.com scan 2026-09-28-0344 | DIY SEO Hub