Scanned sites / runyowa.com / 2026-10-01-0943

runyowa.com scan from 2026-10-01 09:43:06 UTC DR 2

A newer scan exists. See the latest report for runyowa.com.

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

Scan 2026-10-01-0943

Scanned 2026-10-01 09:43:06 UTC, finished 2026-10-01 19:12:49 UTC. Found on page 5 of brave web search results

Site: https://runyowa.com/

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

80/ 100Good

On October 1, 2026 the Site Spider crawled 286 pages and 557 assets of runyowa.com, starting from https://runyowa.com/. It scored 80 out of 100, a good result. 11 of 27 checks found something to fix, led by meta descriptions (232), heavy assets (10), title tags (109); 8 checks passed. Most of the points went to meta descriptions (−6.7), heavy assets (−6), title tags (−3.9). 8 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
286
Assets fetched
557
Status
Completed
Checks with issues
11 of 27
CoverageComplete crawl

843 of 843 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 48 link destinations on other sites were checked.

  • Title tags109 issues
    109 of 257 pages have title issues. 22 noindex or canonicalized pages excluded.
    −3.9 points
  • Meta descriptions232 issues
    232 of 257 pages have meta description issues. 22 noindex or canonicalized pages excluded.
    −6.7 points
  • Headings1 issue
    1 of 257 pages have heading issues. 22 noindex or canonicalized pages excluded.
  • Broken links1 issue
    2 internal links point at 1 broken URL.
    −0.1 points
  • Links to other sites3 issues
    3 destinations answered with an error, 22 could not be determined (timeouts, rate limits or refusals), of 48 destinations checked.
    −0.4 points
  • Redirects3 issues
    4 redirecting URLs, 0 of them chained.
  • Non-200 responses3 issues
    7 URLs did not return a 2xx response. 7 of them are pages, 3 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 257 indexable pages have indexability warnings. 22 pages noindex by design.
  • Image alt textOK
    0 of 1661 image references have no alt attribute. 234 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 557 fetched assets.
    −6 points
  • Orphan pages17 issues
    17 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage122 issues
    7 sitemaps listing 156 URLs: 103 crawled pages missing, 2 listed URLs broken or redirecting, 17 reachable only via the sitemap.
    −2.6 points
  • Internal link counts123 noted
    Internal link counts for 279 pages; 123 worth a look.
  • Thin content1 issue
    1 of 257 pages have fewer than 200 words. 22 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format6 noted
    6 of 286 page URLs are harder to read, share or cache than they need to be.
  • CanonicalsOK
    0 of 279 pages have a canonical worth checking.
  • Robots directives279 noted
    279 pages carry a robots directive; 0 carry none.
  • Anchor text106 noted
    106 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure24 noted
    24 of 257 pages could use the title, heading and snippet space better. 22 noindex or canonicalized pages excluded.
  • Image weight and alt length27 noted
    27 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies1 noted
    1 URL 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 279 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 843 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 279 pages; 245 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 Insights5 noted
    Mobile performance 72 on average across 5 pages; 5 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 scan sits among all scanned sites

2909 sites, median 80%, average 79%

runyowa.com scores 80%, higher than 47% of the 2909 scanned sites. See the full ranking.

0761520%: 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%: 2 sites37%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites80% 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 (rules v4). 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.

