Scanned sites / slaaay.lol

SEO report for slaaay.lol DR 0

The latest Site Spider scan of slaaay.lol, with 2 scans on record. Each scan is at its own address, for example /domain/slaaay-lol/2026-09-10-0056.

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

Latest scan

Scanned 2026-09-10 00:56:24 UTC, finished 2026-09-10 00:58:24 UTC

Site: https://slaaay.lol/

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

63/ 100Needs work

On September 10, 2026 the Site Spider crawled 40 pages and 170 assets of slaaay.lol, starting from https://slaaay.lol/. It scored 63 out of 100, a result that needs work. 8 of 27 checks found something to fix, led by indexability (20), title tags (16), sitemap coverage (40); 12 checks passed. Most of the points went to indexability (−10), title tags (−8), sitemap coverage (−6). 7 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: Medium2 medium and 2 low findings. See the security findings ↓

Pages crawled
40
Assets fetched
170
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

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

  • Title tags16 issues
    16 of 20 pages have title issues.
    −8 points
  • Meta descriptions7 issues
    7 of 20 pages have meta description issues.
    −2.8 points
  • Headings1 issue
    1 of 20 pages have heading issues.
    −0.3 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites3 issues
    3 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 4 destinations checked.
    −1.2 points
  • Redirects24 noted
    24 redirecting URLs, 0 of them chained.
  • Non-200 responses24 noted
    24 URLs did not return a 2xx response. 20 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.
  • Indexability20 issues
    20 of 20 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 47 image references have no alt attribute. 16 use an empty alt (decorative), which is fine.
  • Heavy assets5 issues
    5 assets larger than 500 KB among 170 fetched assets.
    −3 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage40 issues
    1 sitemap listing 20 URLs: 20 crawled pages missing, 20 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 20 pages; none is a dead end or buried.
  • Thin content15 issues
    15 of 20 pages have fewer than 200 words.
    −6 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 40 page URLs are plain lowercase addresses without parameters.
  • Canonicals20 noted
    20 of 20 pages have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 20 pages are open to search engines.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structure17 noted
    17 of 20 pages could use the title, heading and snippet space better.
  • Image weight and alt length11 noted
    11 images over 100 KB; 0 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 20 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; 12 response headers recorded across 210 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 20 pages; 0 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 Insights4 noted
    Mobile performance 89 on average across 5 pages; 4 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

What changed since the last scan

Score unchanged

slaaay.lol scored 63 out of 100 in both of its last two scans. The two crawls did not cover the same ground, so part of the difference is coverage rather than change.

  • Crawl coverage differed between the two scans; some differences may be coverage rather than change
  1. 2026-09-08 20:03:53 UTC63/10040 pages
  2. 2026-09-10 00:56:24 UTC63/10040 pages

Where this site sits among all scanned sites

2312 sites, median 79%, average 78%

slaaay.lol scores 63%, higher than 8% of the 2312 scanned sites. See the full ranking.

0581160%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 16 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 46 sites70%: 44 sites71%: 68 sites72%: 70 sites73%: 69 sites74%: 69 sites75%: 71 sites76%: 86 sites77%: 92 sites78%: 107 sites79%: 85 sites80%: 105 sites81%: 106 sites82%: 116 sites83%: 98 sites84%: 107 sites85%: 86 sites86%: 70 sites87%: 73 sites88%: 59 sites89%: 60 sites90%: 34 sites91%: 44 sites92%: 37 sites93%: 22 sites94%: 15 sites95%: 11 sites96%: 10 sites97%: 12 sites98%: 4 sites99%: 1 site100%: 70 sites63% 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.

Several critical issues need addressing to improve SEO health, including non-200 responses, missing titles and meta descriptions, and indexability warnings. Focusing on these will significantly enhance the site's performance.

  1. 1

    Fix Non-200 Responses

    Why: 24 URLs are returning non-200 responses, harming access and user experience.

    How: Update all URLs in your site settings to ensure they directly resolve without redirecting.

    Checks: status-codes

  2. 2

    Address Title Tag Issues

    Why: 16 pages have short title tags, which may not effectively summarize the content.

    How: Revise title tags to be more descriptive and exceed 30 characters for better insights.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 7 pages have short meta descriptions which can lead to less clickable search results.

    How: Expand meta descriptions to be more engaging and include relevant keywords while keeping them under 160 characters.

    Checks: meta-descriptions

  4. 4

    Add Canonical Tags

    Why: All pages lack canonical tags, which can lead to indexation issues.

    How: Add a canonical tag in the head section of each page to define its preferred URL.

    Checks: indexability

  5. 5

    Perform Redirect Corrections

    Why: 24 redirecting URLs could create confusion for users and search engines.

    How: Change redirects to direct URLs instead of multiple hops, and ensure they return 200 statuses.

    Checks: redirects

  6. 6

    Create More Comprehensive Content

    Why: 15 pages have thin content that could lead to poor search rankings.

    How: Enhance each page with additional relevant content and insights to exceed 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

