Scanned sites / www.lilacbakery.com

SEO report for www.lilacbakery.com DR 5

The latest Site Spider scan of www.lilacbakery.com, with 1 scan on record. Each scan is at its own address, for example /domain/www-lilacbakery-com/2026-10-02-0417.

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

Latest scan

Scanned 2026-10-02 04:17:25 UTC, finished 2026-10-02 06:29:52 UTC. 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 27 checks found something to fix, led by heavy assets (13), title tags (209), meta descriptions (211); 11 checks passed. Most of the points went to heavy assets (−6), title tags (−5.3), meta descriptions (−4.3). 10 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
397
Assets fetched
542
Status
Completed
Checks with issues
6 of 27
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 sites1 issue
    1 destination answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
    −0.1 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 counts367 noted
    Internal link counts for 397 pages; 367 worth a look.
  • 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.
  • URL format1 noted
    1 of 397 page URLs are harder to read, share or cache than they need to be.
  • Canonicals185 noted
    185 of 397 pages have a canonical worth checking.
  • Robots directives397 noted
    397 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure127 noted
    127 of 212 pages could use the title, heading and snippet space better. 185 noindex or canonicalized pages excluded.
  • Image weight and alt length35 noted
    34 images over 100 KB; 1 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 397 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 939 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 397 pages; 375 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 63 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 site sits among all scanned sites

2909 sites, median 80%, average 79%

www.lilacbakery.com scores 83%, higher than 61% 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 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

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.

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.

Earlier scans of www.lilacbakery.com

No other scans of this site yet.

Sites scoring near www.lilacbakery.com

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