Scanned sites / www.pranayogastudio.ca / 2026-09-27-2237

www.pranayogastudio.ca scan from 9/27/2026, 10:37:13 PM

Scan 2026-09-27-2237

Scanned 9/27/2026, 10:37:13 PM, finished 9/27/2026, 10:51:42 PM. 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 27, 2026 the Site Spider crawled 166 pages and 1066 assets of www.pranayogastudio.ca, starting from https://www.pranayogastudio.ca/. It scored 68 out of 100, a result that needs work. 9 of 15 checks found something to fix, led by meta descriptions (70), heavy assets (120), sitemap coverage (70); 4 checks passed. Most of the points went to meta descriptions (−7.8), heavy assets (−6), sitemap coverage (−5.8). 2 checks found something the score does not count, listed as noted. 1 check was not run because the crawl fetched nothing for it. 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
166
Assets fetched
1066
Status
Completed
Checks with issues
9 of 15
CoverageJob finished, partial coverage

1,232 of 1,232 discovered URLs were fetched, 220 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 102 link destinations on other sites have not been checked.

  • Title tags28 issues
    28 of 70 pages have title issues. 2 noindex or canonicalized pages excluded.
    −3.9 points
  • Meta descriptions70 issues
    70 of 70 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −7.8 points
  • Headings47 issues
    47 of 70 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −3.9 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sitesNot checked
    Not checked: the crawl fetched nothing this check can look at.
  • Redirects94 issues
    95 redirecting URLs, 0 of them chained.
    −4 points
  • Non-200 responses95 noted
    95 URLs did not return a 2xx response. 94 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.
  • Indexability2 issues
    2 of 72 indexable pages have indexability warnings.
    −0.3 points
  • Image alt text112 issues
    112 of 2190 image references have no alt attribute. 715 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets120 issues
    120 assets larger than 500 KB among 1066 fetched assets. 2 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages5 issues
    5 pages have no internal links pointing at them.
    −0.3 points
  • Sitemap coverage70 issues
    1 sitemap listing 0 URLs: 70 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.8 points
  • Internal link countsOK
    Internal link counts for 72 pages.
  • Thin contentOK
    0 of 70 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1316 sites, median 80%, average 79%

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

038750%: 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%: 1 site38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 5 sites52%: 5 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 13 sites63%: 11 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 26 sites68%: 25 sites69%: 14 sites70%: 30 sites71%: 29 sites72%: 36 sites73%: 33 sites74%: 41 sites75%: 36 sites76%: 47 sites77%: 44 sites78%: 56 sites79%: 45 sites80%: 66 sites81%: 75 sites82%: 68 sites83%: 58 sites84%: 59 sites85%: 45 sites86%: 51 sites87%: 44 sites88%: 49 sites89%: 36 sites90%: 28 sites91%: 31 sites92%: 18 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 1 site100%: 49 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

Your site has several SEO issues that need addressing to improve visibility and user experience. Prioritize fixing redirects, enhancing titles and meta descriptions, and addressing heading issues to elevate site health.

  1. 1

    Fix Redirects

    Why: 95 URLs redirect unnecessarily, impacting user experience and SEO.

    How: Update links to point directly to the final URLs to eliminate the redirects.

    Checks: redirects

  2. 2

    Update Title Tags

    Why: 28 pages have title issues, reducing clickability in search results.

    How: Revise titles to be unique, engaging and under 60 characters for the 28 affected pages.

    Checks: titles

  3. 3

    Revise Meta Descriptions

    Why: All pages share the same meta description, harming individual search visibility.

    How: Create unique meta descriptions for all pages, accurately reflecting content.

    Checks: meta-descriptions

  4. 4

    Correct Headings

    Why: 47 pages have heading issues, negatively impacting structure and SEO.

    How: Ensure every page has one H1 tag and is appropriately structured with H2s and H3s.

    Checks: headings

  5. 5

    Enhance Sitemap Coverage

    Why: 1 sitemap lists 0 URLs, leading to poor indexing.

    How: Update the sitemap to include all 70 crawled pages to improve discoverability.

    Checks: sitemap-coverage

  6. 6

    Reduce Heavy Assets

    Why: 120 assets are over 500 KB, slowing down the site.

    How: Compress large images and remove any that are not essential for page content.

    Checks: heavy-assets

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 several important security headers, leaving it vulnerable to threats like clickjacking and interception on initial requests. An API key exposed in the code might also present risks. It's essential to implement these measures to protect both the site and its visitors.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on initial HTTP requests.

    Fix: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your server configuration.

    Evidence: HTTP Strict Transport Security

  2. 2

    Absence of Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows unrestricted loading of scripts, styles, and frames.

    Fix: Implement 'Content-Security-Policy: default-src 'self'' to restrict sources.

    Evidence: Content Security Policy

  3. 3

    X-Frame-Options Missing (Clickjacking Protection)Medium

    Why it matters: Pages can be rendered in frames, posing clickjacking risks.

    Fix: Add 'X-Frame-Options: DENY' to your server headers.

    Evidence: Clickjacking protection

  4. 4

    Leaked API Key Found in Page CodeMedium

    Why it matters: An exposed Google API key can be exploited without restrictions.

    Fix: Restrict usage of the API key by configuring referrer restrictions in the Google Cloud console.

    Evidence: Keys and secrets in page code

  5. 5

    Lack of X-Content-Type-Options (MIME Sniffing Protection)Low

    Why it matters: This absence allows browsers to misinterpret files as scripts.

    Fix: Add 'X-Content-Type-Options: nosniff' to your server headers.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Full URLs may leak when users navigate to other sites.

    Fix: Include a header 'Referrer-Policy: no-referrer' to restrict referrer information.

    Evidence: Referrer policy

  7. 7

    Third-Party Scripts Missing Subresource IntegrityLow

    Why it matters: Insecure scripts can compromise site security if third-party resources are attacked.

    Fix: Consider implementing a gradual Content-Security-Policy to restrict and evaluate third-party scripts.

    Evidence: Third-party scripts

  8. 8

    Lack of Permissions PolicyInfo

    Why it matters: Not limiting browser features can increase risks from injected scripts.

    Fix: Implement 'Permissions-Policy: geolocation=(none)' to restrict unused 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 72 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 (13 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 72 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.

Sites scoring near www.pranayogastudio.ca

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

Own www.pranayogastudio.ca?

  • 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.pranayogastudio.ca. Removal needs no account and no proof of purchase.
www.pranayogastudio.ca scan 2026-09-27-2237 | DIY SEO Hub