Scanned sites / www.cafecarlo.com / 2026-10-02-0051

www.cafecarlo.com scan from 10/2/2026, 12:51:29 AM

Scan 2026-10-02-0051

Scanned 10/2/2026, 12:51:29 AM, finished 10/2/2026, 1:34:48 AM. Found on page 1 of brave web search results

Site: https://www.cafecarlo.com/

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

82/ 100Good

On October 2, 2026 the Site Spider crawled 13 pages and 273 assets of www.cafecarlo.com, starting from https://www.cafecarlo.com/. It scored 82 out of 100, a good result. 7 of 16 checks found something to fix, led by meta descriptions (12), heavy assets (6), title tags (3); 6 checks passed. Most of the points went to meta descriptions (−8), heavy assets (−3.6), title tags (−2.5). 3 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: Medium2 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
13
Assets fetched
273
Status
Completed
Checks with issues
7 of 16
CoverageComplete crawl

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

  • Title tags3 issues
    3 of 12 pages have title issues.
    −2.5 points
  • Meta descriptions12 issues
    12 of 12 pages have meta description issues.
    −8 points
  • Headings2 issues
    2 of 12 pages have heading issues.
    −1 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites38 noted
    0 destinations answered with an error, 5 could not be determined (timeouts, rate limits or refusals), of 10 destinations checked.
  • Redirects1 issue
    2 redirecting URLs, 0 of them chained.
    −0.3 points
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 1 of them is a page, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 12 indexable pages have indexability warnings.
  • Image alt text4 issues
    4 of 83 image references have no alt attribute. 78 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets6 issues
    6 assets larger than 500 KB among 273 fetched assets.
    −3.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    2 sitemaps listing 12 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Internal link countsOK
    Internal link counts for 12 pages.
  • Thin content3 issues
    3 of 12 pages have fewer than 200 words.
    −2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1688 sites, median 80%, average 79%

www.cafecarlo.com scores 82%, higher than 58% of the 1688 scanned sites. See the full ranking.

