Scanned sites / www.pranayogastudio.ca / 2026-10-04-0151

www.pranayogastudio.ca scan from 10/4/2026, 1:51:36 AM

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

Scan 2026-10-04-0151

Scanned 10/4/2026, 1:51:36 AM, finished 10/4/2026, 5:52:30 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 October 4, 2026 the Site Spider crawled 129 pages and 1000 assets of www.pranayogastudio.ca, starting from https://www.pranayogastudio.ca/. It scored 68 out of 100, a result that needs work. 10 of 15 checks found something to fix, led by meta descriptions (65), heavy assets (79), sitemap coverage (65); 4 checks passed. Most of the points went to meta descriptions (−7.8), heavy assets (−6), sitemap coverage (−5.8). 1 check 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, 2 low and 1 info findings. See the security findings ↓

Pages crawled
129
Assets fetched
1000
Status
Completed
Checks with issues
10 of 15
CoverageJob finished, partial coverage

1,129 of 1,129 discovered URLs were fetched, 51 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. 95 link destinations on other sites have not been checked.

  • Title tags26 issues
    26 of 65 pages have title issues. 2 noindex or canonicalized pages excluded.
    −3.9 points
  • Meta descriptions65 issues
    65 of 65 pages have meta description issues. 2 noindex or canonicalized pages excluded.
    −7.8 points
  • Headings42 issues
    42 of 65 pages have heading issues. 2 noindex or canonicalized pages excluded.
    −3.8 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.
  • Redirects61 issues
    62 redirecting URLs, 0 of them chained.
    −3.6 points
  • Non-200 responses1 issue
    65 URLs did not return a 2xx response. 62 of them are pages, 1 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 67 indexable pages have indexability warnings.
    −0.3 points
  • Image alt text102 issues
    102 of 2153 image references have no alt attribute. 615 use an empty alt (decorative), which is fine.
    −0.3 points
  • Heavy assets79 issues
    79 assets larger than 500 KB among 1000 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 coverage65 issues
    1 sitemap listing 0 URLs: 65 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 67 pages.
  • Thin contentOK
    0 of 65 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

2051 sites, median 80%, average 78%

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

0521040%: 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%: 3 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 3 sites48%: 2 sites49%: 6 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 10 sites61%: 14 sites62%: 16 sites63%: 19 sites64%: 16 sites65%: 28 sites66%: 24 sites67%: 39 sites68%: 34 sites69%: 24 sites70%: 46 sites71%: 48 sites72%: 64 sites73%: 57 sites74%: 57 sites75%: 73 sites76%: 83 sites77%: 76 sites78%: 96 sites79%: 78 sites80%: 104 sites81%: 102 sites82%: 99 sites83%: 91 sites84%: 87 sites85%: 74 sites86%: 76 sites87%: 66 sites88%: 67 sites89%: 52 sites90%: 39 sites91%: 39 sites92%: 32 sites93%: 18 sites94%: 14 sites95%: 10 sites96%: 6 sites97%: 9 sites98%: 1 site99%: 2 sites100%: 56 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 issues needing attention, including redirects, title tags, and meta descriptions. Addressing these will improve SEO significantly. Let's focus on critical fixes that will enhance site performance.

  1. 1

    Fix Redirects

    Why: Redirects can slow down pages and confuse users.

    How: Remove unnecessary redirects and ensure all pages point directly to their final URL.

    Checks: redirects

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 responses hinder accessibility and SEO performance.

    How: Identify and repair or remove URLs that return errors, ensuring they are live and accessible.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Optimized title tags enhance search visibility.

    How: Revise titles exceeding 60 characters for uniqueness and relevance.

    Evidence: 437 KB of stylesheet, loaded by 67 pages, so every visitor to any of them downloads it.

    67 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: titles

  4. 4

    Update Meta Descriptions

    Why: Meta descriptions influence click-through rates.

    How: Create unique descriptions for each page rather than duplicating a single text.

    Evidence: 65 pages share the meta description "We love bringing the roots of traditional yoga to life for …", which usually means one template writes it for all of them.

    65 pages affected

    Depends on: If these pages really are the same content, the duplicate meta description is a symptom: canonicalise them to one URL instead.

    Checks: meta-descriptions

  5. 5

    Add Missing Headings

    Why: Proper headings improve structure and SEO.

    How: Insert H1 tags where missing and ensure each page has a single H1.

    Checks: headings

  6. 6

    Ensure Sitemap Coverage

    Why: A well-maintained sitemap facilitates better indexing.

    How: Update your sitemap to include all important URLs and submit 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

Your site has several critical security issues, including missing protections against man-in-the-middle attacks, clickjacking, and script injection. Implementing standard security headers and restricting API keys will help protect your users and your site. Prioritize these fixes to strengthen your website's security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors who type the address without HTTPS can be intercepted on the first request.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your HTTP response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of a CSP allows scripts and styles to load from any source, increasing the risk of cross-site scripting attacks.

    Fix: Add a Content-Security-Policy header, e.g., 'Content-Security-Policy: default-src 'self'; script-src 'self';'.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Lack of this header makes your site vulnerable to clickjacking attacks, where attackers can overlay your content with malicious controls.

    Fix: Include 'X-Frame-Options: DENY' or use a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  4. 4

    Exposed Google API KeyMedium

    Why it matters: An exposed API key can be misused, leading to potential costs and data breaches.

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

    Evidence: Keys and secrets in page code

  5. 5

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may interpret files based on their contents, which could lead to script execution risks.

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

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive information about previous pages is leaked to third-party sites.

    Fix: Implement 'Referrer-Policy: no-referrer-when-downgrade' in your headers for better privacy.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not using a Permissions Policy allows potentially harmful features to be accessed by scripts.

    Fix: Add 'Permissions-Policy: interest-cohort=()' to limit browser features for your domain.

    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 67 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 67 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-10-04-0151 | DIY SEO Hub