Scanned sites / www.pranayogastudio.ca / 2026-09-19-0606

www.pranayogastudio.ca scan from 9/19/2026, 6:06:47 AM

A newer scan exists. See the latest report for www.pranayogastudio.ca.

Scan 2026-09-19-0606

Scanned 9/19/2026, 6:06:47 AM, finished 9/19/2026, 6:28:13 AM. Found with openstreetmap overpass

Site: https://www.pranayogastudio.ca/

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

68/ 100Needs work

On September 19, 2026 the Site Spider crawled 171 pages and 1075 assets of www.pranayogastudio.ca, starting from https://www.pranayogastudio.ca/. It scored 68 out of 100, a result that needs work. 9 of 14 checks found something to fix, led by image alt text (120), heavy assets (112), redirects (95); 5 checks passed. 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, 3 low and 1 info findings. See the security findings ↓

Pages crawled
171
Assets fetched
1075
Status
Completed
Checks with issues
9 of 14
  • Title tags28 issues
    28 of 72 pages have title issues. 4 noindex or canonicalized pages excluded.
  • Meta descriptions72 issues
    72 of 72 pages have meta description issues. 4 noindex or canonicalized pages excluded.
  • Headings49 issues
    49 of 72 pages have heading issues. 4 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Redirects95 issues
    96 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    96 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability4 issues
    4 of 76 indexable pages have indexability warnings.
  • Image alt text120 issues
    120 of 2320 image references have no alt attribute. 763 use an empty alt (decorative), which is fine.
  • Heavy assets112 issues
    100 assets larger than 500 KB among the 100 heaviest.
  • Orphan pages5 issues
    5 pages have no internal links pointing at them.
  • Sitemap coverage72 issues
    1 sitemap listing 0 URLs: 72 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Thin contentOK
    0 of 72 pages have fewer than 200 words. 4 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1100 sites, median 82%, average 80%

www.pranayogastudio.ca scores 68%, higher than 10% of the 1100 scanned sites. See the full ranking.

028560%: 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%: 1 site36%: 1 site37%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 5 sites64%: 9 sites65%: 9 sites66%: 8 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 23 sites71%: 22 sites72%: 24 sites73%: 24 sites74%: 30 sites75%: 26 sites76%: 37 sites77%: 37 sites78%: 34 sites79%: 33 sites80%: 43 sites81%: 54 sites82%: 49 sites83%: 45 sites84%: 55 sites85%: 47 sites86%: 47 sites87%: 48 sites88%: 56 sites89%: 38 sites90%: 51 sites91%: 38 sites92%: 25 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 10 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 12 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

