Scanned sites / www.prettysweetco.com / 2026-10-01-2317

www.prettysweetco.com scan from 10/1/2026, 11:17:41 PM

Scan 2026-10-01-2317

Scanned 10/1/2026, 11:17:41 PM, finished 10/2/2026, 2:15:52 AM. Found on page 1 of brave web search results

Site: https://www.prettysweetco.com/

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

72/ 100Needs work

On October 1, 2026 the Site Spider crawled 358 pages and 976 assets of www.prettysweetco.com, starting from https://www.prettysweetco.com/. It scored 72 out of 100, a result that needs work. 11 of 16 checks found something to fix, led by meta descriptions (247), heavy assets (102), headings (246); 4 checks passed. Most of the points went to meta descriptions (−7), heavy assets (−6), headings (−5.2). 1 check 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
358
Assets fetched
976
Status
Completed
Checks with issues
11 of 16
CoverageComplete crawl

1,334 of 1,346 discovered URLs were fetched, 1 failed, 11 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 6 link destinations on other sites were checked.

  • Title tags105 issues
    105 of 247 pages have title issues. 36 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions247 issues
    247 of 247 pages have meta description issues. 36 noindex or canonicalized pages excluded.
    −7 points
  • Headings246 issues
    246 of 247 pages have heading issues. 36 noindex or canonicalized pages excluded.
    −5.2 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 6 destinations checked.
    −0.1 points
  • Redirects42 issues
    75 redirecting URLs, 32 of them chained.
    −0.6 points
  • Non-200 responses2 issues
    77 URLs did not return a 2xx response. 76 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1 issue
    1 of 283 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 769 image references have no alt attribute. 284 use an empty alt (decorative), which is fine.
  • Heavy assets102 issues
    102 assets larger than 500 KB among 976 fetched assets.
    −6 points
  • Orphan pages40 issues
    40 pages have no internal links pointing at them.
    −0.6 points
  • Sitemap coverage39 issues
    11 sitemaps listing 281 URLs: 0 crawled pages missing, 34 listed URLs broken or redirecting, 5 reachable only via the sitemap.
    −0.8 points
  • Internal link countsOK
    Internal link counts for 283 pages.
  • Thin content159 issues
    159 of 247 pages have fewer than 200 words. 36 noindex or canonicalized pages excluded.
    −4.5 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1916 sites, median 80%, average 79%

www.prettysweetco.com scores 72%, higher than 20% of the 1916 scanned sites. See the full ranking.

0561110%: 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%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 7 sites57%: 6 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 22 sites66%: 22 sites67%: 37 sites68%: 30 sites69%: 27 sites70%: 39 sites71%: 40 sites72%: 57 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 77 sites77%: 73 sites78%: 89 sites79%: 70 sites80%: 91 sites81%: 111 sites82%: 86 sites83%: 88 sites84%: 87 sites85%: 67 sites86%: 75 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 36 sites91%: 36 sites92%: 29 sites93%: 16 sites94%: 13 sites95%: 12 sites96%: 8 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites72% 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

Your site has several issues that need addressing regarding redirects, meta descriptions, titles, headings, heavy assets, and thin content. Prioritize resolving these for better SEO performance.

  1. 1

    Fix Redirects and Non-200 Responses

    Why: Streamline redirects to enhance user experience and SEO.

    How: Identify and resolve 75 redirect URLs, especially chained redirects.

    Checks: redirects, status-codes

  2. 2

    Add Meta Descriptions

    Why: Missing meta descriptions impact search visibility.

    How: Create and implement unique meta descriptions for all 247 pages.

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: Short title tags hinder search engine rankings.

    How: Revise and optimize all title tags across 105 impacted pages.

    Checks: titles

  4. 4

    Add H1 Headings

    Why: Missing H1s negatively impact page relevance.

    How: Add appropriate H1 headings on all 246 pages lacking them.

    Checks: headings

  5. 5

    Optimize Heavy Assets

    Why: Large assets slow down the site, affecting performance.

    How: Compress images larger than 500KB, focusing on the largest ones first.

    Checks: heavy-assets

  6. 6

    Enhance Content on Thin Pages

    Why: Thin content affects usability and rankings.

    How: Add more content to 159 pages with less than 200 words.

    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

