Scanned sites / www.tebra.com / 2026-10-01-1043

www.tebra.com scan from 10/1/2026, 10:43:19 AM

Scan 2026-10-01-1043

Scanned 10/1/2026, 10:43:19 AM, finished 10/2/2026, 6:01:17 AM. Found on page 4 of brave web search results

Site: https://www.tebra.com/

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

82/ 100Good

On October 1, 2026 the Site Spider crawled 4917 pages and 547 assets of www.tebra.com, starting from https://www.tebra.com/. It scored 82 out of 100, a good result. 12 of 16 checks found something to fix, led by title tags (3,573), heavy assets (13), sitemap coverage (2,385); 2 checks passed. Most of the points went to title tags (−7.5), heavy assets (−6), sitemap coverage (−3). 2 checks found something the score does not count, listed as noted. 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
4917
Assets fetched
547
Status
Completed
Checks with issues
12 of 16
CoverageJob finished, partial coverage

5,464 of 6,000 discovered URLs were fetched, 536 blocked by robots.txt, 99,135 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, 8327 left unchecked.

  • Title tags3,573 issues
    3573 of 4275 pages have title issues. 495 noindex or canonicalized pages excluded.
    −7.5 points
  • Meta descriptions840 issues
    840 of 4275 pages have meta description issues. 495 noindex or canonicalized pages excluded.
    −1.4 points
  • Headings27 issues
    27 of 4275 pages have heading issues. 495 noindex or canonicalized pages excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites1 issue
    1 destination answered with an error, 37 could not be determined (timeouts, rate limits or refusals), 8327 were left unchecked by the per-scan cap, of 300 destinations checked.
  • Redirects150 issues
    155 redirecting URLs, 3 of them chained.
    −0.1 points
  • Non-200 responses155 noted
    155 URLs did not return a 2xx response. 147 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.
  • Indexability59 issues
    59 of 4741 indexable pages have indexability warnings. 29 pages noindex by design.
    −0.1 points
  • Image alt text11 issues
    11 of 89111 image references have no alt attribute. 19263 use an empty alt (decorative), which is fine.
  • Heavy assets13 issues
    13 assets larger than 500 KB among 547 fetched assets. 3 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages3 issues
    3 pages have no internal links pointing at them.
  • Sitemap coverage2,385 issues
    No sitemap found. Tried: https://www.tebra.com/sitemap.xml (301). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link countsOK
    Internal link counts for 500 pages.
  • Thin content5 issues
    5 of 4275 pages have fewer than 200 words. 495 noindex or canonicalized pages excluded.
  • Duplicate content4 issues
    2 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1715 sites, median 80%, average 79%

www.tebra.com scores 82%, higher than 58% of the 1715 scanned sites. See the full ranking.

0511020%: 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%: 0 sites40%: 2 sites41%: 1 site42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 5 sites50%: 4 sites51%: 5 sites52%: 7 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 5 sites57%: 6 sites58%: 11 sites59%: 6 sites60%: 9 sites61%: 11 sites62%: 15 sites63%: 15 sites64%: 10 sites65%: 19 sites66%: 19 sites67%: 33 sites68%: 26 sites69%: 24 sites70%: 38 sites71%: 36 sites72%: 48 sites73%: 48 sites74%: 46 sites75%: 54 sites76%: 70 sites77%: 60 sites78%: 81 sites79%: 61 sites80%: 82 sites81%: 102 sites82%: 82 sites83%: 80 sites84%: 73 sites85%: 59 sites86%: 63 sites87%: 54 sites88%: 59 sites89%: 53 sites90%: 32 sites91%: 36 sites92%: 23 sites93%: 12 sites94%: 12 sites95%: 8 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 54 sites82% 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 website has some substantial SEO issues, primarily with redirects, title tags, and meta descriptions. I recommend addressing the most impactful items first, such as fixing redirects and optimizing title tags.

  1. 1

    Fix Redirects

    Why: 155 redirecting URLs can negatively impact user experience and SEO.

    How: Update the broken URLs to their final destinations, fixing the chained redirects.

    Checks: redirects

  2. 2

    Optimize Title Tags

    Why: 3573 title tag issues can hinder search engine rankings.

    How: Review and modify titles to be unique and under 60 characters for better compliance.

    Checks: titles

  3. 3

    Optimize Meta Descriptions

    Why: 840 pages with meta description issues may result in poor click-through rates.

    How: Revise meta descriptions to be compelling and under 160 characters.

    Checks: meta-descriptions

  4. 4

    Create a Sitemap

    Why: Lack of a sitemap hinders search engine indexing and discovery.

    How: Generate a sitemap.xml and submit it for Google Search Console.

    Checks: sitemap-coverage

  5. 5

    Address Heavy Assets

    Why: Large assets can slow down page loading, impacting user experience.

    How: Optimize the mentioned assets to reduce sizes or adjust loading methods.

    Checks: heavy-assets

  6. 6

    Resolve Indexability Warnings

    Why: 59 indexable pages with issues could confuse search engines.

    How: Fix canonical tags and ensure pages are indexed correctly.

    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

