Programmable

Website review, no card needed

Titan logo

titan.com website review

Visit site (opens in a new tab)Reviewed 3 November 202616 issues · 71 checks

This review found 16 issues worth fixing on titan.com, 4 of them high impact, across 71 checks. The most urgent: page weight: 10.2 MB in 52 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Titan

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

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

Site score

91A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.0 s2.2 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.5 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.8 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.4 s
Sep 26, 20263.2 s
Oct 3, 20263.0 s
Oct 10, 20262.8 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
130 ms86 msMay 16Oct 3191 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026104 ms
May 30, 2026105 ms
Jun 6, 2026103 ms
Jun 13, 202699 ms
Jun 20, 2026102 ms
Jun 27, 2026103 ms
Jul 4, 2026109 ms
Jul 11, 2026108 ms
Jul 18, 2026106 ms
Jul 25, 2026108 ms
Aug 1, 2026109 ms
Aug 8, 2026114 ms
Aug 15, 2026120 ms
Aug 22, 2026122 ms
Aug 29, 2026123 ms
Sep 5, 2026125 ms
Sep 12, 2026122 ms
Sep 19, 2026115 ms
Sep 26, 2026113 ms
Oct 3, 2026114 ms
Oct 10, 2026111 ms
Oct 17, 2026106 ms
Oct 24, 2026100 ms
Oct 31, 202691 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.titan.com (opens in a new tab)
Full-page screenshot of titan.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. titan.com at 0.6 s0.6 s
  2. titan.com at 1.2 s1.2 s
  3. titan.com at 1.7 s1.7 s
  4. titan.com at 2.3 s2.3 s
  5. titan.com at 2.9 s2.9 s
  6. titan.com at 3.5 s3.5 s
  7. titan.com at 4.1 s4.1 s
  8. titan.com at 4.7 s4.7 s

Speed

1 to fix91

  • Reduce unused JavaScript

    600 ms · 136 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    22 KiB

    Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

  • Forced reflow

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

3 checks passed

  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix100

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Time to Interactive: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

8 checks passed

  • 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: 90 ms

    90 ms

    Real visitors wait 90 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.7 s

    1.7 s

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

  • Largest content (LCP) got 29% faster for real visitors

    -29%

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We manage your investments, equity compensation, tax planni…”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 47 ms

    47 ms

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

Images and page weight

1 to fix70

  • Page weight: 10.2 MB in 52 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 52 requests on a phone: media 9.5 MB (9), scripts 340 KiB (14) and fonts 330 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 2.9 g of CO₂ per visit

    2.89 g

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

3 checks passed

  • 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

3 to fixGoogle 9395

  • 30 text elements with low contrast

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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

3 to fixGoogle 9288

  • 3 H1 headlines

    There are 3 <h1> headlines (“The wealth managerfor tech professionals.”, “We manage your investments, equity compensation, …” and “TitanDiversify”). One clear main headline is easier for people and search engines.

  • Meta description is long (218 characters)

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

  • 3 links with vague text

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

  • 38 internal links, 22 external

    The homepage links to 38 pages on titan.com and 22 external pages.

6 checks passed

  • Title: 48 characters

    Your title is a healthy 48 characters: “Titan | Wealth Management for Tech Professionals”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FinancialService.

  • 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://www.titan.com/sitemap.xml.

AI search readiness

100
4 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: 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 (1,837 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.titan.com/llms.txt (6 KiB, 0 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 25 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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

    12 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 fix88

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

  • About 1,216 words of copy

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

6 checks passed

  • Clear next step on the first screen

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

  • 11 calls to action

    The homepage has 11 calls to action, for example “Get started”, “Learn more” and “Show quote 1”.

  • Social proof on the page

    Social proof on the homepage: a star rating and “10,000+ Clients”.

  • Direct contact links

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

1 checks passed

  • 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 titan.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
Hosting
Vercel

Hiring

Hiring
12 open roles
Teams
Engineering (4), Wealth Management (3), Marketing (2), Client Experience (1)
Job board
ashby
Careers page
www.titan.com/careers (opens in a new tab)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 16 issues on titan.com, including 6 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