Website review, no card needed
tomo.com website review
Visit site (opens in a new tab)Reviewed 18 November 202629 issues · 79 checks
This review found 29 issues worth fixing on tomo.com, 9 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 156 ms |
| Oct 24, 2026 | 158 ms |
| Oct 31, 2026 | 155 ms |
| Nov 7, 2026 | 154 ms |
| Nov 14, 2026 | 155 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
Use efficient cache lifetimes
4.5 s · 1.2 MB53 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, TikTok and Hubspot and others), adding 1.7 MB and 1.9 s of main-thread time.
Reduce unused JavaScript
900 ms · 954 KiBAbout 954 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 824 ms
824 msGoogle Tag Manager costs a phone 824 ms of main-thread work and 847 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 598 ms. During a long task the page ignores taps.
TikTok adds 264 ms
264 msTikTok costs a phone 264 ms of main-thread work and 174 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.
awswaf.com adds 177 ms
177 msawswaf.com costs a phone 177 ms of main-thread work and 309 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.
Legacy JavaScript
150 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
18 KiB1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 109 ms
109 msYour server sent the HTML in 109 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.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A couple celebrating in front of a new home”.
Real-user TTFB: 839 ms
839 msReal visitors wait 839 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 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-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 131 requests
3.0 MBYour homepage downloads 3.0 MB in 131 requests on a phone: scripts 2.4 MB (54), HTML 202 KiB (1) and other files 159 KiB (54). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
happy_homeowners_750-80.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.8 g of CO₂ per visit
0.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 101.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (FAQPage, Organization and Product) but with 1 problem, for example “Product: no offers (price) block”.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
181 internal links, 6 external
The homepage links to 181 pages on tomo.com and 6 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Low Rates, No Gotchas”.
Title: 60 characters
Your title is a healthy 60 characters: “Tomo Mortgage: Home buying made happy, mortgages made simple”.
Canonical URL set
The canonical URL is https://tomo.com/.
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://tomo.com/mortgage/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 (1,394 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://tomo.com/llms.txt (13 KiB, 93 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://tomo.com/mortgage declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://tomo.com/mortgage all use the title “Tomo Mortgage: Home buying made happy, mortgages made simple”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without an H1
https://tomo.com/mortgage/app/preapproval has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 165 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
5 small tap targets
5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 609 words of copy
The homepage carries about 609 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”.
14 calls to action
The homepage has 14 calls to action, for example “Get started”, “Learn more” and “Get your TrueRate”.
Social proof on the page
Social proof on the homepage: 31 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Amplitude, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 tomo.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 Tag Manager
- Hosting
- CloudFront
Hiring
- Hiring
- 13 open roles
- Teams
- Mortgage Sales (7), Mortgage Operations (4), Executive (1), Marketing (1)
- Job board
- ashby
- Careers page
- tomo.com/mortgage/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 29 issues on tomo.com, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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.