Scanned sites / www.roastlocal.com / 2026-09-26-1922

www.roastlocal.com scan from 9/26/2026, 7:22:34 PM

Scan 2026-09-26-1922

Scanned 9/26/2026, 7:22:34 PM, finished 9/27/2026, 6:25:26 PM

Site: https://www.roastlocal.com/

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

86/ 100Good

On September 26, 2026 the Site Spider crawled 4997 pages and 992 assets of www.roastlocal.com, starting from https://www.roastlocal.com/. It scored 86 out of 100, a good result. 9 of 16 checks found something to fix, led by heavy assets (34), thin content (1,978), sitemap coverage (1,616); 5 checks passed. Most of the points went to heavy assets (−6), thin content (−3.2), sitemap coverage (−1.9). 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 and 1 low findings. See the security findings ↓

Pages crawled
4997
Assets fetched
992
Status
Completed
Checks with issues
9 of 16
CoverageJob finished, partial coverage

5,989 of 6,000 discovered URLs were fetched, 11 blocked by robots.txt, 148,982 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. 300 link destinations on other sites were checked, 4903 left unchecked.

  • Title tags284 issues
    284 of 4991 pages have title issues. 2 noindex or canonicalized pages excluded.
    −0.6 points
  • Meta descriptions685 issues
    685 of 4991 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −1.1 points
  • Headings1 issue
    1 of 4991 pages have heading issues. 2 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites3 issues
    3 destinations answered with an error, 21 could not be determined (timeouts, rate limits or refusals), 4903 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects1 issue
    4 redirecting URLs, 0 of them chained.
  • Non-200 responses8 noted
    8 URLs did not return a 2xx response. 4 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 4993 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 12326 image references have no alt attribute.
  • Heavy assets34 issues
    34 assets larger than 500 KB among 992 fetched assets.
    −6 points
  • Orphan pages1,599 issues
    1599 pages have no internal links pointing at them.
    −1.3 points
  • Sitemap coverage1,616 issues
    1 sitemap listing 5,000+ URLs (first 5,000 entries read): 13 crawled pages missing, 4 listed URLs broken or redirecting, 1599 reachable only via the sitemap. 18 listed URLs not crawled within the 5000-page budget.
    −1.9 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content1,978 issues
    1978 of 4991 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
    −3.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1315 sites, median 80%, average 79%

www.roastlocal.com scores 86%, higher than 74% 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 sites86% 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 several SEO improvements to make, particularly with redirects, title tags, and orphan pages. Prioritize resolving redirect issues, optimizing titles and meta descriptions, addressing heavy assets, linking orphan pages, and improving thin content for better visibility.

  1. 1

    Fix Redirects

    Why: Redirects hinder user experience and SEO performance.

    How: Update the affected URLs to avoid redirects. Ensure that URLs lead directly to the intended pages without 308 status.

    Checks: redirects

  2. 2

    Optimize Title Tags

    Why: 284 title issues can affect search rankings and click-through rates.

    How: Revise titles to ensure they are longer than 30 characters and unique for each page.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 685 meta description issues may prevent effective search result displays.

    How: Craft engaging and descriptive meta descriptions per page, keeping them within 150-160 characters.

    Checks: meta-descriptions

  4. 4

    Address Orphan Pages

    Why: 1,599 orphan pages lack internal links, reducing findability.

    How: Link from relevant pages to orphan pages to create an internal link structure.

    Checks: orphan-pages

  5. 5

    Reduce Heavy Assets

    Why: Large files can slow down page loading, affecting user experience.

    How: Optimize heavy assets (images) to reduce file sizes below 500 KB and improve site speed.

    Checks: heavy-assets

  6. 6

    Enhance Thin Content

    Why: 1978 pages with less than 200 words should be improved for value and relevance.

    How: Add content to thin pages to reach over 200 words, ensuring relevance to the topic.

    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 crawl

The website roastlocal.com has a Content Security Policy that is too permissive, allowing for inline and eval scripts, which diminishes its effectiveness against potential attacks. Additionally, it reveals some framework information in response headers. Adjusting these settings will enhance the site's security.

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

    Permissive Content Security PolicyMedium

    Why it matters: The policy allows 'unsafe-inline' and 'unsafe-eval', increasing vulnerability to script injection attacks.

    Fix: Update the Content-Security-Policy to remove 'unsafe-inline' and 'unsafe-eval' from the script-src directive.

    Evidence: Content Security Policy

  2. 2

    Software Version DisclosureLow

    Why it matters: The X-Powered-By header reveals the use of Next.js, exposing the site to targeted attacks.

    Fix: Remove the X-Powered-By header in the server configuration by setting `x-powered-by: false` to reduce information leakage.

    Evidence: Software version disclosure

What the checks found

  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://www.roastlocal.com/ → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/explore → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/states → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/shop → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-halifax → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-toronto → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-phoenix → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-boston → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-nashville → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-winnipeg → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
    • https://www.roastlocal.com/blog/best-coffee-roasters-washington-dc → default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.supabase.co https://plausible.io https://us-assets.i.posthog.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: h
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: Vercel (5989 responses)
    • x-powered-by: Next.js (4782 responses)
12 checks passed, 2 not applicable
  • OKHTTPS

    All 4993 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

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

  • OKClickjacking protection

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

  • OKMIME sniffing protection

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

  • OKReferrer policy

    referrer-policy is set on all 4993 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 4993 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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

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