Programmable

Website review, no card needed

triumph.io logo

triumph.io website review

Visit site (opens in a new tab)Reviewed 20 October 202615 issues · 77 checks

This review found 15 issues worth fixing on triumph.io, 3 of them high impact, across 77 checks. The most urgent: largest Contentful Paint: 7.3 s. 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

87B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.0 s1.4 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.6 s
May 16, 20261.7 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
142 ms103 msMay 2Oct 17137 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026111 ms
May 9, 2026111 ms
May 16, 2026107 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026119 ms
Jun 13, 2026117 ms
Jun 20, 2026119 ms
Jun 27, 2026113 ms
Jul 4, 2026113 ms
Jul 11, 2026120 ms
Jul 18, 2026122 ms
Jul 25, 2026128 ms
Aug 1, 2026131 ms
Aug 8, 2026137 ms
Aug 15, 2026135 ms
Aug 22, 2026130 ms
Aug 29, 2026128 ms
Sep 5, 2026122 ms
Sep 12, 2026120 ms
Sep 19, 2026120 ms
Sep 26, 2026125 ms
Oct 3, 2026133 ms
Oct 10, 2026137 ms
Oct 17, 2026137 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

triumph.io (opens in a new tab)
Full-page screenshot of triumph.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix59

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59 (desktop: 65). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 123 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • 3 third-party services on the page

    3 third-party services load with your homepage (cdn-cookieyes.com, Marketo and monsido.com), adding 46 KiB and 24 ms of main-thread time.

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    5 KiB

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

2 checks passed

  • Main-thread work: 1.4 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Triumph service network.”.

  • Total Blocking Time: 663 ms

    663 ms

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

  • Time to Interactive: 7.4 s

    7.4 s

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

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

    +23%

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

9 checks passed

  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 137 ms

    137 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 639 ms

    639 ms

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.18 g

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

4 checks passed

  • Page weight: 647 KiB in 42 requests

    647 KiB

    Your homepage downloads 647 KiB in 42 requests on a phone: scripts 415 KiB (13), images 94 KiB (16) and fonts 48 KiB (1). 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.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

Google 98100

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9292

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • 131 internal links, 32 external

    The homepage links to 131 pages on triumph.io and 32 external pages.

7 checks passed

  • Meta description: 154 characters

    Your meta description is 154 characters: “Experience the Triumph Network, a unified trucking platform modernizing and simplifying freight transactions for carrie…”.

  • One H1 headline

    Your main headline reads: “TRANSACT CONFIDENTLY”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Triumph Network | Freight Payments, Banking, and Intelligence”.

  • Canonical URL set

    The canonical URL is https://triumph.io/.

  • 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://static.triumph.io/sitemap.xml.

AI search readiness

1 to fix88

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://triumph.io/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.

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

  • Text is in the HTML

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

Other pages

1 to fix98

  • 2 pages share a meta description

    https://triumph.io/carrier and https://triumph.io/carrier/payments use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 57 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

Google 100100

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

  • No map or directions link

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

  • About 848 words of copy

    The homepage carries about 848 words of visible text.

7 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Started”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply for Factoring + LoadPay”, “Get Started” and “Learn More”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 1 customer or partner logo.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 triumph.io, 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
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on triumph.io, including 8 speed issues, 3 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