Scanned sites / www.lilacbakery.com / 2026-10-02-0417

www.lilacbakery.com scan from 10/2/2026, 4:17:25 AM

Scan 2026-10-02-0417

Scanned 10/2/2026, 4:17:25 AM, finished 10/2/2026, 6:29:52 AM. Found on page 4 of brave web search results

Site: https://www.lilacbakery.com/

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

83/ 100Good

On October 2, 2026 the Site Spider crawled 397 pages and 542 assets of www.lilacbakery.com, starting from https://www.lilacbakery.com/. It scored 83 out of 100, a good result. 6 of 16 checks found something to fix, led by heavy assets (13), title tags (209), meta descriptions (211); 7 checks passed. Most of the points went to heavy assets (−6), title tags (−5.3), meta descriptions (−4.3). 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: Medium4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
397
Assets fetched
542
Status
Completed
Checks with issues
6 of 16
CoverageComplete crawl

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

  • Title tags209 issues
    209 of 212 pages have title issues. 185 noindex or canonicalized pages excluded.
    −5.3 points
  • Meta descriptions211 issues
    211 of 212 pages have meta description issues. 185 noindex or canonicalized pages excluded.
    −4.3 points
  • Headings41 issues
    41 of 212 pages have heading issues. 185 noindex or canonicalized pages excluded.
    −0.6 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites2 issues
    2 destinations answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
    −0.2 points
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses2 noted
    2 URLs 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 212 indexable pages have indexability warnings. 185 pages noindex by design.
  • Image alt textOK
    0 of 3701 image references have no alt attribute. 490 use an empty alt (decorative), which is fine.
  • Heavy assets13 issues
    13 assets larger than 500 KB among 542 fetched assets. 3 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage40 issues
    3 sitemaps listing 172 URLs: 40 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −0.6 points
  • Internal link countsOK
    Internal link counts for 397 pages.
  • Thin contentOK
    0 of 212 pages have fewer than 200 words. 185 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1750 sites, median 80%, average 79%

