Scanned sites / www.foliocafe.ca / 2026-11-01-2306

www.foliocafe.ca scan from 2026-11-01 23:06:24 UTC DR 2

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-11-01-2306

Scanned 2026-11-01 23:06:24 UTC, finished 2026-11-01 23:24:57 UTC. Found on page 1 of brave web search results

Site: https://www.foliocafe.ca/

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

72/ 100Needs work

On November 1, 2026 the Site Spider crawled 1 page and 15 assets of www.foliocafe.ca, starting from https://www.foliocafe.ca/. It scored 72 out of 100, a result that needs work. 5 of 33 checks found something to fix, led by meta descriptions (1), thin content (1), headings (1); 26 checks passed. Most of the points went to meta descriptions (−8), thin content (−8), headings (−6). 2 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. 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: Medium4 medium, 2 low and 2 info findings. See the security findings ↓

Pages crawled
1
Assets fetched
15
Status
Completed
Checks with issues
5 of 33
CoverageComplete crawl

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

  • Title tagsOK
    0 of 1 page have title issues.
  • Meta descriptions1 issue
    1 of 1 page have meta description issues.
    −8 points
  • Headings1 issue
    1 of 1 page have heading issues.
    −6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 5 destinations checked.
    −0.4 points
  • RedirectsOK
    0 redirecting URLs, 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 1 indexable page have indexability warnings.
  • Image alt textOK
    0 of 1 image reference have no alt attribute. 1 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 15 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1 issue
    No sitemap found. Tried: https://www.foliocafe.ca/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −6 points
  • Internal link countsOK
    Internal link counts for 1 page; none is a dead end or buried.
  • Thin content1 issue
    1 of 1 page have fewer than 200 words.
    −8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 1 page URL are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 1 page have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 1 page are open to search engines.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure1 noted
    1 of 1 page could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 1 page keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (1 indexable page checked).
  • Near duplicatesOK
    No near duplicates among 0 pages with enough text to compare.
  • Soft 404sOK
    None of 1 page answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsOK
    0 of 0 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 7 response headers recorded across 16 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 1 page; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingOK
    No unfamiliar lower-case words on 1 page (English pages only).

Where this scan sits among all scanned sites

2873 sites, median 80%, average 79%

www.foliocafe.ca scores 72%, higher than 21% of the 2873 scanned sites. See the full ranking.

0751500%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites72% 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 important SEO issues to address, including a missing sitemap, meta description, and multiple H1 tags. Focusing on these will enhance your site's crawlability and user experience.

  1. 1

    Create a Sitemap

    Why: A sitemap helps search engines index your site better.

    How: Create a sitemap.xml file and list all important pages. Upload it to the root directory.

    Checks: sitemap-coverage

  2. 2

    Fix Meta Descriptions

    Why: Meta descriptions improve click-through rates from search results.

    How: Write a concise meta description (150-160 characters) summarizing your page’s content.

    Checks: meta-descriptions

  3. 3

    Simplify Headings

    Why: Multiple H1s confuse search engines and dilute content value.

    How: Limit the page to one H1 tag. Use H2s and H3s for subheadings.

    Checks: headings

  4. 4

    Improve Content Length

    Why: Ensuring more than 200 words enhances relevancy and ranking potential.

    How: Add more informative content relevant to your site's focus.

    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 site has several security weaknesses that could allow attackers to intercept traffic and exploit vulnerabilities. Addressing these issues is important for protecting user data and enhancing overall security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be intercepted on first-time visits without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of a CSP increases the risk of XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: No protection against Clickjacking, allowing malicious framing.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: Using jQuery 1.12.4 with known vulnerabilities raises security risks.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing MIME Sniffing Protection (X-Content-Type-Options)Low

    Why it matters: Lack of protection may lead to file type confusion in browsers.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without it, sensitive URL information can leak.

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

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Exposed browser features can pose risk if scripts are injected.

    Fix: Add the header: Permissions-Policy: *;

    Evidence: Permissions policy

  8. 8

    Sensitive Paths in robots.txtInfo

    Why it matters: publicly accessible robots.txt can reveal sensitive site paths.

    Fix: Consider securing access to /wp-admin/ and other sensitive paths.

    Evidence: Sensitive paths in robots.txt

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://www.foliocafe.ca/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 1 HTML page 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.foliocafe.ca/ → 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://www.foliocafe.ca/ → 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://www.foliocafe.ca/ → 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://www.foliocafe.ca/ → 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://www.foliocafe.ca/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 1.12.4. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.12.4 in https://www.foliocafe.ca/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • 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/
7 checks passed, 1 not applicable
  • OKHTTPS

    All 1 crawled page 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

    1 form 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.

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

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.foliocafe.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.foliocafe.ca?

  • 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.foliocafe.ca. Removal needs no account and no proof of purchase.