Scanned sites / www.studio1rpdance.com / 2026-10-03-1127

www.studio1rpdance.com scan from 10/3/2026, 11:27:59 AM

Scan 2026-10-03-1127

Scanned 10/3/2026, 11:27:59 AM, finished 10/3/2026, 2:16:36 PM. Found on page 1 of brave web search results

Site: https://www.studio1rpdance.com/

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

57/ 100Needs work

On October 3, 2026 the Site Spider crawled 303 pages and 460 assets of www.studio1rpdance.com, starting from https://www.studio1rpdance.com/. It scored 57 out of 100, a result that needs work. 10 of 16 checks found something to fix, led by broken links (204), non-200 responses (204), duplicate content (204); 4 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), duplicate content (−8). 2 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: Medium1 medium, 1 low and 1 info findings. See the security findings ↓

Pages crawled
303
Assets fetched
460
Status
Completed
Checks with issues
10 of 16
CoverageComplete crawl

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

  • Title tags1 issue
    1 of 23 pages have title issues. 76 noindex or canonicalized pages excluded.
    −0.1 points
  • Meta descriptions9 issues
    9 of 23 pages have meta description issues. 76 noindex or canonicalized pages excluded.
    −0.7 points
  • HeadingsOK
    0 of 23 pages have heading issues. 76 noindex or canonicalized pages excluded.
  • Broken links204 issues
    476 internal links point at 204 broken URLs.
    −20 points
  • Links to other sites2 issues
    2 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 31 destinations checked.
    −0.8 points
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses204 issues
    206 URLs did not return a 2xx response. 204 of them are pages, 204 with an error status; the rest are assets or redirects.
    −10 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 23 indexable pages have indexability warnings. 76 pages noindex by design.
    −0.2 points
  • Image alt textOK
    0 of 238 image references have no alt attribute. 209 use an empty alt (decorative), which is fine.
  • Heavy assets1 issue
    1 asset larger than 500 KB among 460 fetched assets.
    −0.6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage50 issues
    No sitemap found. Tried: https://www.studio1rpdance.com/sitemap.xml (301), https://www.studio1rpdance.com/sitemap_index.xml (503). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link countsOK
    Internal link counts for 99 pages.
  • Thin content1 issue
    1 of 23 pages have fewer than 200 words. 76 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate content204 issues
    1 group of pages with identical HTML.
    −8 points

Where this scan sits among all scanned sites

1983 sites, median 80%, average 79%

www.studio1rpdance.com scores 57%, higher than 4% of the 1983 scanned sites. See the full ranking.

0571130%: 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%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 5 sites56%: 7 sites57%: 7 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 23 sites66%: 24 sites67%: 37 sites68%: 32 sites69%: 27 sites70%: 40 sites71%: 42 sites72%: 59 sites73%: 55 sites74%: 51 sites75%: 63 sites76%: 79 sites77%: 77 sites78%: 92 sites79%: 73 sites80%: 94 sites81%: 113 sites82%: 87 sites83%: 90 sites84%: 90 sites85%: 72 sites86%: 76 sites87%: 69 sites88%: 66 sites89%: 56 sites90%: 38 sites91%: 39 sites92%: 31 sites93%: 17 sites94%: 12 sites95%: 12 sites96%: 8 sites97%: 9 sites98%: 2 sites99%: 2 sites100%: 55 sites57% 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 website has several areas needing improvement, especially broken links and missing titles and meta descriptions. Addressing these can significantly enhance SEO performance.

  1. 1

    Fix Broken Links

    Why: 476 internal links to broken URLs negatively impact user experience and SEO.

    How: Identify and remove links to the 204 broken URLs. Review each case and decide if redirection or removal is appropriate.

    Checks: broken-links

  2. 2

    Address Title Tag Issues

    Why: Only 1 out of 23 pages has a correct title, affecting search ranking.

    How: Revise the title tag on the specific page to be under 60 characters and more descriptive.

    Checks: titles

  3. 3

    Improve Meta Descriptions

    Why: 9 of 23 pages have meta description issues, which can lower click-through rates.

    How: Provide unique and descriptive meta descriptions for pages where issues are reported.

    Checks: meta-descriptions

  4. 4

    Create a Sitemap

    Why: No sitemap found, limiting indexation of important pages.

    How: Generate a sitemap and add it to the root directory, then link in the robots.txt file.

    Checks: sitemap-coverage

  5. 5

    Fix Non-200 Responses

    Why: 206 URLs did not return a 2xx response, indicating server issues.

    How: Resolve the issues with these URLs to ensure they return the correct status code.

    Checks: status-codes

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 important headers for security. No Permissions-Policy header is set, and the Content Security Policy permits unsafe scripts, increasing vulnerability to attacks. Additionally, third-party scripts are running without Subresource Integrity, which can allow unauthorized changes to site behavior.

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

    Insecure Content Security PolicyMedium

    Why it matters: The current CSP allows unsafe inline scripts, reducing protection against script injection.

    Fix: Modify CSP to remove 'unsafe-inline' and 'unsafe-eval' from default-src.

    Evidence: Content Security Policy

  2. 2

    Third-Party Scripts InsecureLow

    Why it matters: Scripts from external domains run without Subresource Integrity, increasing risks if these domains are compromised.

    Fix: Implement Subresource Integrity on third-party scripts or restrict them through CSP.

    Evidence: Third-party scripts

  3. 3

    Missing Permissions-Policy HeaderInfo

    Why it matters: Without a Permissions-Policy, unused browser features remain accessible to potential malicious scripts.

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

    Evidence: Permissions policy

What the checks found

  • 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.studio1rpdance.com/ → no permissions-policy
    • https://www.studio1rpdance.com/about/ → no permissions-policy
    • https://www.studio1rpdance.com/locations/ → no permissions-policy
    • https://www.studio1rpdance.com/class-schedule/ → no permissions-policy
    • https://www.studio1rpdance.com/class-attire/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/classical-ballet/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/jazz/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/tap/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/contemporary/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/hip-hop/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/lyrical/ → no permissions-policy
    • https://www.studio1rpdance.com/classes/acro/ → no permissions-policy
  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://www.studio1rpdance.com/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/about/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/locations/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/class-schedule/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/class-attire/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/classical-ballet/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/jazz/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/tap/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/contemporary/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/hip-hop/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/lyrical/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
    • https://www.studio1rpdance.com/classes/acro/ → default-src 'unsafe-inline' 'unsafe-eval' https: data: blob:;
  • 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.)

    • link.msgsndr.com (40 script tags)
11 checks passed, 2 not applicable
  • OKHTTPS

    All 99 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 99 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 99 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 99 HTML pages.

  • OKReferrer policy

    referrer-policy is set on all 99 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.

  • OKVulnerable JavaScript libraries

    1 library version recognised, none with known vulnerabilities.

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

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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

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