Website review, no card needed
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
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.6 s |
| Nov 7, 2026 | 3.6 s |
| Nov 14, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 320 ms |
| Jun 6, 2026 | 344 ms |
| Jun 13, 2026 | 356 ms |
| Jun 20, 2026 | 369 ms |
| Jun 27, 2026 | 371 ms |
| Jul 4, 2026 | 367 ms |
| Jul 11, 2026 | 357 ms |
| Jul 18, 2026 | 349 ms |
| Jul 25, 2026 | 350 ms |
| Aug 1, 2026 | 346 ms |
| Aug 8, 2026 | 351 ms |
| Aug 15, 2026 | 354 ms |
| Aug 22, 2026 | 352 ms |
| Aug 29, 2026 | 345 ms |
| Sep 5, 2026 | 335 ms |
| Sep 12, 2026 | 329 ms |
| Sep 19, 2026 | 334 ms |
| Sep 26, 2026 | 346 ms |
| Oct 3, 2026 | 369 ms |
| Oct 10, 2026 | 396 ms |
| Oct 17, 2026 | 411 ms |
| Oct 24, 2026 | 421 ms |
| Oct 31, 2026 | 436 ms |
| Nov 7, 2026 | 462 ms |
| Nov 14, 2026 | 498 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
Speed
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 MBAbout 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 scloudfront.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 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 30
30/100Your 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 KiB28 files are served with short cache lifetimes, so returning visitors download them again (777 KiB).
Improve image delivery
500 ms · 93 KiB3 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 KiBPolyfills 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 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 sYour 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 sScripts 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 sThe page becomes fully interactive after 45.1 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal 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 msReal 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 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 905 ms
905 msReal 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 sThe 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.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.098
0.098The layout barely moves while loading (CLS 0.098, good is under 0.1).
Images and page weight
Page weight: 6.1 MB in 222 requests
6.1 MBYour 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 KiB1 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 gBy 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
<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
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
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
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
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
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
7Before 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
25Opening 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
- Careers page
- telnyx.com/careers (opens in a new tab)
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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.