The site has several issues needing attention, especially with redirects, status codes, and metadata. Prioritizing fixes will enhance user experience and SEO significantly.

  1. 1

    Fix Redirects

    Why: 96 URLs currently redirect, affecting site speed and user experience.

    How: Identify the correct final destination URL for each redirect and remove unnecessary redirects.

    Checks: redirects, status-codes

  2. 2

    Resolve Non-200 Responses

    Why: 96 URLs return non-200 statuses, indicating broken or improperly configured pages.

    How: Review these URLs, correcting 301 redirects or fixing broken links.

    Checks: status-codes

  3. 3

    Update Title Tags

    Why: 28 pages have title issues affecting SEO and discoverability.

    How: Ensure each page has a unique, concise title under 60 characters.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 72 pages have meta description issues, reducing click-through rates.

    How: Craft unique meta descriptions under 160 characters for each page.

    Checks: meta-descriptions

  5. 5

    Address Heading Issues

    Why: 49 pages have heading issues leading to potential SEO penalties.

    How: Standardize H1 usage to one per page and structure headings hierarchically.

    Checks: headings

  6. 6

    Improve Sitemap Coverage

    Why: Only 1 sitemap with 0 URLs listed is hindering site indexing.

    How: Ensure all crucial pages are added to the sitemap and resubmit it to search engines.

    Checks: sitemap-coverage

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 important security headers that protect against various threats, including data interception, clickjacking, and information leaks. Additionally, a Google API key is exposed in the code. Implementing the recommended headers and securing sensitive keys will enhance the site's security against potential attacks.

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

    Missing HSTSMedium

    Why it matters: Without HSTS, visitors can be vulnerable to man-in-the-middle attacks when accessing the site via HTTP.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains; preload' to respond with HTTPS requests.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Without CSP, the site is susceptible to cross-site scripting (XSS) and other code injection attacks.

    Fix: Add the header 'Content-Security-Policy: default-src 'self';' to limit where resources can be loaded from.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, your pages can be embedded in malicious frames, which could deceive users.

    Fix: Add the header 'X-Frame-Options: DENY' to prevent this attack vector.

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: An exposed API key can lead to unauthorized access and billing issues.

    Fix: Restrict the API key by setting appropriate HTTP referrer restrictions in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without the X-Content-Type-Options header, there is a risk browsers could execute files as scripts.

    Fix: Add the header 'X-Content-Type-Options: nosniff' to protect against content type confusion.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a Referrer-Policy, sensitive information may be sent to external sites when users click links.

    Fix: Add the header 'Referrer-Policy: no-referrer' to restrict the information sent.

    Evidence: Referrer policy

  7. 7

    Third-party Scripts Lack Integrity ChecksLow

    Why it matters: Third-party scripts can be altered, leading to potential security breaches.

    Fix: Consider implementing Subresource Integrity (SRI) where possible or use a strict Content Security Policy to control resource access.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: Without a Permissions-Policy, unnecessary browser features may remain enabled, increasing risk from malicious scripts.

    Fix: Add a header like 'Permissions-Policy: geolocation=(self), microphone=()' to limit access to features.

    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.pranayogastudio.ca/ → no strict-transport-security
    • https://www.pranayogastudio.ca/workshops/ → no strict-transport-security
    • https://www.pranayogastudio.ca/training/ → no strict-transport-security
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no strict-transport-security
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no strict-transport-security
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no strict-transport-security
    • https://www.pranayogastudio.ca/training/speciality-training/ → no strict-transport-security
    • https://www.pranayogastudio.ca/schedule/ → no strict-transport-security
    • https://www.pranayogastudio.ca/yoga/ → no strict-transport-security
    • https://www.pranayogastudio.ca/classes/rates/ → no strict-transport-security
    • https://www.pranayogastudio.ca/about/studio/ → no strict-transport-security
    • https://www.pranayogastudio.ca/about/teachers/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 76 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.pranayogastudio.ca/ → no content-security-policy
    • https://www.pranayogastudio.ca/workshops/ → no content-security-policy
    • https://www.pranayogastudio.ca/training/ → no content-security-policy
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no content-security-policy
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no content-security-policy
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no content-security-policy
    • https://www.pranayogastudio.ca/training/speciality-training/ → no content-security-policy
    • https://www.pranayogastudio.ca/schedule/ → no content-security-policy
    • https://www.pranayogastudio.ca/yoga/ → no content-security-policy
    • https://www.pranayogastudio.ca/classes/rates/ → no content-security-policy
    • https://www.pranayogastudio.ca/about/studio/ → no content-security-policy
    • https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no x-frame-options
    • https://www.pranayogastudio.ca/workshops/ → no x-frame-options
    • https://www.pranayogastudio.ca/training/ → no x-frame-options
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no x-frame-options
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no x-frame-options
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no x-frame-options
    • https://www.pranayogastudio.ca/training/speciality-training/ → no x-frame-options
    • https://www.pranayogastudio.ca/schedule/ → no x-frame-options
    • https://www.pranayogastudio.ca/yoga/ → no x-frame-options
    • https://www.pranayogastudio.ca/classes/rates/ → no x-frame-options
    • https://www.pranayogastudio.ca/about/studio/ → no x-frame-options
    • https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no x-content-type-options
    • https://www.pranayogastudio.ca/workshops/ → no x-content-type-options
    • https://www.pranayogastudio.ca/training/ → no x-content-type-options
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no x-content-type-options
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no x-content-type-options
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no x-content-type-options
    • https://www.pranayogastudio.ca/training/speciality-training/ → no x-content-type-options
    • https://www.pranayogastudio.ca/schedule/ → no x-content-type-options
    • https://www.pranayogastudio.ca/yoga/ → no x-content-type-options
    • https://www.pranayogastudio.ca/classes/rates/ → no x-content-type-options
    • https://www.pranayogastudio.ca/about/studio/ → no x-content-type-options
    • https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no referrer-policy
    • https://www.pranayogastudio.ca/workshops/ → no referrer-policy
    • https://www.pranayogastudio.ca/training/ → no referrer-policy
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no referrer-policy
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no referrer-policy
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no referrer-policy
    • https://www.pranayogastudio.ca/training/speciality-training/ → no referrer-policy
    • https://www.pranayogastudio.ca/schedule/ → no referrer-policy
    • https://www.pranayogastudio.ca/yoga/ → no referrer-policy
    • https://www.pranayogastudio.ca/classes/rates/ → no referrer-policy
    • https://www.pranayogastudio.ca/about/studio/ → no referrer-policy
    • https://www.pranayogastudio.ca/about/teachers/ → 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.pranayogastudio.ca/ → no permissions-policy
    • https://www.pranayogastudio.ca/workshops/ → no permissions-policy
    • https://www.pranayogastudio.ca/training/ → no permissions-policy
    • https://www.pranayogastudio.ca/training/200-hour-teacher-training/ → no permissions-policy
    • https://www.pranayogastudio.ca/training/500-hours-teacher-training-2/ → no permissions-policy
    • https://www.pranayogastudio.ca/training/prenatal-yoga-teacher-training/ → no permissions-policy
    • https://www.pranayogastudio.ca/training/speciality-training/ → no permissions-policy
    • https://www.pranayogastudio.ca/schedule/ → no permissions-policy
    • https://www.pranayogastudio.ca/yoga/ → no permissions-policy
    • https://www.pranayogastudio.ca/classes/rates/ → no permissions-policy
    • https://www.pranayogastudio.ca/about/studio/ → no permissions-policy
    • https://www.pranayogastudio.ca/about/teachers/ → no permissions-policy
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…mQ (39 chars) in https://www.pranayogastudio.ca/contact/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 3 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.)

    • a.mailmunch.co (40 script tags)
    • momence.com (2 script tags)
    • maps.googleapis.com (15 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

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

    6 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    3 library versions recognised, none with known vulnerabilities.

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

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.

This report was produced by the DIY SEO Hub Site Spider crawling www.pranayogastudio.ca from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

www.pranayogastudio.ca scan 2026-09-19-0606 | DIY SEO Hub