Scanned sites / www.eitherorpdx.com / 2026-09-19-0648
www.eitherorpdx.com scan from 9/19/2026, 6:48:09 AM
Scan 2026-09-19-0648
Scanned 9/19/2026, 6:48:09 AM, finished 9/19/2026, 6:55:03 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.
On September 19, 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 14 checks found something to fix, led by heavy assets (25), meta descriptions (8), title tags (7); 6 checks passed. 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 14
- Title tags7 issues7 of 8 pages have title issues. 6 noindex or canonicalized pages excluded.
- Meta descriptions8 issues8 of 8 pages have meta description issues. 6 noindex or canonicalized pages excluded.
- Headings2 issues2 of 8 pages have heading issues. 6 noindex or canonicalized pages excluded.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK1 redirecting URL, 0 of them chained.
- Non-200 responsesOK1 URL did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability3 issues3 of 11 indexable pages have indexability warnings. 3 pages noindex by design.
- Image alt textOK0 of 175 image references have no alt attribute. 161 use an empty alt (decorative), which is fine.
- Heavy assets25 issues25 assets larger than 500 KB among the 100 heaviest.
- Orphan pages1 issue1 page have no internal links pointing at them.
- Sitemap coverage1 issue5 sitemaps listing 8 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 1 reachable only via the sitemap.
- Thin content5 issues5 of 8 pages have fewer than 200 words. 6 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1101 sites, median 82%, average 80%
www.eitherorpdx.com scores 78%, higher than 33% of the 1101 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has several key issues impacting SEO performance, primarily around title tags, meta descriptions, and indexability. Prioritizing these can greatly enhance visibility. Below are the top recommended fixes.
- 1
Fix Redirects
Why: A redirect on sitemap can confuse search engines and users.
How: Change the sitemap link to direct to the final URL without the 301 redirect.
Checks: redirects
- 2
Update Title Tags
Why: 7 pages have short titles which can limit SEO effectiveness.
How: Revise title tags to be at least 30 characters long and descriptive of the page content.
Checks: titles
- 3
Add Meta Descriptions
Why: Missing meta descriptions can affect Click-Through Rate in search results.
How: Create a compelling meta description for each page, targeted for search relevancy.
Checks: meta-descriptions
- 4
Implement H1 Tags
Why: Missing H1 tags hurt page structure and SEO ranking potential.
How: Ensure each page has one H1 tag that clearly indicates the page topic.
Checks: headings
- 5
Resolve Orphan Pages
Why: Orphan pages are not linked internally, affecting their discoverability by search engines.
How: Add internal links to the orphan page from relevant pages within your site.
Checks: orphan-pages
- 6
Improve Page Content
Why: Thin content can lead to lower rankings.
How: Enhance pages with fewer than 200 words by adding valuable content to provide more context.
Checks: thin-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 crawlThe website lacks a Content Security Policy and Permissions Policy, which may expose it to cross-site scripting and other attacks. Furthermore, there are third-party scripts without Subresource Integrity, which heightens security risk. The robots.txt file lists sensitive paths, potentially disclosing private areas of the site.
- 0 high
- 1 medium
- 1 low
- 2 info
- 1
Missing Content Security PolicyMedium
Why it matters: Without a Content Security Policy, scripts, styles, and frames can be loaded from any source, increasing the risk of XSS and other attacks.
Fix: Implement a Content-Security-Policy header with appropriate directives, e.g., `Content-Security-Policy: default-src 'self';`.
Evidence: Content Security Policy
- 2
Third-party Scripts Without Subresource IntegrityLow
Why it matters: The site includes scripts from another domain without Subresource Integrity, which could allow unauthorized changes to scripts served.
Fix: Consider implementing a Content Security Policy that specifically allows trusted sources, or use Subresource Integrity for third-party scripts.
Evidence: Third-party scripts
- 3
Missing Permissions PolicyInfo
Why it matters: The absence of a Permissions-Policy header allows potentially harmful features like camera and geolocation access by unauthorized scripts.
Fix: Add a Permissions-Policy header, e.g., `Permissions-Policy: geolocation=(), microphone=(), camera=();`.
Evidence: Permissions policy
- 4
Sensitive Paths in robots.txtInfo
Why it matters: The robots.txt file lists paths that appear private, which might expose sensitive areas to unauthorized users.
Fix: Ensure proper access controls are in place instead of relying on robots.txt for security.
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.
This report was produced by the DIY SEO Hub Site Spider crawling www.eitherorpdx.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.