Scanned sites / frillylilly.ca / 2026-09-15-0738

frillylilly.ca scan from 2026-09-15 07:38:05 UTC DR 26

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

Scan 2026-09-15-0738

Scanned 2026-09-15 07:38:05 UTC, finished 2026-09-15 08:08:35 UTC. Found with openstreetmap overpass

Site: https://frillylilly.ca/

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

68/ 100Needs work

On September 15, 2026 the Site Spider crawled 382 pages and 948 assets of frillylilly.ca, starting from https://frillylilly.ca/. It scored 68 out of 100, a result that needs work. 14 of 27 checks found something to fix, led by meta descriptions (221), heavy assets (210), broken links (59); 3 checks passed. Most of the points went to meta descriptions (−6.4), heavy assets (−6), broken links (−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: Medium3 medium, 3 low and 1 info findings. See the security findings ↓

Pages crawled
382
Assets fetched
948
Status
Completed
Checks with issues
14 of 27
CoverageComplete crawl

1,330 of 1,479 discovered URLs were fetched, 149 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 135 link destinations on other sites were checked.

  • Title tags60 issues
    60 of 270 pages have title issues. 5 noindex or canonicalized pages excluded.
    −2.2 points
  • Meta descriptions221 issues
    221 of 270 pages have meta description issues. 5 noindex or canonicalized pages excluded.
    −6.4 points
  • Headings35 issues
    35 of 270 pages have heading issues. 5 noindex or canonicalized pages excluded.
    −0.8 points
  • Broken links59 issues
    350 internal links point at 59 broken URLs.
    −4.3 points
  • Links to other sites31 issues
    31 destinations answered with an error, 53 could not be determined (timeouts, rate limits or refusals), of 134 destinations checked.
    −4 points
  • Redirects46 issues
    48 redirecting URLs, 0 of them chained.
    −0.7 points
  • Non-200 responses60 issues
    140 URLs did not return a 2xx response. 107 of them are pages, 60 with an error status; the rest are assets or redirects.
    −2.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 270 indexable pages have indexability warnings. 5 pages noindex by design. 2 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −0.1 points
  • Image alt text42 issues
    42 of 1851 image references have no alt attribute. 258 use an empty alt (decorative), which is fine.
    −0.1 points
  • Heavy assets210 issues
    210 assets larger than 500 KB among 948 fetched assets.
    −6 points
  • Orphan pages20 issues
    20 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage121 issues
    10 sitemaps listing 180 URLs: 96 crawled pages missing, 4 listed URLs broken or redirecting, 19 reachable only via the sitemap.
    −2.6 points
  • Internal link counts104 noted
    Internal link counts for 275 pages; 104 worth a look.
  • Thin content6 issues
    6 of 270 pages have fewer than 200 words. 5 noindex or canonicalized pages excluded.
    −0.2 points
  • Duplicate content59 issues
    1 group of pages with identical HTML.
    −1.7 points
  • URL format26 noted
    26 of 382 page URLs are harder to read, share or cache than they need to be.
  • Canonicals3 noted
    3 of 275 pages have a canonical worth checking.
  • Robots directives275 noted
    275 pages carry a robots directive; 0 carry none.
  • Anchor text182 noted
    182 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure101 noted
    101 of 270 pages could use the title, heading and snippet space better. 5 noindex or canonicalized pages excluded.
  • Image weight and alt length122 noted
    122 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • 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 404s11 noted
    11 pages answer 200 but say they are not there.
  • 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; 14 response headers recorded across 1330 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 275 pages; 196 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 62 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

2873 sites, median 80%, average 79%

frillylilly.ca scores 68%, higher than 13% of the 2873 scanned sites. See the full ranking.

