Scanned sites / www.studio1rpdance.com / 2026-10-03-0712
www.studio1rpdance.com scan from 10/3/2026, 7:12:52 AM
Scan 2026-10-03-0712
Scanned 10/3/2026, 7:12:52 AM, finished 10/3/2026, 8:22:43 AM. Found on page 5 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.
On October 3, 2026 the Site Spider crawled 329 pages and 473 assets of www.studio1rpdance.com, starting from https://www.studio1rpdance.com/. It scored 57 out of 100, a result that needs work. 11 of 16 checks found something to fix, led by broken links (202), non-200 responses (202), duplicate content (149); 4 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), duplicate content (−8). 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: Medium1 medium, 1 low and 1 info findings. See the security findings ↓
- Pages crawled
- 329
- Assets fetched
- 473
- Status
- Completed
- Checks with issues
- 11 of 16
802 of 802 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 32 link destinations on other sites were checked.
- Title tags1 issue1 of 24 pages have title issues. 86 noindex or canonicalized pages excluded.−0.1 points
- Meta descriptions9 issues9 of 24 pages have meta description issues. 86 noindex or canonicalized pages excluded.−0.7 points
- HeadingsOK0 of 24 pages have heading issues. 86 noindex or canonicalized pages excluded.
- Broken links202 issues207 internal links point at 202 broken URLs.−20 points
- Links to other sites2 issues2 destinations answered with an error, 7 could not be determined (timeouts, rate limits or refusals), of 32 destinations checked.−0.7 points
- Redirects17 issues18 redirecting URLs, 0 of them chained.−0.6 points
- Non-200 responses202 issues221 URLs did not return a 2xx response. 219 of them are pages, 202 with an error status; the rest are assets or redirects.−10 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability1 issue1 of 24 indexable pages have indexability warnings. 86 pages noindex by design.−0.1 points
- Image alt textOK0 of 260 image references have no alt attribute. 213 use an empty alt (decorative), which is fine.
- Heavy assets1 issue1 asset larger than 500 KB among 473 fetched assets.−0.6 points
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage55 issuesNo 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 countsOKInternal link counts for 110 pages.
- Thin content1 issue1 of 24 pages have fewer than 200 words. 86 noindex or canonicalized pages excluded.−0.1 points
- Duplicate content149 issues2 groups of pages with identical HTML.−8 points
Where this scan sits among all scanned sites
1942 sites, median 80%, average 79%
www.studio1rpdance.com scores 57%, higher than 4% of the 1942 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour website has significant issues that need attention, particularly broken links and non-200 responses. Fixing these will improve user experience and SEO. Additionally, optimize your title tags and meta descriptions for better visibility.
- 1
Fix Broken Links
Why: Improves user experience and site credibility.
How: Identify links leading to broken URLs, and either correct the destination or remove the links.
Checks: broken-links
- 2
Resolve Non-200 Responses
Why: Enhances site accessibility and search engine rankings.
How: Review URLs returning errors, address them by fixing, redirecting, or removing these links.
Checks: status-codes
- 3
Add a Sitemap
Why: Improves indexability and helps search engines crawl your site better.
How: Create a sitemap.xml file and ensure it's accessible at the root of your domain.
Checks: sitemap-coverage
- 4
Optimize Title Tags
Why: Helps improve SEO and click-through rates.
How: Revise the long title tag to 60 characters or less to enhance search engine results.
Checks: titles
- 5
Fix Meta Description Issues
Why: Aids in search engine visibility and user engagement.
How: Create unique, engaging meta descriptions for pages that are missing or too short.
Checks: meta-descriptions
- 6
Address Duplicate Content
Why: Prevents keyword cannibalization and improves ranking.
How: Identify and differentiate duplicate pages to improve unique content across your site.
Checks: duplicate-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 crawlThe site lacks crucial security headers, exposing it to potential vulnerabilities. Specifically, a missing Permissions-Policy header may allow unauthorized access to sensitive browser features, and your Content Security Policy allows unsafe script execution, increasing the risk of attacks. Additionally, third-party scripts run without integrity checks could compromise the site.
- 0 high
- 1 medium
- 1 low
- 1 info
- 1
Insecure Content Security PolicyMedium
Why it matters: The existing Content Security Policy allows inline and eval scripts, which undermines its protective capabilities against XSS attacks.
Fix: Revise the CSP to eliminate 'unsafe-inline' and 'unsafe-eval', e.g., Content-Security-Policy: default-src 'self'; script-src 'self' https:; object-src 'none';
Evidence: Content Security Policy
- 2
Third-Party Scripts Without Subresource IntegrityLow
Why it matters: Scripts from another domain (link.msgsndr.com) lack Subresource Integrity, making the site vulnerable if these scripts are compromised.
Fix: Add Subresource Integrity to the third-party scripts where applicable, or adjust the Content Security Policy to restrict the loading of untrusted scripts.
Evidence: Third-party scripts
- 3
Missing Permissions-Policy HeaderInfo
Why it matters: Without a Permissions-Policy header, browser features like camera, microphone, and geolocation can be accessed by potentially malicious scripts.
Fix: Implement a Permissions-Policy header using: Permissions-Policy: geolocation=(), microphone=(), camera=()
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/dance-classes/ → 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
- 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/dance-classes/ → 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:;
- 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 110 crawled pages were served over HTTPS.
- OKHTTP Strict Transport Security
strict-transport-security is set on all 110 HTML pages.
- OKClickjacking protection
x-frame-options is set on all 110 HTML pages.
- OKMIME sniffing protection
x-content-type-options is set on all 110 HTML pages.
- OKReferrer policy
referrer-policy is set on all 110 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.
- member.homebuilders.mb.ca58/100 · rank 1847 · 1,350 pages
- example.com58/100 · rank 1847 · 1 page
- example.org58/100 · rank 1847 · 1 page
- www.sistani.org57/100 · rank 1862 · 4,997 pages
- www.echodance.com57/100 · rank 1862 · 47 pages
- www.northwestanimal.com57/100 · rank 1862 · 61 pages
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.