Scanned sites / www.felicecafe.ca / 2026-09-10-1228

www.felicecafe.ca scan from 2026-09-10 12:28:12 UTC DR 23

A newer scan exists. See the latest report for www.felicecafe.ca.

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

Scan 2026-09-10-1228

Scanned 2026-09-10 12:28:12 UTC, finished 2026-09-10 18:02:47 UTC

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 September 10, 2026 the Site Spider crawled 21 pages and 365 assets of www.felicecafe.ca, starting from https://www.felicecafe.ca/. It scored 73 out of 100, a result that needs work. 8 of 27 checks found something to fix, led by meta descriptions (16), title tags (8), heavy assets (7); 11 checks passed. Most of the points went to meta descriptions (−8), title tags (−5), heavy assets (−4.2). 8 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
21
Assets fetched
365
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

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

  • Title tags8 issues
    8 of 16 pages have title issues.
    −5 points
  • Meta descriptions16 issues
    16 of 16 pages have meta description issues.
    −8 points
  • Headings5 issues
    5 of 16 pages have heading issues.
    −1.9 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites55 noted
    0 destinations answered with an error, 10 could not be determined (timeouts, rate limits or refusals), of 19 destinations checked.
  • Redirects5 issues
    6 redirecting URLs, 0 of them chained.
    −1.3 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 16 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 91 image references have no alt attribute. 28 use an empty alt (decorative), which is fine.
  • Heavy assets7 issues
    7 assets larger than 500 KB among 365 fetched assets.
    −4.2 points
  • Orphan pages5 issues
    5 pages have no internal links pointing at them.
    −1.3 points
  • Sitemap coverage5 issues
    5 sitemaps listing 16 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 5 reachable only via the sitemap.
    −1.9 points
  • Internal link counts1 noted
    Internal link counts for 16 pages; 1 worth a look.
  • Thin content7 issues
    7 of 16 pages have fewer than 200 words.
    −3.5 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 21 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 16 pages have a canonical worth checking.
  • Robots directives16 noted
    16 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 16 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 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 16 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; 12 response headers recorded across 386 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 16 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 54 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

2316 sites, median 79%, average 78%

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

0581150%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 86 sites77%: 92 sites78%: 106 sites79%: 86 sites80%: 105 sites81%: 105 sites82%: 115 sites83%: 99 sites84%: 107 sites85%: 85 sites86%: 70 sites87%: 74 sites88%: 59 sites89%: 61 sites90%: 35 sites91%: 44 sites92%: 38 sites93%: 22 sites94%: 16 sites95%: 11 sites96%: 9 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 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

Written from an earlier version of the analysis. 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 technical SEO issues that need addressing, especially with redirects, title tags, and meta descriptions. Prioritizing these will improve overall site health significantly.

  1. 1

    Fix Redirects and Non-200 Responses

    Why: Redirects can confuse search engines and users. Ensuring all URLs return a 200 response enhances crawlability.

    How: Change the redirected URLs to their final forms to eliminate redirects. Update invalid URLs.

    Checks: redirects, status-codes

  2. 2

    Optimize Title Tags

    Why: Titles longer than 60 characters may truncate in search results, impacting click-through rates.

    How: Revise titles of affected pages to be concise, keeping them under 60 characters.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: Meta descriptions guide users and can influence click-through rates in search results.

    How: Add missing meta descriptions and shorten any exceeding 160 characters.

    Checks: meta-descriptions

  4. 4

    Resolve Heading Issues

    Why: Multiple H1s can confuse search engines about page structure. Missing H1s affect SEO.

    How: Ensure each page has one unique H1 and correct multiple H1 issues.

    Checks: headings

  5. 5

    Link Orphan Pages Internally

    Why: Orphan pages have no internal links, making them harder to find for users and search engines.

    How: Create internal links to the orphan pages from related content on the website.

    Checks: orphan-pages

  6. 6

    Address Thin Content

    Why: Pages with less than 200 words may not provide enough value for users or search engines.

    How: Expand content on thin pages to ensure each has at least 200 words and adds value.

    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 lacks important security headers and uses outdated libraries that may expose it to risks. Implementing proper headers will enhance protection against various attacks. Upgrading the libraries will address known vulnerabilities.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first request if they type the address without HTTPS.

    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 loading scripts from any location, increasing the risk of cross-site scripting attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this header, pages can be embedded in frames which could lead to clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Outdated JavaScript LibrariesMedium

    Why it matters: Using outdated libraries like jQuery and Bootstrap increases vulnerability to known exploits.

    Fix: Upgrade jQuery to 3.5.0 and Bootstrap to 3.4.1.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may incorrectly interpret files as executable scripts.

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

    Evidence: MIME sniffing protection

  6. 6

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from other domains can be altered, introducing risks to the site.

    Fix: Consider implementing a Content-Security-Policy that restricts these scripts or use Subresource Integrity.

    Evidence: Third-party scripts

  7. 7

    Sensitive Paths in robots.txtInfo

    Why it matters: The robots.txt file discloses paths that may be sensitive, which could aid attackers.

    Fix: Restrict access to sensitive paths through proper server configurations 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 16 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
  • 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 (16 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, 3 not applicable
  • OKHTTPS

    All 16 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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.