0751500%: 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%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites68% 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 significant issues, particularly with broken links and meta descriptions. Addressing these will improve user experience and SEO performance significantly.

  1. 1

    Fix Broken Links

    Why: 350 internal links are broken; fixing these enhances user experience and SEO.

    How: Identify the URLs in the crawl report and update or remove the broken links.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 140 URLs are not returning a valid response, impacting SEO.

    How: Replace or repair these URLs so they return a 2xx response.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 60 title tags have issues which affects click-through rates.

    How: Update titles to be unique, relevant, and between 30-60 characters.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 220 pages have meta description issues affecting search visibility.

    How: Write unique meta descriptions for each page, ideally between 50-160 characters.

    Checks: meta-descriptions

  5. 5

    Address Heading Issues

    Why: 35 pages have heading issues that may confuse search engines.

    How: Ensure each page has one H1 tag and appropriately used H2/H3 tags.

    Checks: headings

  6. 6

    Link Orphan Pages

    Why: 20 pages are orphaned; they should be linked for discoverability.

    How: Add internal links from relevant pages to these orphaned content sections.

    Checks: orphan-pages

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 has several important security issues, including missing protections against clickjacking and MIME sniffing. Additionally, HTTP Strict Transport Security is not enabled, which exposes users to interception on their first connection. Addressing these issues will significantly increase the security of your site.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing your web address without https:// can be intercepted.

    Fix: Add the following header to each page: Strict-Transport-Security: max-age=63072000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Pages without X-Frame-Options can be embedded in a frame on another site, risking clickjacking attacks.

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

    Evidence: Clickjacking protection

  3. 3

    Vulnerable jQuery LibraryMedium

    Why it matters: Using jQuery 3.0.2 exposes the site to known vulnerabilities that may impact security.

    Fix: Upgrade jQuery to version 3.5.0 or later to mitigate these vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may wrongly run a file as a script based on its content.

    Fix: Add this header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Pages without a referrer policy may expose sensitive URL information to other sites.

    Fix: Add the following header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Mixed Content IssuesLow

    Why it matters: Loading resources over HTTP on HTTPS pages can compromise security.

    Fix: Ensure all resources are loaded over HTTPS to avoid mixed content.

    Evidence: Mixed content

  7. 7

    Missing Permissions-PolicyInfo

    Why it matters: This header controls browser features and limits what injected scripts can do.

    Fix: Add the following header: Permissions-Policy: camera=(), microphone=(), geolocation=()

    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://frillylilly.ca/ → no strict-transport-security
    • https://frillylilly.ca/franchise/ → no strict-transport-security
    • https://frillylilly.ca/about-us/our-story/ → no strict-transport-security
    • https://frillylilly.ca/about-us/social-responsibility/ → no strict-transport-security
    • https://frillylilly.ca/about-us/waxing-care/ → no strict-transport-security
    • https://frillylilly.ca/about-us/health-standards/ → no strict-transport-security
    • https://frillylilly.ca/services/waxing-nails/ → no strict-transport-security
    • https://frillylilly.ca/services/facials/ → no strict-transport-security
    • https://frillylilly.ca/services/lash-brow/ → no strict-transport-security
    • https://frillylilly.ca/locations/ → no strict-transport-security
    • https://frillylilly.ca/products/ → no strict-transport-security
    • https://frillylilly.ca/careers/ → no strict-transport-security
  • FoundClickjacking protectionMedium

    4 of 275 HTML pages send 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://frillylilly.ca/ → no x-frame-options
    • https://frillylilly.ca/franchise/ → no x-frame-options
    • https://frillylilly.ca/about-us/our-story/ → no x-frame-options
    • https://frillylilly.ca/about-us/social-responsibility/ → no x-frame-options
    • https://frillylilly.ca/about-us/waxing-care/ → no x-frame-options
    • https://frillylilly.ca/about-us/health-standards/ → no x-frame-options
    • https://frillylilly.ca/services/waxing-nails/ → no x-frame-options
    • https://frillylilly.ca/services/facials/ → no x-frame-options
    • https://frillylilly.ca/services/lash-brow/ → no x-frame-options
    • https://frillylilly.ca/locations/ → no x-frame-options
    • https://frillylilly.ca/products/ → no x-frame-options
    • https://frillylilly.ca/careers/ → 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://frillylilly.ca/ → no x-content-type-options
    • https://frillylilly.ca/franchise/ → no x-content-type-options
    • https://frillylilly.ca/about-us/our-story/ → no x-content-type-options
    • https://frillylilly.ca/about-us/social-responsibility/ → no x-content-type-options
    • https://frillylilly.ca/about-us/waxing-care/ → no x-content-type-options
    • https://frillylilly.ca/about-us/health-standards/ → no x-content-type-options
    • https://frillylilly.ca/services/waxing-nails/ → no x-content-type-options
    • https://frillylilly.ca/services/facials/ → no x-content-type-options
    • https://frillylilly.ca/services/lash-brow/ → no x-content-type-options
    • https://frillylilly.ca/locations/ → no x-content-type-options
    • https://frillylilly.ca/products/ → no x-content-type-options
    • https://frillylilly.ca/careers/ → 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://frillylilly.ca/ → no referrer-policy
    • https://frillylilly.ca/franchise/ → no referrer-policy
    • https://frillylilly.ca/about-us/our-story/ → no referrer-policy
    • https://frillylilly.ca/about-us/social-responsibility/ → no referrer-policy
    • https://frillylilly.ca/about-us/waxing-care/ → no referrer-policy
    • https://frillylilly.ca/about-us/health-standards/ → no referrer-policy
    • https://frillylilly.ca/services/waxing-nails/ → no referrer-policy
    • https://frillylilly.ca/services/facials/ → no referrer-policy
    • https://frillylilly.ca/services/lash-brow/ → no referrer-policy
    • https://frillylilly.ca/locations/ → no referrer-policy
    • https://frillylilly.ca/products/ → no referrer-policy
    • https://frillylilly.ca/careers/ → 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://frillylilly.ca/ → no permissions-policy
    • https://frillylilly.ca/franchise/ → no permissions-policy
    • https://frillylilly.ca/about-us/our-story/ → no permissions-policy
    • https://frillylilly.ca/about-us/social-responsibility/ → no permissions-policy
    • https://frillylilly.ca/about-us/waxing-care/ → no permissions-policy
    • https://frillylilly.ca/about-us/health-standards/ → no permissions-policy
    • https://frillylilly.ca/services/waxing-nails/ → no permissions-policy
    • https://frillylilly.ca/services/facials/ → no permissions-policy
    • https://frillylilly.ca/services/lash-brow/ → no permissions-policy
    • https://frillylilly.ca/locations/ → no permissions-policy
    • https://frillylilly.ca/products/ → no permissions-policy
    • https://frillylilly.ca/careers/ → no permissions-policy
  • FoundMixed contentLow

    108 resources on HTTPS pages are loaded over plain HTTP.

    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/6a00d8341c630a53ef017ee944ab40970d-640wi…
    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/image.jpg?698
    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/1102665_10151593645530665_965306887_o.jp…
    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/Presentation4.jpg?700
    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/photo_0d52b20a-bc23-46c6-bc8f-c2035adb2f…
    • https://frillylilly.ca/blog/a-day-in-santa-monica-with-debra-2/ loads image http://cdn.shopify.com/s/files/1/0152/8783/files/1002165_556862991016192_1077493693_n.jpg…
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/Presentation1_c411b95a-b5e3-47c1-99d8-76…
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/Medicine_Cabinet_3b7e6df5-4876-447a-accc…
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/Mirror.JPG?592
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/IMG_1185.JPG?597
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/IMG_1176.JPG?598
    • https://frillylilly.ca/blog/design-is-in-the-details-at-frilly-lilly-… loads image http://cdn.shopify.com/s/files/1/0152/8783/files/IMG_1181_12f4a54b-5718-4eea-807a-bd3987b…
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 3.0.2 in https://frillylilly.ca/app/plugins/gravityforms/js/placeholders.jquery.min.js?v…: 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 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.)

    • use.typekit.net (40 script tags)
    • www.google.com (2 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/wp-admin/
6 checks passed, 1 not applicable
  • OKHTTPS

    All 275 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 4 of 275 pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKForms over HTTPS

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

Own frillylilly.ca?