Website review, no card needed

Telnyx logo

telnyx.com website review

Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 82 checks

This review found 35 issues worth fixing on telnyx.com, 13 of them high impact, across 82 checks. The most urgent: main-thread work: 41.8 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Telnyx

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

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

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.3 sMay 30Nov 143.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.5 s
Oct 31, 20263.6 s
Nov 7, 20263.6 s
Nov 14, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
525 ms293 msMay 30Nov 14498 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026320 ms
Jun 6, 2026344 ms
Jun 13, 2026356 ms
Jun 20, 2026369 ms
Jun 27, 2026371 ms
Jul 4, 2026367 ms
Jul 11, 2026357 ms
Jul 18, 2026349 ms
Jul 25, 2026350 ms
Aug 1, 2026346 ms
Aug 8, 2026351 ms
Aug 15, 2026354 ms
Aug 22, 2026352 ms
Aug 29, 2026345 ms
Sep 5, 2026335 ms
Sep 12, 2026329 ms
Sep 19, 2026334 ms
Sep 26, 2026346 ms
Oct 3, 2026369 ms
Oct 10, 2026396 ms
Oct 17, 2026411 ms
Oct 24, 2026421 ms
Oct 31, 2026436 ms
Nov 7, 2026462 ms
Nov 14, 2026498 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

Full-page screenshot of telnyx.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. telnyx.com at 1.5 s1.5 s
  2. telnyx.com at 3.1 s3.1 s
  3. telnyx.com at 4.6 s4.6 s
  4. telnyx.com at 6.1 s6.1 s
  5. telnyx.com at 7.7 s7.7 s
  6. telnyx.com at 9.2 s9.2 s
  7. telnyx.com at 10.7 s10.7 s
  8. telnyx.com at 12.3 s12.3 s

Speed

10 to fix30
  • Main-thread work: 41.8 s

    A phone's processor spends 41.8 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    1.9 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • cloudfront.net adds 1.8 s

    1.8 s

    cloudfront.net costs a phone 1.8 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 30

    30/100

    Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 5.1 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (cloudfront.net, Optanon and reddit and others), adding 2.4 MB and 2.1 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 777 KiB

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

  • Improve image delivery

    500 ms · 93 KiB

    3 images could be 93 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • 1,952 HTML elements

    The page has 1,952 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 79 KiB

    Polyfills for old browsers add 79 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 16.8 s

    16.8 s

    Your largest element takes 16.8 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Total Blocking Time: 18.3 s

    18.3 s

    Scripts block taps and scrolling for 18.3 s in total while the page loads. Good is under 200 ms.

  • Time to Interactive: 45.1 s

    45.1 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 401 ms

    401 ms

    Real visitors wait 401 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 45% slower for real visitors

    +45%

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

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

    +46%

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

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 905 ms

    905 ms

    Real visitors wait 905 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

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

2 checks passed
  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.098

    0.098

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

Images and page weight

2 to fix60
  • Page weight: 6.1 MB in 222 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 222 requests on a phone: scripts 3.0 MB (107), media 2.5 MB (3) and images 280 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    42 KiB

    1 image is downloaded at several times the size a phone draws it, for example hero-poster.webp at 1,920 px wide, shown at 334 px. Resized copies would save about 42 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.74 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

4 to fixGoogle 9595
  • <dt> and <dd> elements must be contained by a <dl> (8 elements)

    <dt> and <dd> elements must be contained by a <dl>: 8 elements on the page fail this check, rated serious by axe-core.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 67 images in the HTML carry an alt attribute.

  • 57 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • Meta description is long (202 characters)

    Your meta description is 202 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 205 internal links, 44 external

    The homepage links to 205 pages on telnyx.com and 44 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Infrastructure for real-time agents.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Infrastructure for realtime agents | Telnyx”.

  • Canonical URL set

    The canonical URL is https://telnyx.com/.

  • Structured data in place

    Structured data found: AggregateRating, BreadcrumbList, ItemList, Organization and Service.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://telnyx.com/llms.txt (18 KiB, 86 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    14 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,449 words of copy

    The homepage carries about 1,449 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START BUILDING”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Pricing”, “Contact sales” and “Sign up”.

  • Social proof on the page

    Social proof on the homepage: 12 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, LinkedIn Insight, Meta Pixel and Reddit Pixel and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 5 of them by other companies (measured from a US location before any click).

  • 35 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

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

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 telnyx.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
64 open roles
Teams
Sales (45), Software Engineering (7), Infrastructure Engineering (2), Marketing (2)
Job board
greenhouse

Company

Employees
110

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on telnyx.com, including 22 speed issues, 2 SEO issues and 3 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