Scanned sites / cafebloom.ca / 2026-10-01-2230

cafebloom.ca scan from 2026-10-01 22:30:13 UTC DR 16

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

Scan 2026-10-01-2230

Scanned 2026-10-01 22:30:13 UTC, finished 2026-10-02 00:03:38 UTC. Found on page 3 of brave web search results

Site: https://cafebloom.ca/

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

69/ 100Needs work

On October 1, 2026 the Site Spider crawled 6 pages and 210 assets of cafebloom.ca, starting from https://cafebloom.ca/. It scored 69 out of 100, a result that needs work. 6 of 27 checks found something to fix, led by title tags (5), meta descriptions (5), thin content (3); 14 checks passed. Most of the points went to title tags (−10), meta descriptions (−8), thin content (−4.8). 7 checks found something the score does not count, listed as noted. 10 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, 3 low and 1 info findings. See the security findings ↓

Pages crawled
6
Assets fetched
210
Status
Completed
Checks with issues
6 of 27
CoverageComplete crawl

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

  • Title tags5 issues
    5 of 5 pages have title issues.
    −10 points
  • Meta descriptions5 issues
    5 of 5 pages have meta description issues.
    −8 points
  • HeadingsOK
    0 of 5 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesOK
    0 destinations answered with an error, of 5 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses5 noted
    5 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limited1 issue
    3 URLs (1 page) answered HTTP 429 on every try, so the crawler backed off and moved on without analysing them. A site that throttles crawlers this hard can throttle search engines too.
    −0.8 points
  • IndexabilityOK
    0 of 5 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 37 image references have no alt attribute. 27 use an empty alt (decorative), which is fine.
  • Heavy assets7 issues
    7 assets larger than 500 KB among 210 fetched assets. 2 documents over that size are listed but not counted: downloads are not page weight.
    −4.2 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage3 issues
    No sitemap found. Tried: https://cafebloom.ca/sitemap.xml (429). Add one at /sitemap.xml or list it in robots.txt.
    −3.6 points
  • Internal link countsOK
    Internal link counts for 5 pages; none is a dead end or buried.
  • Thin content3 issues
    3 of 5 pages have fewer than 200 words.
    −4.8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 6 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 5 pages have a canonical worth checking.
  • Robots directives5 noted
    5 pages carry a robots directive; 0 carry none.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure5 noted
    5 of 5 pages could use the title, heading and snippet space better.
  • Image weight and alt length20 noted
    20 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 5 pages 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 216 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 5 pages; 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 Insights5 noted
    Mobile performance 62 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2909 sites, median 80%, average 79%

cafebloom.ca scores 69%, higher than 14% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites69% 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

Written from an earlier version of the analysis (rules v4). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your site has several issues that need attention, particularly with non-200 responses, meta descriptions, titles, and thin content. Addressing these will enhance your SEO performance.

  1. 1

    Fix Rate Limiting

    Why: Rate limiting affects crawler access, hindering indexing by search engines.

    How: Reduce rate limiting on your server to allow crawlers to access https://cafebloom.ca/cafe-menu, https://cafebloom.ca/robots.txt, and https://cafebloom.ca/sitemap.xml.

    Checks: rate-limited

  2. 2

    Add a Sitemap

    Why: A sitemap helps search engines discover all your pages effectively.

    How: Create a sitemap and host it at https://cafebloom.ca/sitemap.xml. Ensure it's not rate-limited.

    Evidence: One URL: no sitemap found.

    1 page affected

    Checks: sitemap-coverage

  3. 3

    Improve Title Tags

    Why: Short title tags can limit visibility in search results, affecting click-through rates.

    How: Revise title tags to be more descriptive and within the recommended length. Aim for 50-60 characters.

    Checks: titles

  4. 4

    Write Meta Descriptions

    Why: Missing meta descriptions can reduce click-through rates from search results.

    How: Create engaging meta descriptions for all pages, ensuring they are concise and around 150-160 characters.

    Checks: meta-descriptions

  5. 5

    Reduce Heavy Assets

    Why: Large assets slow down page loading, negatively impacting user experience and SEO.

    How: Optimize or compress heavy assets, especially those over 500 KB. Consider using formats like WebP for images.

    Evidence: 437 KB of stylesheet, loaded by 5 pages, so every visitor to any of them downloads it.

    5 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  6. 6

    Address Thin Content

    Why: Thin content may lead to lower rankings in search engines as it provides little value.

    How: Expand content on pages with fewer than 200 words to enhance relevance and user engagement.

    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