Your website has several important security vulnerabilities that need attention, including missing response headers and the use of outdated libraries. Implementing recommended fixes will enhance security and protect user data.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors using HTTP may be susceptible to interception.

    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: A CSP helps prevent XSS and other code injection attacks by restricting sources of content.

    Fix: Add the header 'Content-Security-Policy: default-src 'self'' to all HTML responses.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows clickjacking attacks by embedding your site in a frame.

    Fix: Add the header 'X-Frame-Options: DENY' to all responses.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery LibraryMedium

    Why it matters: Using jQuery 1.7.0 exposes your site to known vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or newer.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may execute files based on their content, risking security.

    Fix: Add the header 'X-Content-Type-Options: nosniff' to all HTML responses.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of this header exposes your full URL to other sites through referrer data.

    Fix: Add the header 'Referrer-Policy: no-referrer' to all HTML responses.

    Evidence: Referrer policy

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: This policy limits the capabilities of browser features that can be exploited by injected scripts.

    Fix: Add the header 'Permissions-Policy: geolocation=(), microphone=(), camera=()' to all HTML responses.

    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.prettysweetco.com/ → no strict-transport-security
    • https://www.prettysweetco.com/order/ → no strict-transport-security
    • https://www.prettysweetco.com/about/ → no strict-transport-security
    • https://www.prettysweetco.com/faq/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/seasonal/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/cakes/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/cupcakes/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/donuts/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no strict-transport-security
    • https://www.prettysweetco.com/menu/sweets/ → no strict-transport-security
    • https://www.prettysweetco.com/weddings/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 283 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.prettysweetco.com/ → no content-security-policy
    • https://www.prettysweetco.com/order/ → no content-security-policy
    • https://www.prettysweetco.com/about/ → no content-security-policy
    • https://www.prettysweetco.com/faq/ → no content-security-policy
    • https://www.prettysweetco.com/menu/seasonal/ → no content-security-policy
    • https://www.prettysweetco.com/menu/ → no content-security-policy
    • https://www.prettysweetco.com/menu/cakes/ → no content-security-policy
    • https://www.prettysweetco.com/menu/cupcakes/ → no content-security-policy
    • https://www.prettysweetco.com/menu/donuts/ → no content-security-policy
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no content-security-policy
    • https://www.prettysweetco.com/menu/sweets/ → no content-security-policy
    • https://www.prettysweetco.com/weddings/ → 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.prettysweetco.com/ → no x-frame-options
    • https://www.prettysweetco.com/order/ → no x-frame-options
    • https://www.prettysweetco.com/about/ → no x-frame-options
    • https://www.prettysweetco.com/faq/ → no x-frame-options
    • https://www.prettysweetco.com/menu/seasonal/ → no x-frame-options
    • https://www.prettysweetco.com/menu/ → no x-frame-options
    • https://www.prettysweetco.com/menu/cakes/ → no x-frame-options
    • https://www.prettysweetco.com/menu/cupcakes/ → no x-frame-options
    • https://www.prettysweetco.com/menu/donuts/ → no x-frame-options
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no x-frame-options
    • https://www.prettysweetco.com/menu/sweets/ → no x-frame-options
    • https://www.prettysweetco.com/weddings/ → 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.prettysweetco.com/ → no x-content-type-options
    • https://www.prettysweetco.com/order/ → no x-content-type-options
    • https://www.prettysweetco.com/about/ → no x-content-type-options
    • https://www.prettysweetco.com/faq/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/seasonal/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/cakes/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/cupcakes/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/donuts/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no x-content-type-options
    • https://www.prettysweetco.com/menu/sweets/ → no x-content-type-options
    • https://www.prettysweetco.com/weddings/ → 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.prettysweetco.com/ → no referrer-policy
    • https://www.prettysweetco.com/order/ → no referrer-policy
    • https://www.prettysweetco.com/about/ → no referrer-policy
    • https://www.prettysweetco.com/faq/ → no referrer-policy
    • https://www.prettysweetco.com/menu/seasonal/ → no referrer-policy
    • https://www.prettysweetco.com/menu/ → no referrer-policy
    • https://www.prettysweetco.com/menu/cakes/ → no referrer-policy
    • https://www.prettysweetco.com/menu/cupcakes/ → no referrer-policy
    • https://www.prettysweetco.com/menu/donuts/ → no referrer-policy
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no referrer-policy
    • https://www.prettysweetco.com/menu/sweets/ → no referrer-policy
    • https://www.prettysweetco.com/weddings/ → 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.prettysweetco.com/ → no permissions-policy
    • https://www.prettysweetco.com/order/ → no permissions-policy
    • https://www.prettysweetco.com/about/ → no permissions-policy
    • https://www.prettysweetco.com/faq/ → no permissions-policy
    • https://www.prettysweetco.com/menu/seasonal/ → no permissions-policy
    • https://www.prettysweetco.com/menu/ → no permissions-policy
    • https://www.prettysweetco.com/menu/cakes/ → no permissions-policy
    • https://www.prettysweetco.com/menu/cupcakes/ → no permissions-policy
    • https://www.prettysweetco.com/menu/donuts/ → no permissions-policy
    • https://www.prettysweetco.com/menu/sugar-cookies/ → no permissions-policy
    • https://www.prettysweetco.com/menu/sweets/ → no permissions-policy
    • https://www.prettysweetco.com/weddings/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 1.7.0 in https://www.prettysweetco.com/wp-content/themes/salient/js/third-party/hoverint…: CVE-2012-6708 (selector XSS), CVE-2015-9251, CVE-2019-11358, CVE-2020-11022, CVE-2020-11023; fixed in 3.5.0
  • NoteThird-party scripts

    Scripts run from 4 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 (40 script tags)
    • unpkg.com (80 script tags)
    • cdn.jsdelivr.net (80 script tags)
    • cdn.by.wonderpush.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 6 paths 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: /admin/
    • Disallow: /includes/
    • Disallow: /config/
    • Disallow: /backup/
    • Disallow: /wp-admin/
    • Disallow: /wp-includes/
6 checks passed, 1 not applicable
  • OKHTTPS

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

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

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