Scanned sites / www.ridetime.ca

SEO report for www.ridetime.ca DR 28

The latest Site Spider scan of www.ridetime.ca, with 1 scan on record. Each scan is at its own address, for example /domain/www-ridetime-ca/2026-09-13-1637.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-09-13 16:37:31 UTC, finished 2026-09-13 20:06:22 UTC. Found on page 5 of brave web search results

Site: https://www.ridetime.ca/

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

84/ 100Good

On September 13, 2026 the Site Spider crawled 5000 pages and 1000 assets of www.ridetime.ca, starting from https://www.ridetime.ca/. It scored 84 out of 100, a good result. 13 of 27 checks found something to fix, led by heavy assets (815), title tags (1,386), meta descriptions (1,590); 5 checks passed. Most of the points went to heavy assets (−6), title tags (−3.6), meta descriptions (−3.3). 9 checks found something the score does not count, listed as noted. 10 checks were not run because the crawl fetched nothing for them. 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 and 2 low findings. See the security findings ↓

Pages crawled
5000
Assets fetched
1000
Status
Completed
Checks with issues
13 of 27
CoverageJob finished, partial coverage

6,000 of 6,000 discovered URLs were fetched, 31,435 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. 300 link destinations on other sites were checked, 182 left unchecked.

  • Title tags1,386 issues
    1386 of 1967 pages have title issues. 1877 noindex or canonicalized pages excluded.
    −3.6 points
  • Meta descriptions1,590 issues
    1590 of 1967 pages have meta description issues. 1877 noindex or canonicalized pages excluded.
    −3.3 points
  • Headings7 issues
    7 of 1967 pages have heading issues. 1877 noindex or canonicalized pages excluded.
  • Broken links15 issues
    88 internal links point at 15 broken URLs.
    −0.1 points
  • Links to other sites22 issues
    22 destinations answered with an error, 152 could not be determined (timeouts, rate limits or refusals), 182 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.2 points
  • Redirects1,103 issues
    1104 redirecting URLs, 9 of them chained.
    −1.1 points
  • Non-200 responses53 issues
    1160 URLs did not return a 2xx response. 1156 of them are pages, 53 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability4 issues
    4 of 3783 indexable pages have indexability warnings. 61 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
  • Image alt text3,890 issues
    3890 of 47425 image references have no alt attribute. 18371 use an empty alt (decorative), which is fine.
    −0.5 points
  • Heavy assets815 issues
    815 assets larger than 500 KB among 1000 fetched assets.
    −6 points
  • Orphan pages831 issues
    831 pages have no internal links pointing at them.
    −0.9 points
  • Sitemap coverage237 issues
    5 sitemaps listing 1771 URLs: 230 crawled pages missing, 4 listed URLs broken or redirecting, 2 reachable only via the sitemap. 27 listed URLs not crawled within the 5000-page budget.
    −0.4 points
  • Internal link counts313 noted
    Internal link counts for 500 pages; 313 worth a look.
  • Thin contentOK
    0 of 1967 pages have fewer than 200 words. 1877 noindex or canonicalized pages excluded.
  • Duplicate content53 issues
    2 groups of pages with identical HTML.
    −0.1 points
  • URL format1,898 noted
    1898 of 5000 page URLs are harder to read, share or cache than they need to be.
  • Canonicals1,876 noted
    1876 of 3844 pages have a canonical worth checking.
  • Robots directives3,844 noted
    3844 pages carry a robots directive; 0 carry none.
  • Anchor text18 noted
    18 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1,600 noted
    1600 of 1967 pages could use the title, heading and snippet space better. 1877 noindex or canonicalized pages excluded.
  • Image weight and alt length982 noted
    970 images over 100 KB; 12 with alt text over 100 characters.
  • Response anomalies47 noted
    47 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 3844 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 6000 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 3844 pages; 3695 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed Insights3 noted
    Mobile performance 91 on average across 5 pages; 3 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2873 sites, median 80%, average 79%

www.ridetime.ca scores 84%, higher than 65% of the 2873 scanned sites. See the full ranking.

0751500%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 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%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites84% 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