0511020%: 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%: 2 sites36%: 1 site37%: 2 sites38%: 2 sites39%: 0 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 3 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 19 sites66%: 19 sites67%: 32 sites68%: 26 sites69%: 24 sites70%: 38 sites71%: 37 sites72%: 48 sites73%: 46 sites74%: 47 sites75%: 53 sites76%: 66 sites77%: 60 sites78%: 78 sites79%: 61 sites80%: 82 sites81%: 102 sites82%: 80 sites83%: 78 sites84%: 73 sites85%: 59 sites86%: 60 sites87%: 54 sites88%: 59 sites89%: 49 sites90%: 32 sites91%: 34 sites92%: 22 sites93%: 11 sites94%: 12 sites95%: 7 sites96%: 7 sites97%: 7 sites98%: 2 sites99%: 2 sites100%: 54 sites82% 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 a few areas for improvement, mainly involving redirects, titles, meta descriptions, headings, and thin content. Prioritize addressing these issues for better SEO performance.

  1. 1

    Fix Redirects

    Why: Improving redirects enhances user experience and SEO.

    How: Update links to avoid redirects, changing 'https://www.cafecarlo.com/reservations' to 'https://www.cafecarlo.com/reservations/'.

    Checks: redirects

  2. 2

    Optimize Title Tags

    Why: Unique titles improve click-through rates and SEO.

    How: Revise titles for 3 affected pages to eliminate duplicates and make them compelling.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: Proper meta descriptions boost visibility and click rates.

    How: Create unique meta descriptions for 11 pages and add one for the missing one.

    Checks: meta-descriptions

  4. 4

    Add H1 Tags

    Why: H1 tags are crucial for your page structure and SEO.

    How: Ensure each page has one H1 tag that summarizes the page content.

    Checks: headings

  5. 5

    Enhance Thin Content

    Why: Adding valuable content improves SEO rankings.

    How: Increase word count on 3 thin-content pages to at least 200 words.

    Checks: thin-content

  6. 6

    Optimize Heavy Assets

    Why: Reducing asset sizes speeds up page load times.

    How: Shrink or eliminate unneeded heavy assets, focusing on scripts and images.

    Checks: heavy-assets

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 needs improved security headers to protect user data and prevent attacks. Key areas requiring attention include HTTP Strict Transport Security, Content Security Policy, and related protections. Implementing these will significantly enhance your site’s security.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, visitors can be intercepted on their first HTTP request.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Lack of CSP allows unrestricted loading of scripts and styles.

    Fix: Add a Content Security Policy header, e.g., `Content-Security-Policy: default-src 'self'; script-src 'self' www.googletagmanager.com www.google.com;`.

    Evidence: Content Security Policy

  3. 3

    Missing X-Content-Type-Options HeaderLow

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

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

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: No referrer-policy means full address information is shared with third-party sites.

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

    Evidence: Referrer policy

  5. 5

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Scripts from external domains can be compromised, affecting site security.

    Fix: Implement a Content-Security-Policy that specifies trusted domains and consider adding Subresource Integrity where supported.

    Evidence: Third-party scripts

  6. 6

    Missing Permissions Policy HeaderInfo

    Why it matters: This header can prevent unauthorized access to browser features.

    Fix: Add the header: `Permissions-Policy: none` or set according to site usage.

    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://www.cafecarlo.com/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/dinner/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/lunch/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/dessert/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/wine/ → no strict-transport-security
    • https://www.cafecarlo.com/our-menu/cocktails/ → no strict-transport-security
    • https://www.cafecarlo.com/reservations/ → no strict-transport-security
    • https://www.cafecarlo.com/faq/ → no strict-transport-security
    • https://www.cafecarlo.com/our-story/ → no strict-transport-security
    • https://www.cafecarlo.com/contact/ → no strict-transport-security
    • https://www.cafecarlo.com/work-with-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 12 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.cafecarlo.com/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/dinner/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/lunch/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/dessert/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/wine/ → no content-security-policy
    • https://www.cafecarlo.com/our-menu/cocktails/ → no content-security-policy
    • https://www.cafecarlo.com/reservations/ → no content-security-policy
    • https://www.cafecarlo.com/faq/ → no content-security-policy
    • https://www.cafecarlo.com/our-story/ → no content-security-policy
    • https://www.cafecarlo.com/contact/ → no content-security-policy
    • https://www.cafecarlo.com/work-with-us/ → no content-security-policy
  • 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.cafecarlo.com/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/dinner/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/lunch/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/dessert/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/wine/ → no x-content-type-options
    • https://www.cafecarlo.com/our-menu/cocktails/ → no x-content-type-options
    • https://www.cafecarlo.com/reservations/ → no x-content-type-options
    • https://www.cafecarlo.com/faq/ → no x-content-type-options
    • https://www.cafecarlo.com/our-story/ → no x-content-type-options
    • https://www.cafecarlo.com/contact/ → no x-content-type-options
    • https://www.cafecarlo.com/work-with-us/ → 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.cafecarlo.com/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/dinner/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/lunch/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/dessert/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/wine/ → no referrer-policy
    • https://www.cafecarlo.com/our-menu/cocktails/ → no referrer-policy
    • https://www.cafecarlo.com/reservations/ → no referrer-policy
    • https://www.cafecarlo.com/faq/ → no referrer-policy
    • https://www.cafecarlo.com/our-story/ → no referrer-policy
    • https://www.cafecarlo.com/contact/ → no referrer-policy
    • https://www.cafecarlo.com/work-with-us/ → 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.cafecarlo.com/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/dinner/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/lunch/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/dessert/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/wine/ → no permissions-policy
    • https://www.cafecarlo.com/our-menu/cocktails/ → no permissions-policy
    • https://www.cafecarlo.com/reservations/ → no permissions-policy
    • https://www.cafecarlo.com/faq/ → no permissions-policy
    • https://www.cafecarlo.com/our-story/ → no permissions-policy
    • https://www.cafecarlo.com/contact/ → no permissions-policy
    • https://www.cafecarlo.com/work-with-us/ → no permissions-policy
  • NoteThird-party scripts

    Scripts run from 2 other domains 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.googletagmanager.com (12 script tags)
    • www.google.com (2 script tags)
9 checks passed, 1 not applicable
  • OKHTTPS

    All 12 crawled pages were served over HTTPS.

  • OKClickjacking protection

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

  • 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

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

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

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

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

Own www.cafecarlo.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.cafecarlo.com. Removal needs no account and no proof of purchase.
www.cafecarlo.com scan 2026-10-02-0051 | DIY SEO Hub