Your website has several security issues that need to be addressed. High priority items include the absence of HTTP Strict Transport Security, Content Security Policy, and Clickjacking protection. These omissions can expose your site to attacks. Additionally, there are issues with vulnerable JavaScript libraries and server version disclosure, which could be exploited. Immediate fixes are recommended.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users accessing your site over HTTP may be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows untrusted content to load, increasing attack risk.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, your pages can be embedded in other sites, exposing users.

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

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 2.1.0 can lead to vulnerabilities if exploited.

    Fix: Upgrade jQuery to at least version 3.5.0.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without this header, browsers might incorrectly handle file types.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: No referrer policy can expose users' page addresses when navigating away.

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

    Evidence: Referrer policy

  7. 7

    Server Version DisclosureLow

    Why it matters: Revealing server versions can help attackers find known vulnerabilities.

    Fix: Hide version information by modifying the server settings or disabling 'X-Powered-By'.

    Evidence: Software version disclosure

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Turning off unused features can limit what an injected script can do.

    Fix: Add the header 'Permissions-Policy: geolocation=(none), microphone=(none), camera=(none)'.

    Evidence: Permissions policy

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://cafebloom.ca/ → no strict-transport-security
    • https://cafebloom.ca/menu/ → no strict-transport-security
    • https://cafebloom.ca/events/ → no strict-transport-security
    • https://cafebloom.ca/contact-us/ → no strict-transport-security
    • https://cafebloom.ca/reservations/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 5 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://cafebloom.ca/ → no content-security-policy
    • https://cafebloom.ca/menu/ → no content-security-policy
    • https://cafebloom.ca/events/ → no content-security-policy
    • https://cafebloom.ca/contact-us/ → no content-security-policy
    • https://cafebloom.ca/reservations/ → 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://cafebloom.ca/ → no x-frame-options
    • https://cafebloom.ca/menu/ → no x-frame-options
    • https://cafebloom.ca/events/ → no x-frame-options
    • https://cafebloom.ca/contact-us/ → no x-frame-options
    • https://cafebloom.ca/reservations/ → 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://cafebloom.ca/ → no x-content-type-options
    • https://cafebloom.ca/menu/ → no x-content-type-options
    • https://cafebloom.ca/events/ → no x-content-type-options
    • https://cafebloom.ca/contact-us/ → no x-content-type-options
    • https://cafebloom.ca/reservations/ → 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://cafebloom.ca/ → no referrer-policy
    • https://cafebloom.ca/menu/ → no referrer-policy
    • https://cafebloom.ca/events/ → no referrer-policy
    • https://cafebloom.ca/contact-us/ → no referrer-policy
    • https://cafebloom.ca/reservations/ → 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://cafebloom.ca/ → no permissions-policy
    • https://cafebloom.ca/menu/ → no permissions-policy
    • https://cafebloom.ca/events/ → no permissions-policy
    • https://cafebloom.ca/contact-us/ → no permissions-policy
    • https://cafebloom.ca/reservations/ → no permissions-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: LiteSpeed (216 responses)
    • x-powered-by: PHP/7.4.33 (13 responses)
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.1.0 in https://cafebloom.ca/wp-content/themes/cafebloomwp/assets/js/jquery.countdown.m…: 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
  • 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.google.com (2 script tags)
5 checks passed, 2 not applicable
  • OKHTTPS

    All 5 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

  • Not applicableCookie flags

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

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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

Own cafebloom.ca?