Scanned sites / www.felicecafe.ca / 2026-11-02-0156

www.felicecafe.ca scan from 2026-11-02 01:56:26 UTC DR 23

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

Scan 2026-11-02-0156

Scanned 2026-11-02 01:56:26 UTC, finished 2026-11-02 02:20:55 UTC. Found on page 1 of brave web search results

Site: https://www.felicecafe.ca/

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

73/ 100Needs work

On November 2, 2026 the Site Spider crawled 24 pages and 257 assets of www.felicecafe.ca, starting from https://www.felicecafe.ca/. It scored 73 out of 100, a result that needs work. 8 of 33 checks found something to fix, led by meta descriptions (19), title tags (10), thin content (9); 16 checks passed. Most of the points went to meta descriptions (−8), title tags (−5.3), thin content (−3.8). 9 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, 3 low and 2 info findings. See the security findings ↓

Pages crawled
24
Assets fetched
257
Status
Completed
Checks with issues
8 of 33
CoverageComplete crawl

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

  • Title tags10 issues
    10 of 19 pages have title issues.
    −5.3 points
  • Meta descriptions19 issues
    19 of 19 pages have meta description issues.
    −8 points
  • Headings5 issues
    5 of 19 pages have heading issues.
    −1.6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites38 noted
    0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 20 destinations checked.
  • Redirects5 issues
    6 redirecting URLs, 0 of them chained.
    −1.1 points
  • Non-200 responses8 noted
    8 URLs did not return a 2xx response. 5 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 19 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 102 image references have no alt attribute. 28 use an empty alt (decorative), which is fine.
  • Heavy assets5 issues
    5 assets larger than 500 KB among 257 fetched assets.
    −3 points
  • Orphan pages8 issues
    8 pages have no internal links pointing at them.
    −1.7 points
  • Sitemap coverage8 issues
    5 sitemaps listing 19 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 8 reachable only via the sitemap.
    −2.5 points
  • Internal link counts1 noted
    Internal link counts for 19 pages; 1 worth a look.
  • Thin content9 issues
    9 of 19 pages have fewer than 200 words.
    −3.8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 24 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 19 pages have a canonical worth checking.
  • Robots directives19 noted
    19 pages carry a robots directive; 0 carry none.
  • Anchor text8 noted
    8 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure5 noted
    5 of 19 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 anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 19 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    19 of 19 indexable pages carry structured data: BreadcrumbList (19), ListItem (19), WebSite (19), WebPage (16), ImageObject (7). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 14 pages with enough text to compare.
  • Soft 404sOK
    None of 19 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 positions4 noted
    4 of 11 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; 12 response headers recorded across 281 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 19 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling3 noted
    3 words an English dictionary does not know, on 2 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2536 sites, median 80%, average 78%

www.felicecafe.ca scores 73%, higher than 25% of the 2536 scanned sites. See the full ranking.

0601190%: 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%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 5 sites52%: 8 sites53%: 8 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 37 sites67%: 39 sites68%: 38 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 72 sites73%: 75 sites74%: 75 sites75%: 76 sites76%: 91 sites77%: 101 sites78%: 115 sites79%: 101 sites80%: 119 sites81%: 112 sites82%: 115 sites83%: 116 sites84%: 118 sites85%: 95 sites86%: 77 sites87%: 85 sites88%: 64 sites89%: 70 sites90%: 46 sites91%: 55 sites92%: 40 sites93%: 28 sites94%: 20 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites73% 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