Your website has several security issues that need addressing, primarily regarding HTTP headers. Key measures like HTTP Strict Transport Security (HSTS) and clickjacking protections are absent, potentially exposing users to attacks. Additionally, outdated JavaScript libraries and leaked API keys could pose security risks. Implementing the recommendations below will enhance your site's security significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request if they type the site address without https://.

    Fix: Add the header `Strict-Transport-Security: max-age=31536000; includeSubDomains` to your HTML responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Absence of Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options or CSP frame-ancestors, your pages can be embedded in frames by malicious sites.

    Fix: Include the header `X-Frame-Options: DENY` in your HTML responses.

    Evidence: Clickjacking protection

  3. 3

    Outdated JavaScript LibraryMedium

    Why it matters: Using jQuery 1.12.4 introduces known vulnerabilities that could be exploited.

    Fix: Upgrade to jQuery version 3.5.0 or higher to mitigate risks.

    Evidence: Vulnerable JavaScript libraries

  4. 4

    Leaked Google API KeyMedium

    Why it matters: Exposing an API key can lead to unauthorized use and potential costs or data breaches.

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

    Evidence: Keys and secrets in page code

  5. 5

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers may execute files as scripts incorrectly.

    Fix: Include the header `X-Content-Type-Options: nosniff` in your HTML responses.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Lack of referrer policy could expose sensitive URL info when users navigate away from your site.

    Fix: Add `Referrer-Policy: no-referrer` to your HTML responses to limit referrer information.

    Evidence: Referrer policy

  7. 7

    No Permissions PolicyInfo

    Why it matters: Not having a permissions policy allows browser features to remain enabled that may not be needed.

    Fix: Set `Permissions-Policy: microphone=(), camera=()` in your HTML responses.

    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.tebra.com/ → no strict-transport-security
    • https://www.tebra.com/ehr-software → no strict-transport-security
    • https://www.tebra.com/billing-payments → no strict-transport-security
    • https://www.tebra.com/billing-payments/patient-payments → no strict-transport-security
    • https://www.tebra.com/patient-experience → no strict-transport-security
    • https://www.tebra.com/marketing → no strict-transport-security
    • https://www.tebra.com/independent-practices → no strict-transport-security
    • https://www.tebra.com/billing-payments/for-billing-companies → no strict-transport-security
    • https://www.tebra.com/specialties/family-medicine → no strict-transport-security
    • https://www.tebra.com/specialties/primary-care → no strict-transport-security
    • https://www.tebra.com/specialties/pediatrics → no strict-transport-security
    • https://www.tebra.com/specialties/psychology → no strict-transport-security
  • FoundClickjacking protectionMedium

    1314 of 4770 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.tebra.com/care/ → no x-frame-options
    • https://www.tebra.com/care/help/ → no x-frame-options
    • https://www.tebra.com/care/join/ → no x-frame-options
    • https://www.tebra.com/care/family-doctors/ → no x-frame-options
    • https://www.tebra.com/care/dentists/ → no x-frame-options
    • https://www.tebra.com/care/ob-gyns/ → no x-frame-options
    • https://www.tebra.com/care/dermatologists/ → no x-frame-options
    • https://www.tebra.com/care/podiatrists/ → no x-frame-options
    • https://www.tebra.com/care/psychiatrists/ → no x-frame-options
    • https://www.tebra.com/care/orthopedic-surgeons/ → no x-frame-options
    • https://www.tebra.com/care/physical-therapists/ → no x-frame-options
    • https://www.tebra.com/care/chiropractors/ → 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.tebra.com/ → no x-content-type-options
    • https://www.tebra.com/ehr-software → no x-content-type-options
    • https://www.tebra.com/billing-payments → no x-content-type-options
    • https://www.tebra.com/billing-payments/patient-payments → no x-content-type-options
    • https://www.tebra.com/patient-experience → no x-content-type-options
    • https://www.tebra.com/marketing → no x-content-type-options
    • https://www.tebra.com/independent-practices → no x-content-type-options
    • https://www.tebra.com/billing-payments/for-billing-companies → no x-content-type-options
    • https://www.tebra.com/specialties/family-medicine → no x-content-type-options
    • https://www.tebra.com/specialties/primary-care → no x-content-type-options
    • https://www.tebra.com/specialties/pediatrics → no x-content-type-options
    • https://www.tebra.com/specialties/psychology → 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.tebra.com/ → no referrer-policy
    • https://www.tebra.com/ehr-software → no referrer-policy
    • https://www.tebra.com/billing-payments → no referrer-policy
    • https://www.tebra.com/billing-payments/patient-payments → no referrer-policy
    • https://www.tebra.com/patient-experience → no referrer-policy
    • https://www.tebra.com/marketing → no referrer-policy
    • https://www.tebra.com/independent-practices → no referrer-policy
    • https://www.tebra.com/billing-payments/for-billing-companies → no referrer-policy
    • https://www.tebra.com/specialties/family-medicine → no referrer-policy
    • https://www.tebra.com/specialties/primary-care → no referrer-policy
    • https://www.tebra.com/specialties/pediatrics → no referrer-policy
    • https://www.tebra.com/specialties/psychology → 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.tebra.com/ → no permissions-policy
    • https://www.tebra.com/ehr-software → no permissions-policy
    • https://www.tebra.com/billing-payments → no permissions-policy
    • https://www.tebra.com/billing-payments/patient-payments → no permissions-policy
    • https://www.tebra.com/patient-experience → no permissions-policy
    • https://www.tebra.com/marketing → no permissions-policy
    • https://www.tebra.com/independent-practices → no permissions-policy
    • https://www.tebra.com/billing-payments/for-billing-companies → no permissions-policy
    • https://www.tebra.com/specialties/family-medicine → no permissions-policy
    • https://www.tebra.com/specialties/primary-care → no permissions-policy
    • https://www.tebra.com/specialties/pediatrics → no permissions-policy
    • https://www.tebra.com/specialties/psychology → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    1 library with published vulnerabilities: jQuery 1.12.4. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.12.4 in https://www.tebra.com/next-assets/scripts/forms.js: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

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

    • Google API key AIzaSy…-s (39 chars) in https://www.tebra.com/tebranew/_next/static/chunks/5317-df757aaaf3df09ca.js: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (5464 responses)
    • x-powered-by: WP Engine Headless Platform (1681 responses)
    • x-powered-by: WP Engine (83 responses)
  • NoteThird-party scripts

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

    • info1.patientpop.com (6 script tags)
    • cdn.jsdelivr.net (6 script tags)
    • cdn.bizible.com (6 script tags)
    • fast.wistia.com (2 script tags)
    • prod.impartner.live (1 script tag)
7 checks passed
  • OKHTTPS

    All 4770 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 1314 of 4770 pages.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

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

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

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.tebra.com

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

Own www.tebra.com?

www.tebra.com scan 2026-10-01-1043 | DIY SEO Hub