The site lacks strong security protections, including a Content Security Policy and clickjacking protection. Implementing these measures is crucial to safeguard against malicious attacks. Address these issues promptly to enhance the site's security posture.

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

    Missing Content Security PolicyMedium

    Why it matters: The absence of a Content Security Policy allows unrestricted loading of resources, increasing the risk of cross-site scripting attacks.

    Fix: Add a header: `Content-Security-Policy: default-src 'self';`

    Evidence: Content Security Policy

  2. 2

    Lack of Clickjacking ProtectionMedium

    Why it matters: Not having X-Frame-Options enables other sites to embed your pages, potentially deceiving users into revealing sensitive information.

    Fix: Add a header: `X-Frame-Options: DENY`.

    Evidence: Clickjacking protection

  3. 3

    Absence of MIME Sniffing ProtectionLow

    Why it matters: Lack of X-Content-Type-Options may permit browsers to interpret files as different types, which can lead to security risks.

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

    Evidence: MIME sniffing protection

  4. 4

    Third-party Scripts Without IntegrityLow

    Why it matters: Running scripts from external domains without Subresource Integrity increases the risk of harmful changes to your site if those scripts are compromised.

    Fix: Implement Subresource Integrity where possible, or use a Content Security Policy to restrict these sources.

    Evidence: Third-party scripts

What the checks found

  • FoundContent Security PolicyMedium

    None of the 20 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.slaaay.lol/ → no content-security-policy
    • https://www.slaaay.lol/daily → no content-security-policy
    • https://www.slaaay.lol/categories → no content-security-policy
    • https://www.slaaay.lol/about → no content-security-policy
    • https://www.slaaay.lol/terms → no content-security-policy
    • https://www.slaaay.lol/refunds → no content-security-policy
    • https://www.slaaay.lol/privacy → no content-security-policy
    • https://www.slaaay.lol/rules → no content-security-policy
    • https://www.slaaay.lol/contact → no content-security-policy
    • https://www.slaaay.lol/category/beauty-skincare → no content-security-policy
    • https://www.slaaay.lol/category/fashion-style → no content-security-policy
    • https://www.slaaay.lol/category/hair-nails → 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.slaaay.lol/ → no x-frame-options
    • https://www.slaaay.lol/daily → no x-frame-options
    • https://www.slaaay.lol/categories → no x-frame-options
    • https://www.slaaay.lol/about → no x-frame-options
    • https://www.slaaay.lol/terms → no x-frame-options
    • https://www.slaaay.lol/refunds → no x-frame-options
    • https://www.slaaay.lol/privacy → no x-frame-options
    • https://www.slaaay.lol/rules → no x-frame-options
    • https://www.slaaay.lol/contact → no x-frame-options
    • https://www.slaaay.lol/category/beauty-skincare → no x-frame-options
    • https://www.slaaay.lol/category/fashion-style → no x-frame-options
    • https://www.slaaay.lol/category/hair-nails → 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.slaaay.lol/ → no x-content-type-options
    • https://www.slaaay.lol/daily → no x-content-type-options
    • https://www.slaaay.lol/categories → no x-content-type-options
    • https://www.slaaay.lol/about → no x-content-type-options
    • https://www.slaaay.lol/terms → no x-content-type-options
    • https://www.slaaay.lol/refunds → no x-content-type-options
    • https://www.slaaay.lol/privacy → no x-content-type-options
    • https://www.slaaay.lol/rules → no x-content-type-options
    • https://www.slaaay.lol/contact → no x-content-type-options
    • https://www.slaaay.lol/category/beauty-skincare → no x-content-type-options
    • https://www.slaaay.lol/category/fashion-style → no x-content-type-options
    • https://www.slaaay.lol/category/hair-nails → no x-content-type-options
  • 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.)

    • cloud.umami.is (20 script tags)
8 checks passed, 4 not applicable
  • OKHTTPS

    All 20 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 20 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

    1 form 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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

Sites scoring near slaaay.lol

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

Own slaaay.lol?