The site has several SEO issues needing attention. The most critical involve meta descriptions, title tags, and redirects. Addressing these will improve visibility and user experience.

  1. 1

    Fix Title Tag Issues

    Why: 10 pages have title issues, which can affect visibility in search results.

    How: Shorten titles to under 60 characters to ensure they display fully in search results.

    Evidence: 2 pages share the title "Coffee Beans Archives - Felice Cafe", which usually means one template writes it for all of them.

    2 pages affected

    Depends on: If these pages really are the same content, the duplicate title is a symptom: canonicalise them to one URL instead.

    Checks: titles

  2. 2

    Add Missing Meta Descriptions

    Why: 19 pages lack meta descriptions, impacting click-through rates.

    How: Create unique, concise meta descriptions for all pages, focusing on relevant keywords.

    Checks: meta-descriptions

  3. 3

    Address Non-200 Responses

    Why: 8 URLs returned non-200 responses which may confuse search engines.

    How: Check and correct the status of each URL, ensuring they return a 200 status.

    Checks: status-codes

  4. 4

    Reduce Heavy Assets

    Why: 5 assets are larger than 500 KB, slowing down page loads.

    How: Optimize or compress heavy assets to enhance load times.

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

    19 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

  5. 5

    Fix Orphan Pages

    Why: 8 pages lack internal links, making them hard to discover.

    How: Add internal links to these pages from relevant content to improve navigation.

    Checks: orphan-pages

  6. 6

    Improve Thin Content

    Why: 9 pages have less than 200 words and may not provide sufficient value.

    How: Enhance these pages with additional relevant text to improve information quality.

    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 www.felicecafe.ca has several security issues that need your attention. Key improvements include implementing HTTP Strict Transport Security, Content Security Policy, and Clickjacking protection, as they are crucial for protecting users from website attacks. Additionally, there are outdated JavaScript libraries which should be upgraded immediately.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users could be vulnerable to interception when visiting the site via HTTP.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows potential malicious scripts to load without restrictions.

    Fix: Implement a Content Security Policy header like 'Content-Security-Policy: default-src 'self';' across all pages.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without clickjacking protection, users can be tricked into actions on the site.

    Fix: Add the header 'X-Frame-Options: DENY' to every HTML page.

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibrariesMedium

    Why it matters: Vulnerable libraries can expose the site to potential attacks.

    Fix: Upgrade jQuery to at least version 3.5.0 and Bootstrap to at least version 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without MIME type options, browsers may process files in an unintended manner.

    Fix: Add the header 'X-Content-Type-Options: nosniff' to every HTML page.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Not using a Referrer-Policy may expose complete URL details when users navigate away.

    Fix: Implement 'Referrer-Policy: no-referrer' as a header for all pages.

    Evidence: Referrer policy

  7. 7

    Third-Party Scripts without SRILow

    Why it matters: Using external scripts without Subresource Integrity can lead to security risks.

    Fix: Consider adding 'integrity' attributes or implement a strict Content Security Policy for external scripts.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: This lack might allow unnecessary access to browser features that aren't needed.

    Fix: Add 'Permissions-Policy: camera=(), microphone=(), geolocation=()' as a header to pages.

    Evidence: Permissions policy

  9. 9

    Sensitive paths in robots.txtInfo

    Why it matters: Public listing of sensitive directories could aid malicious users.

    Fix: Restrict access control measures instead of relying solely on 'robots.txt'.

    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.felicecafe.ca/ → no strict-transport-security
    • https://www.felicecafe.ca/cafe/ → no strict-transport-security
    • https://www.felicecafe.ca/cafe/menu/ → no strict-transport-security
    • https://www.felicecafe.ca/market/ → no strict-transport-security
    • https://www.felicecafe.ca/noir/ → no strict-transport-security
    • https://www.felicecafe.ca/gives-back/ → no strict-transport-security
    • https://www.felicecafe.ca/space-rentals/ → no strict-transport-security
    • https://www.felicecafe.ca/market/market-vendor-application/ → no strict-transport-security
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no strict-transport-security
    • https://www.felicecafe.ca/entrepreneur/ → no strict-transport-security
    • https://www.felicecafe.ca/subscribe-part-two/ → no strict-transport-security
    • https://www.felicecafe.ca/subscribe/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 19 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.felicecafe.ca/ → no content-security-policy
    • https://www.felicecafe.ca/cafe/ → no content-security-policy
    • https://www.felicecafe.ca/cafe/menu/ → no content-security-policy
    • https://www.felicecafe.ca/market/ → no content-security-policy
    • https://www.felicecafe.ca/noir/ → no content-security-policy
    • https://www.felicecafe.ca/gives-back/ → no content-security-policy
    • https://www.felicecafe.ca/space-rentals/ → no content-security-policy
    • https://www.felicecafe.ca/market/market-vendor-application/ → no content-security-policy
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no content-security-policy
    • https://www.felicecafe.ca/entrepreneur/ → no content-security-policy
    • https://www.felicecafe.ca/subscribe-part-two/ → no content-security-policy
    • https://www.felicecafe.ca/subscribe/ → 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.felicecafe.ca/ → no x-frame-options
    • https://www.felicecafe.ca/cafe/ → no x-frame-options
    • https://www.felicecafe.ca/cafe/menu/ → no x-frame-options
    • https://www.felicecafe.ca/market/ → no x-frame-options
    • https://www.felicecafe.ca/noir/ → no x-frame-options
    • https://www.felicecafe.ca/gives-back/ → no x-frame-options
    • https://www.felicecafe.ca/space-rentals/ → no x-frame-options
    • https://www.felicecafe.ca/market/market-vendor-application/ → no x-frame-options
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no x-frame-options
    • https://www.felicecafe.ca/entrepreneur/ → no x-frame-options
    • https://www.felicecafe.ca/subscribe-part-two/ → no x-frame-options
    • https://www.felicecafe.ca/subscribe/ → 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.felicecafe.ca/ → no x-content-type-options
    • https://www.felicecafe.ca/cafe/ → no x-content-type-options
    • https://www.felicecafe.ca/cafe/menu/ → no x-content-type-options
    • https://www.felicecafe.ca/market/ → no x-content-type-options
    • https://www.felicecafe.ca/noir/ → no x-content-type-options
    • https://www.felicecafe.ca/gives-back/ → no x-content-type-options
    • https://www.felicecafe.ca/space-rentals/ → no x-content-type-options
    • https://www.felicecafe.ca/market/market-vendor-application/ → no x-content-type-options
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no x-content-type-options
    • https://www.felicecafe.ca/entrepreneur/ → no x-content-type-options
    • https://www.felicecafe.ca/subscribe-part-two/ → no x-content-type-options
    • https://www.felicecafe.ca/subscribe/ → 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.felicecafe.ca/ → no referrer-policy
    • https://www.felicecafe.ca/cafe/ → no referrer-policy
    • https://www.felicecafe.ca/cafe/menu/ → no referrer-policy
    • https://www.felicecafe.ca/market/ → no referrer-policy
    • https://www.felicecafe.ca/noir/ → no referrer-policy
    • https://www.felicecafe.ca/gives-back/ → no referrer-policy
    • https://www.felicecafe.ca/space-rentals/ → no referrer-policy
    • https://www.felicecafe.ca/market/market-vendor-application/ → no referrer-policy
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no referrer-policy
    • https://www.felicecafe.ca/entrepreneur/ → no referrer-policy
    • https://www.felicecafe.ca/subscribe-part-two/ → no referrer-policy
    • https://www.felicecafe.ca/subscribe/ → 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.felicecafe.ca/ → no permissions-policy
    • https://www.felicecafe.ca/cafe/ → no permissions-policy
    • https://www.felicecafe.ca/cafe/menu/ → no permissions-policy
    • https://www.felicecafe.ca/market/ → no permissions-policy
    • https://www.felicecafe.ca/noir/ → no permissions-policy
    • https://www.felicecafe.ca/gives-back/ → no permissions-policy
    • https://www.felicecafe.ca/space-rentals/ → no permissions-policy
    • https://www.felicecafe.ca/market/market-vendor-application/ → no permissions-policy
    • https://www.felicecafe.ca/cafe/food-vendor-application/ → no permissions-policy
    • https://www.felicecafe.ca/entrepreneur/ → no permissions-policy
    • https://www.felicecafe.ca/subscribe-part-two/ → no permissions-policy
    • https://www.felicecafe.ca/subscribe/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 2.2.4, Bootstrap 3.3.5. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 2.2.4 in https://www.felicecafe.ca/wp-content/themes/interiart/js/jquery-2.2.4.min.js?ve…: 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
    • Bootstrap 3.3.5 in https://www.felicecafe.ca/wp-content/themes/interiart/js/bootstrap.min.js?ver=7…: CVE-2016-10735, CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 3.4.1
  • 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.)

    • static.klaviyo.com (19 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/
6 checks passed, 1 not applicable
  • OKHTTPS

    All 19 crawled pages 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

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

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

Own www.felicecafe.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.felicecafe.ca. Removal needs no account and no proof of purchase.