www.lilacbakery.com scores 83%, higher than 63% of the 1750 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%: 1 site40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 16 sites64%: 12 sites65%: 20 sites66%: 19 sites67%: 33 sites68%: 27 sites69%: 25 sites70%: 39 sites71%: 37 sites72%: 49 sites73%: 49 sites74%: 48 sites75%: 56 sites76%: 71 sites77%: 62 sites78%: 83 sites79%: 60 sites80%: 85 sites81%: 102 sites82%: 82 sites83%: 81 sites84%: 77 sites85%: 59 sites86%: 64 sites87%: 55 sites88%: 60 sites89%: 53 sites90%: 32 sites91%: 35 sites92%: 24 sites93%: 14 sites94%: 12 sites95%: 9 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites83% 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 room for improvement, particularly in title tags, meta descriptions, and heading structures. Focus on completing these for better SEO performance.

  1. 1

    Fix Title Tag Issues

    Why: 75 pages share titles which can harm SEO.

    How: Assign unique titles to these pages, reflecting actual content.

    Checks: titles

  2. 2

    Add Missing Meta Descriptions

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

    How: Create concise, relevant meta descriptions for each page.

    Checks: meta-descriptions

  3. 3

    Introduce H1 Headings

    Why: 41 pages are missing H1 tags, affecting content clarity.

    How: Ensure each page has a unique H1 that summarizes its content.

    Checks: headings

  4. 4

    Address Asset Size Issues

    Why: Several images exceed 500 KB, slowing load times.

    How: Optimize images for smaller file sizes without losing quality.

    Checks: heavy-assets

  5. 5

    Resolve Redirects

    Why: There are 1 redirecting URL that could confuse users.

    How: Update links to point directly to the final destination.

    Checks: redirects

  6. 6

    Update Sitemap Coverage

    Why: 40 pages are missing from your sitemap, hindering discovery.

    How: Ensure all relevant pages are included in the sitemap.

    Checks: sitemap-coverage

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 lacks several important security headers and uses a vulnerable JavaScript library. Implementing these fixes will enhance security against various attacks and vulnerabilities. Priority should be given to enabling HTTP Strict Transport Security and setting a Content Security Policy.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be vulnerable to man-in-the-middle attacks when accessing the site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: The absence of CSP allows potentially malicious scripts to run on your site without restriction.

    Fix: Implement a CSP header, e.g., `Content-Security-Policy: default-src 'self';` to control resource loading.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Not using this header leaves the site vulnerable to clickjacking attacks.

    Fix: Add `X-Frame-Options: DENY` or `SAMEORIGIN` to prevent framing.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript Library DetectedMedium

    Why it matters: The use of jQuery 3.1.2 contains known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to at least version 3.5.0 to resolve known issues.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers might incorrectly interpret files as scripts, leading to security risks.

    Fix: Add `X-Content-Type-Options: nosniff` to all responses.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of this policy exposes your site's full URLs to third-party sites upon navigation.

    Fix: Implement `Referrer-Policy: no-referrer` to limit what is shared.

    Evidence: Referrer policy

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: Not using a Permissions-Policy allows potentially harmful injected scripts to access sensitive features.

    Fix: Add `Permissions-Policy: geolocation=(), microphone=(), camera=()` to control feature access.

    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.lilacbakery.com/ → no strict-transport-security
    • https://www.lilacbakery.com/menu/ → no strict-transport-security
    • https://www.lilacbakery.com/catering/ → no strict-transport-security
    • https://www.lilacbakery.com/wedding-cakes/ → no strict-transport-security
    • https://www.lilacbakery.com/custom-baking/ → no strict-transport-security
    • https://www.lilacbakery.com/corporate/ → no strict-transport-security
    • https://www.lilacbakery.com/wholesale/ → no strict-transport-security
    • https://www.lilacbakery.com/about/ → no strict-transport-security
    • https://www.lilacbakery.com/press/ → no strict-transport-security
    • https://www.lilacbakery.com/news/ → no strict-transport-security
    • https://www.lilacbakery.com/contact/ → no strict-transport-security
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 397 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.lilacbakery.com/ → no content-security-policy
    • https://www.lilacbakery.com/menu/ → no content-security-policy
    • https://www.lilacbakery.com/catering/ → no content-security-policy
    • https://www.lilacbakery.com/wedding-cakes/ → no content-security-policy
    • https://www.lilacbakery.com/custom-baking/ → no content-security-policy
    • https://www.lilacbakery.com/corporate/ → no content-security-policy
    • https://www.lilacbakery.com/wholesale/ → no content-security-policy
    • https://www.lilacbakery.com/about/ → no content-security-policy
    • https://www.lilacbakery.com/press/ → no content-security-policy
    • https://www.lilacbakery.com/news/ → no content-security-policy
    • https://www.lilacbakery.com/contact/ → no content-security-policy
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → 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.lilacbakery.com/ → no x-frame-options
    • https://www.lilacbakery.com/menu/ → no x-frame-options
    • https://www.lilacbakery.com/catering/ → no x-frame-options
    • https://www.lilacbakery.com/wedding-cakes/ → no x-frame-options
    • https://www.lilacbakery.com/custom-baking/ → no x-frame-options
    • https://www.lilacbakery.com/corporate/ → no x-frame-options
    • https://www.lilacbakery.com/wholesale/ → no x-frame-options
    • https://www.lilacbakery.com/about/ → no x-frame-options
    • https://www.lilacbakery.com/press/ → no x-frame-options
    • https://www.lilacbakery.com/news/ → no x-frame-options
    • https://www.lilacbakery.com/contact/ → no x-frame-options
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → 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.lilacbakery.com/ → no x-content-type-options
    • https://www.lilacbakery.com/menu/ → no x-content-type-options
    • https://www.lilacbakery.com/catering/ → no x-content-type-options
    • https://www.lilacbakery.com/wedding-cakes/ → no x-content-type-options
    • https://www.lilacbakery.com/custom-baking/ → no x-content-type-options
    • https://www.lilacbakery.com/corporate/ → no x-content-type-options
    • https://www.lilacbakery.com/wholesale/ → no x-content-type-options
    • https://www.lilacbakery.com/about/ → no x-content-type-options
    • https://www.lilacbakery.com/press/ → no x-content-type-options
    • https://www.lilacbakery.com/news/ → no x-content-type-options
    • https://www.lilacbakery.com/contact/ → no x-content-type-options
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → 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.lilacbakery.com/ → no referrer-policy
    • https://www.lilacbakery.com/menu/ → no referrer-policy
    • https://www.lilacbakery.com/catering/ → no referrer-policy
    • https://www.lilacbakery.com/wedding-cakes/ → no referrer-policy
    • https://www.lilacbakery.com/custom-baking/ → no referrer-policy
    • https://www.lilacbakery.com/corporate/ → no referrer-policy
    • https://www.lilacbakery.com/wholesale/ → no referrer-policy
    • https://www.lilacbakery.com/about/ → no referrer-policy
    • https://www.lilacbakery.com/press/ → no referrer-policy
    • https://www.lilacbakery.com/news/ → no referrer-policy
    • https://www.lilacbakery.com/contact/ → no referrer-policy
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → 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.lilacbakery.com/ → no permissions-policy
    • https://www.lilacbakery.com/menu/ → no permissions-policy
    • https://www.lilacbakery.com/catering/ → no permissions-policy
    • https://www.lilacbakery.com/wedding-cakes/ → no permissions-policy
    • https://www.lilacbakery.com/custom-baking/ → no permissions-policy
    • https://www.lilacbakery.com/corporate/ → no permissions-policy
    • https://www.lilacbakery.com/wholesale/ → no permissions-policy
    • https://www.lilacbakery.com/about/ → no permissions-policy
    • https://www.lilacbakery.com/press/ → no permissions-policy
    • https://www.lilacbakery.com/news/ → no permissions-policy
    • https://www.lilacbakery.com/contact/ → no permissions-policy
    • https://www.lilacbakery.com/national-day-for-truth-and-reconciliation-3/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 3.1.2 in https://www.lilacbakery.com/wp-content/plugins/gravityforms/js/placeholders.jqu…: 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.googletagmanager.com (40 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 397 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

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

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

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