The site has several technical SEO issues, including broken links, excessive redirects, and problems with title tags and meta descriptions. Prioritizing fixes for these will improve user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: Helps prevent 404 errors and improves user experience.

    How: Identify the broken URLs and either remove or update the internal links pointing to them.

    Checks: broken-links

  2. 2

    Reduce Redirects

    Why: Minimizing redirects enhances page load speed and improves crawl efficiency.

    How: Replace chained URLs with direct links, and ensure that any unnecessary redirects are eliminated.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: Fixing these URLs aids in crawling and ranking.

    How: Audit 1160 URLs for server issues and resolve those returning errors.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: Improving titles boosts CTR and relevance in search results.

    How: Ensure all title tags are concise (50-60 characters) and relevant to their pages.

    Checks: titles

  5. 5

    Enhance Meta Descriptions

    Why: Better meta descriptions can increase click-through rates.

    How: Revise meta descriptions to be unique, engaging, and within the 150-160 character limit.

    Checks: meta-descriptions

  6. 6

    Resolve Indexability Issues

    Why: Ensures the right pages are indexed for search visibility.

    How: Check the 3 pages with warnings and adjust their indexing settings as needed.

    Checks: indexability

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 exhibits several security shortcomings, notably missing critical HTTP response headers that protect against attacks like clickjacking and resource theft. Immediate remediation of these vulnerabilities is recommended to safeguard user data and enhance site security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows interception on the first request if the user types the address without HTTPS.

    Fix: Add the header: Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP leaves the site vulnerable to code injection attacks.

    Fix: Implement a CSP header: Content-Security-Policy: default-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Without this, pages can be embedded in a frame on another site, risking user interaction manipulation.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Leaked Google API KeyMedium

    Why it matters: An API key found in public code can be exploited if not properly restricted.

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

    Evidence: Keys and secrets in page code

  5. 5

    Lack of X-Content-Type-OptionsLow

    Why it matters: Without this header, browsers may misinterpret file types, posing a risk of script execution.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  6. 6

    Mixed Content on HTTPS PagesLow

    Why it matters: Loading resources over HTTP can expose users to man-in-the-middle attacks.

    Fix: Update the URL to use HTTPS: replace http:// with https:// for resources in code.

    Evidence: Mixed content

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.ridetime.ca/ → no strict-transport-security
    • https://www.ridetime.ca/my-account/ → no strict-transport-security
    • https://www.ridetime.ca/bargain-brothers-tv-show/ → no strict-transport-security
    • https://www.ridetime.ca/ride-time-blog/ → no strict-transport-security
    • https://www.ridetime.ca/videos-resources/ → no strict-transport-security
    • https://www.ridetime.ca/about-us/ → no strict-transport-security
    • https://www.ridetime.ca/contact-us/ → no strict-transport-security
    • https://www.ridetime.ca/buy-used-cars/ → no strict-transport-security
    • https://www.ridetime.ca/buy-used-cars/?sort=created_desc → no strict-transport-security
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=913&sort=created_desc → no strict-transport-security
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=906&sort=created_desc → no strict-transport-security
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=918&sort=created_desc → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 3844 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.ridetime.ca/ → no content-security-policy
    • https://www.ridetime.ca/my-account/ → no content-security-policy
    • https://www.ridetime.ca/bargain-brothers-tv-show/ → no content-security-policy
    • https://www.ridetime.ca/ride-time-blog/ → no content-security-policy
    • https://www.ridetime.ca/videos-resources/ → no content-security-policy
    • https://www.ridetime.ca/about-us/ → no content-security-policy
    • https://www.ridetime.ca/contact-us/ → no content-security-policy
    • https://www.ridetime.ca/buy-used-cars/ → no content-security-policy
    • https://www.ridetime.ca/buy-used-cars/?sort=created_desc → no content-security-policy
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=913&sort=created_desc → no content-security-policy
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=906&sort=created_desc → no content-security-policy
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=918&sort=created_desc → no content-security-policy
  • FoundClickjacking protectionMedium

    3 of 3844 HTML pages send 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.ridetime.ca/ → no x-frame-options
    • https://www.ridetime.ca/bargain-brothers-tv-show/ → no x-frame-options
    • https://www.ridetime.ca/ride-time-blog/ → no x-frame-options
    • https://www.ridetime.ca/videos-resources/ → no x-frame-options
    • https://www.ridetime.ca/about-us/ → no x-frame-options
    • https://www.ridetime.ca/contact-us/ → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/ → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/?sort=created_desc → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=913&sort=created_desc → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=906&sort=created_desc → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=918&sort=created_desc → no x-frame-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=933&sort=created_desc → 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.ridetime.ca/ → no x-content-type-options
    • https://www.ridetime.ca/my-account/ → no x-content-type-options
    • https://www.ridetime.ca/bargain-brothers-tv-show/ → no x-content-type-options
    • https://www.ridetime.ca/ride-time-blog/ → no x-content-type-options
    • https://www.ridetime.ca/videos-resources/ → no x-content-type-options
    • https://www.ridetime.ca/about-us/ → no x-content-type-options
    • https://www.ridetime.ca/contact-us/ → no x-content-type-options
    • https://www.ridetime.ca/buy-used-cars/ → no x-content-type-options
    • https://www.ridetime.ca/buy-used-cars/?sort=created_desc → no x-content-type-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=913&sort=created_desc → no x-content-type-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=906&sort=created_desc → no x-content-type-options
    • https://www.ridetime.ca/buy-used-cars/?filter%5Bpa_body-type%5D=918&sort=created_desc → no x-content-type-options
  • FoundMixed contentLow

    1 resource on HTTPS pages are loaded over plain HTTP.

    • https://www.ridetime.ca/blog/loan-buddies-four-great-reasons-to-have-… loads image http://38.media.tumblr.com/74b98ea322b622e3bb4ea53381a49787/tumblr_n1i4c7dYtI1tooympo1_40…
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…2s (39 chars) in https://www.ridetime.ca/: 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 10 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.)

    • www.googletagmanager.com (79 script tags)
    • news.google.com (40 script tags)
    • cdnjs.cloudflare.com (40 script tags)
    • storage.googleapis.com (39 script tags)
    • use.typekit.net (39 script tags)
    • maps.googleapis.com (1 script tag)
    • challenges.cloudflare.com (2 script tags)
    • js.hsforms.net (6 script tags)
    • apis.google.com (2 script tags)
    • platform.linkedin.com (2 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin/
5 checks passed, 3 not applicable
  • OKHTTPS

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

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    1 library version 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.

  • Not applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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.

Earlier scans of www.ridetime.ca

No other scans of this site yet.

Sites scoring near www.ridetime.ca

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling www.ridetime.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own www.ridetime.ca?