Website review, no card needed

domandtom.com logo

domandtom.com website review

Visit site (opens in a new tab)Reviewed 21 October 202627 issues · 70 checks

This review found 27 issues worth fixing on domandtom.com, 12 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
5.9 s3.3 sMay 2Jul 45.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.8 s
May 16, 20264.4 s
May 23, 20264.9 s
May 30, 20265.6 s
Jun 6, 20265.3 s
Jun 13, 20265.1 s
Jun 20, 20265.0 s
Jun 27, 20264.8 s
Jul 4, 20265.1 s

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 domandtom.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix59
  • Use efficient cache lifetimes

    32.5 s · 6.5 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).

  • Render-blocking requests

    3.5 s

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

  • Improve image delivery

    2.3 s · 566 KiB

    13 images could be 566 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Reduce unused JavaScript

    750 ms · 279 KiB

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

  • Reduce unused CSS

    900 ms · 127 KiB

    About 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 59

    59/100

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

  • Google Tag Manager adds 195 ms

    195 ms

    Google Tag Manager costs a phone 195 ms of main-thread work and 321 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Mailchimp and bunny.net and others), adding 422 KiB and 195 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 324 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

6 to fix66
  • Largest Contentful Paint: 35.4 s

    35.4 s

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

  • Time to Interactive: 35.4 s

    35.4 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Speed Index: 7.4 s

    7.4 s

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

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

    +34%

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

  • 18 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 94 ms

    94 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 7.3 MB in 116 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 116 requests on a phone: images 5.9 MB (19), scripts 612 KiB (12) and other files 333 KiB (68). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    alzheimers-case.jpg weighs 5.1 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    4.9 MB

    2 images are downloaded at several times the size a phone draws them, for example alzheimers-case.jpg at 4,096 px wide, shown at 358 px. Resized copies would save about 4.9 MB.

  • 3 images in older formats

    3 images (5.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 4 images below the first screen load straight away

    4 images further down the page (5.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.06 g

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

Accessibility

3 to fixGoogle 8795
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 27 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9291
  • Meta description is long (168 characters)

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

  • Structured data has 8 problems

    Structured data found (FAQPage, Organization, Service and WebSite) but with 8 problems, for example “Service: no offers (price) block”.

  • 42 internal links, 13 external

    The homepage links to 42 pages on domandtom.com and 13 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Your product has momentum. Now it needs to hold up.”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Dom & Tom | Digital Product Agency for AI, Web & Mobile Products”.

  • Canonical URL set

    The canonical URL is https://domandtom.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://domandtom.com/sitemap.xml.

AI search readiness

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

    Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) 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,417 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://domandtom.com/insights has no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://domandtom.com/founder-tools, https://domandtom.com/contact, https://domandtom.com/services/ai-product-development, https://domandtom.com/services/app-rescue-modernization, https://domandtom.com/services/mobile-app-development and https://domandtom.com/work/turner-broadcasting-company-data-visualization and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

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

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

    The homepage carries about 1,147 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: “Talk to a Product Leader”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Talk to a Product Leader” and “Learn more →”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

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

  • 7 other companies contacted

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

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 domandtom.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
Vue.js
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on domandtom.com, including 13 speed issues, 2 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

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