Programmable

Website review, no card needed

teletracking.com logo

teletracking.com website review

Visit site (opens in a new tab)Reviewed 1 November 202624 issues · 73 checks

This review found 24 issues worth fixing on teletracking.com, 8 of them high impact, across 73 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

85B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.7 s1.3 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.5 s
May 23, 20261.7 s
May 30, 20262.0 s
Jun 6, 20262.3 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.5 s
Jul 25, 20263.0 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
143 ms68 msMay 16Oct 377 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202687 ms
May 23, 2026113 ms
May 30, 2026122 ms
Jun 6, 2026127 ms
Jun 13, 2026134 ms
Jun 20, 2026129 ms
Jun 27, 2026132 ms
Jul 4, 2026133 ms
Jul 11, 2026128 ms
Jul 18, 2026134 ms
Oct 3, 202677 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

www.teletracking.com (opens in a new tab)
Full-page screenshot of teletracking.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teletracking.com at 0.4 s0.4 s
  2. teletracking.com at 0.8 s0.8 s
  3. teletracking.com at 1.1 s1.1 s
  4. teletracking.com at 1.5 s1.5 s
  5. teletracking.com at 1.9 s1.9 s
  6. teletracking.com at 2.3 s2.3 s
  7. teletracking.com at 2.6 s2.6 s
  8. teletracking.com at 3.0 s3.0 s

Speed

5 to fix79

  • Improve image delivery

    1.1 s · 186 KiB

    1 image could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.1 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 79

    79/100

    Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    450 ms · 117 KiB

    22 files are served with short cache lifetimes, so returning visitors download them again (117 KiB).

  • nxedge.io adds 170 ms

    170 ms

    nxedge.io costs a phone 170 ms of main-thread work and 391 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 4 third-party services on the page

    4 third-party services load with your homepage (nxedge.io, cdn-cookieyes.com and Google Fonts and others), adding 477 KiB and 225 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 23 KiB

    About 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 245 ms of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix78

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Carilion Clinic Transfer Command Center on TeleTracking pla…”.

  • Largest content (LCP) got 56% slower for real visitors

    +56%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.2 s

    2.2 s

    The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 4.7 s

    4.7 s

    The page becomes fully interactive after 4.7 s. Good is under 3.8 s.

  • Speed Index: 3.8 s

    3.8 s

    Visually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 87 ms to 77 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed

  • Cumulative Layout Shift: 0.017

    0.017

    The layout barely moves while loading (CLS 0.017, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90

  • 1 image far larger than shown

    200 KiB

    1 image is downloaded at several times the size a phone draws it, for example Jason-Broll-Selects.00_43_42_10.Still017-scaled.webp at 2,560 px wide, shown at 309 px. Resized copies would save about 200 KiB.

  • About 0.1 g of CO₂ per visit

    0.14 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.14 g of CO₂e: 16.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed

  • Page weight: 509 KiB in 37 requests

    509 KiB

    Your homepage downloads 509 KiB in 37 requests on a phone: images 239 KiB (8), scripts 156 KiB (17) and fonts 47 KiB (2). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8793

  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

2 checks passed

  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9295

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 105 internal links, 15 external

    The homepage links to 105 pages on teletracking.com and 15 external pages.

7 checks passed

  • Meta description: 156 characters

    Your meta description is 156 characters: “At TeleTracking, we build solutions to coordinate care and improve workflows so your healthcare system can focus on the…”.

  • One H1 headline

    Your main headline reads: “The Operations Platform for Hospitals and Health Systems”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “TeleTracking - Integrated Healthcare Operations”.

  • Canonical URL set

    The canonical URL is https://www.teletracking.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.teletracking.com/sitemap.xml.

AI search readiness

100

  • No llms.txt

    There is no https://www.teletracking.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (662 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81

  • 2 pages share a title

    https://www.teletracking.com/healthcare-operations-iq-platform/data-analytics and https://www.teletracking.com/healthcare-operations-iq-platform/decision-iq all use the title “Patient & Healthcare Analytics Platform - TeleTracking”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.teletracking.com/healthcare-operations-iq-platform/access, https://www.teletracking.com/healthcare-operations-iq-platform/throughput, https://www.teletracking.com/healthcare-operations-iq-platform/ambulatory, https://www.teletracking.com/mediatype/clientsuccess, https://www.teletracking.com/mediatype/insights and https://www.teletracking.com/news and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.teletracking.com/healthcare-operations-iq-platform/data-analytics and https://www.teletracking.com/healthcare-operations-iq-platform/decision-iq use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.teletracking.com/healthcare-operations-iq-platform/access, https://www.teletracking.com/healthcare-operations-iq-platform/throughput, https://www.teletracking.com/healthcare-operations-iq-platform/decision-iq, https://www.teletracking.com/healthcare-operations-iq-platform/ambulatory and https://www.teletracking.com/about/innovation have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.teletracking.com/news took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.

4 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    10 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67

  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 451 words of copy

    The homepage carries about 451 words of visible text.

4 checks passed

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Learn more” and “Download our eBook”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed

  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at teletracking.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Nexcess Net

Hiring

Hiring
12 open roles
Teams
Data Engineering (4), Finance and Operations (2), Finance (1), Logistics Engineering (1)
Job board
greenhouse
Careers page
www.teletracking.com/careers (opens in a new tab)

Company

Employees
220
Headquarters
Pittsburgh

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on teletracking.com, including 11 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25