Website review, no card needed

titmouse.net logo

titmouse.net website review

Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 78 checks

This review found 39 issues worth fixing on titmouse.net, 18 of them high impact, across 78 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
4.7 s4.1 sMay 9Oct 244.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.2 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.3 s
Jun 20, 20264.4 s
Jun 27, 20264.5 s
Jul 4, 20264.6 s
Jul 11, 20264.6 s
Jul 18, 20264.5 s
Jul 25, 20264.3 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20264.3 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.6 s
Sep 12, 20264.6 s
Sep 19, 20264.5 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.4 s
Oct 17, 20264.4 s
Oct 24, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
106 ms93 msMay 9Oct 2494 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 202698 ms
May 23, 202698 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202699 ms
Jun 27, 2026100 ms
Jul 4, 2026100 ms
Jul 11, 202698 ms
Jul 18, 202697 ms
Jul 25, 202699 ms
Aug 1, 2026100 ms
Aug 8, 2026103 ms
Aug 15, 202696 ms
Aug 22, 202698 ms
Aug 29, 2026102 ms
Sep 5, 2026101 ms
Sep 12, 2026104 ms
Sep 19, 2026103 ms
Sep 26, 2026100 ms
Oct 3, 202696 ms
Oct 10, 202698 ms
Oct 17, 202695 ms
Oct 24, 202694 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

Full-page screenshot of titmouse.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. titmouse.net at 0.7 s0.7 s
  2. titmouse.net at 1.4 s1.4 s
  3. titmouse.net at 2.0 s2.0 s
  4. titmouse.net at 2.7 s2.7 s
  5. titmouse.net at 3.4 s3.4 s
  6. titmouse.net at 4.1 s4.1 s
  7. titmouse.net at 4.8 s4.8 s
  8. titmouse.net at 5.5 s5.5 s

Speed

7 to fix23
  • Use efficient cache lifetimes

    3.5 s · 15.6 MB

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

  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    1.1 s · 150 KiB

    About 150 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 23

    23/100

    Your mobile performance score is 23 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    460 ms · 72 KiB

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

  • Google Tag Manager adds 422 ms

    422 ms

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

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 983 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Vimeo and others), adding 590 KiB and 490 ms of main-thread time.

  • 12 long tasks on the main thread

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Improve image delivery

    45 KiB

    1 image could be 45 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Phones get a much slower page than desktops

    Desktop scores 60 but mobile only 23. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 4.4 s

    4.4 s

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

  • Real-user CLS: 0.46

    0.46

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

  • Largest Contentful Paint: 10.7 s

    10.7 s

    Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dang! Netflix”.

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Cumulative Layout Shift: 0.461

    0.461

    The layout shifts by 0.461 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 10.7 s

    10.7 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 526 ms

    526 ms

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

1 checks passed
  • Real-user INP: 93 ms

    93 ms

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

Images and page weight

1 to fix70
  • Page weight: 16.2 MB in 71 requests

    16.2 MB

    Your homepage downloads 16.2 MB in 71 requests on a phone: media 14.1 MB (1), images 972 KiB (6) and fonts 485 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 4.6 g of CO₂ per visit

    4.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.59 g of CO₂e: 550.4 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

4 to fixGoogle 9294
  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

    8 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9270
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (15 characters)

    Your title is only 15 characters: “Home - Titmouse”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 35 internal links, 8 external

    The homepage links to 35 pages on titmouse.net and 8 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://titmouse.net/titmouse-2016/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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://titmouse.net/sitemap_index.xml.

AI search readiness

1 to fix83
  • 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://titmouse.net/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.

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

Other pages

4 to fix78
  • 2 pages share a title

    https://titmouse.net/work and https://titmouse.net/titmouse-2016/work all use the title “Work - Titmouse”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://titmouse.net/work, https://titmouse.net/about, https://titmouse.net/contact, https://titmouse.net/careers, https://titmouse.net/press and https://titmouse.net/work/dang and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://titmouse.net/work, whose canonical is https://titmouse.net/titmouse-2016/work. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://titmouse.net/work, https://titmouse.net/press and https://titmouse.net/titmouse-2016/work have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://titmouse.net/work/dang, https://titmouse.net/work/mating-season, https://titmouse.net/work/the-legend-of-vox-machina-2, https://titmouse.net/work/titmouse-reel-2026 and https://titmouse.net/work/kevin have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

    4 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 36 words

    The homepage has only about 36 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 titmouse.net, 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
jQuery
Analytics
Google Analytics

Company

Founded
2000
Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on titmouse.net, including 18 speed issues, 4 SEO issues and 4 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