Your site's health is good but there are some key areas to improve for better SEO performance. Focus on fixing broken links, enhancing title tags and meta descriptions, and resolving non-200 responses.

  1. 1

    Fix Broken Links

    Why: Broken links can harm user experience and SEO rankings.

    How: Update the two internal links pointing to broken URLs or remove them.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: Pages returning errors can deter visitors and affect your site’s credibility.

    How: Fix or remove the 7 URLs with non-200 responses, ensuring they load correctly.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Improving title tags can enhance click-through rates from search results.

    How: Revise the 109 pages with title issues, ensuring they are unique and within recommended lengths.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Meta descriptions are essential for attracting clicks from search results.

    How: Write meta descriptions for the 232 pages that lack them, making them informative and keyword-rich.

    Checks: meta-descriptions

  5. 5

    Fix Headings Issues

    Why: Proper heading structure assists user navigation and SEO.

    How: Correct the page with multiple H1 tags to ensure only one H1 tag is used.

    Checks: headings

  6. 6

    Address Orphan Pages

    Why: Orphan pages do not contribute to your site's link structure and can become outdated.

    How: Add internal links to the 17 orphan pages to improve their visibility.

    Checks: orphan-pages

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 runyowa.com lacks several important security headers, making it vulnerable to interception and attacks. Key improvements include implementing HTTP Strict Transport Security and Content Security Policy. Addressing these issues will enhance user protection and reduce potential risks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted when accessing the site without HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: The lack of CSP allows unrestricted loading of scripts and styles, increasing the risk of XSS attacks.

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site can be embedded in a frame on other sites, vulnerable to clickjacking.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may execute files as scripts based on content rather than type.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of this header allows full URLs with query strings to be sent to other sites, risking data leakage.

    Fix: Add the header: Referrer-Policy: no-referrer

    Evidence: Referrer policy

  6. 6

    Server Version ExposureLow

    Why it matters: Revealing server and framework versions helps attackers identify vulnerabilities.

    Fix: Remove or modify server banner settings. Consider using: Server: My Custom Server.

    Evidence: Software version disclosure

  7. 7

    Mixed Content IssueLow

    Why it matters: Loading resources over HTTP can compromise the security of HTTPS pages.

    Fix: Update the images to HTTPS from: http://buinfinitytech.com/law/wp-content/uploads/2023/03/Screenshot-2023-03-16-135326.jpg to https.

    Evidence: Mixed content

  8. 8

    Missing Permissions-Policy HeaderInfo

    Why it matters: The lack of this header leaves browser features enabled that may not be used and could be exploited.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()

    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://runyowa.com/ → no strict-transport-security
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no strict-transport-security
    • https://runyowa.com/civil-litigation/ → no strict-transport-security
    • https://runyowa.com/automobile-accidents/ → no strict-transport-security
    • https://runyowa.com/wrongful-death/ → no strict-transport-security
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no strict-transport-security
    • https://runyowa.com/administrative-law-and-tribunals/ → no strict-transport-security
    • https://runyowa.com/privacy-breaches/ → no strict-transport-security
    • https://runyowa.com/civil-fraud/ → no strict-transport-security
    • https://runyowa.com/contract-dispute/ → no strict-transport-security
    • https://runyowa.com/insurance-disputes/ → no strict-transport-security
    • https://runyowa.com/professional-discipline/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 279 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://runyowa.com/ → no content-security-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no content-security-policy
    • https://runyowa.com/civil-litigation/ → no content-security-policy
    • https://runyowa.com/automobile-accidents/ → no content-security-policy
    • https://runyowa.com/wrongful-death/ → no content-security-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no content-security-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no content-security-policy
    • https://runyowa.com/privacy-breaches/ → no content-security-policy
    • https://runyowa.com/civil-fraud/ → no content-security-policy
    • https://runyowa.com/contract-dispute/ → no content-security-policy
    • https://runyowa.com/insurance-disputes/ → no content-security-policy
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no x-frame-options
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no x-frame-options
    • https://runyowa.com/civil-litigation/ → no x-frame-options
    • https://runyowa.com/automobile-accidents/ → no x-frame-options
    • https://runyowa.com/wrongful-death/ → no x-frame-options
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no x-frame-options
    • https://runyowa.com/administrative-law-and-tribunals/ → no x-frame-options
    • https://runyowa.com/privacy-breaches/ → no x-frame-options
    • https://runyowa.com/civil-fraud/ → no x-frame-options
    • https://runyowa.com/contract-dispute/ → no x-frame-options
    • https://runyowa.com/insurance-disputes/ → no x-frame-options
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no x-content-type-options
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no x-content-type-options
    • https://runyowa.com/civil-litigation/ → no x-content-type-options
    • https://runyowa.com/automobile-accidents/ → no x-content-type-options
    • https://runyowa.com/wrongful-death/ → no x-content-type-options
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no x-content-type-options
    • https://runyowa.com/administrative-law-and-tribunals/ → no x-content-type-options
    • https://runyowa.com/privacy-breaches/ → no x-content-type-options
    • https://runyowa.com/civil-fraud/ → no x-content-type-options
    • https://runyowa.com/contract-dispute/ → no x-content-type-options
    • https://runyowa.com/insurance-disputes/ → no x-content-type-options
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no referrer-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no referrer-policy
    • https://runyowa.com/civil-litigation/ → no referrer-policy
    • https://runyowa.com/automobile-accidents/ → no referrer-policy
    • https://runyowa.com/wrongful-death/ → no referrer-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no referrer-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no referrer-policy
    • https://runyowa.com/privacy-breaches/ → no referrer-policy
    • https://runyowa.com/civil-fraud/ → no referrer-policy
    • https://runyowa.com/contract-dispute/ → no referrer-policy
    • https://runyowa.com/insurance-disputes/ → no referrer-policy
    • https://runyowa.com/professional-discipline/ → 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://runyowa.com/ → no permissions-policy
    • https://runyowa.com/sports-misconduct-complaints-disputes/ → no permissions-policy
    • https://runyowa.com/civil-litigation/ → no permissions-policy
    • https://runyowa.com/automobile-accidents/ → no permissions-policy
    • https://runyowa.com/wrongful-death/ → no permissions-policy
    • https://runyowa.com/agriculture-farming-dispute-resolution/ → no permissions-policy
    • https://runyowa.com/administrative-law-and-tribunals/ → no permissions-policy
    • https://runyowa.com/privacy-breaches/ → no permissions-policy
    • https://runyowa.com/civil-fraud/ → no permissions-policy
    • https://runyowa.com/contract-dispute/ → no permissions-policy
    • https://runyowa.com/insurance-disputes/ → no permissions-policy
    • https://runyowa.com/professional-discipline/ → no permissions-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • server: Apache (843 responses)
    • x-powered-by: PHP/8.1.34 (293 responses)
  • FoundMixed contentLow

    2 resources on HTTPS pages are loaded over plain HTTP.

    • https://runyowa.com/elementor-landing-page-2209/ loads image http://buinfinitytech.com/law/wp-content/uploads/2023/03/Screenshot-2023-03-16-135326.jpg
    • https://runyowa.com/elementor-landing-page-2209/ loads image http://buinfinitytech.com/law/wp-content/uploads/2023/03/Screenshot-2023-03-16-135326.jpg
  • NoteThird-party scripts

    Scripts run from 2 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 (40 script tags)
    • www.google.com (15 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, 1 not applicable
  • OKHTTPS

    All 279 crawled pages were served over HTTPS.

  • OKForms over HTTPS

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

  • OKVulnerable JavaScript libraries

    2 library versions 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.

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

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

Own runyowa.com?