Website review, no card needed

trustfundpensions.com logo

trustfundpensions.com website review

Visit site (opens in a new tab)Reviewed 19 November 202632 issues · 63 checks

This review found 32 issues worth fixing on trustfundpensions.com, 12 of them high impact, across 63 checks. The most urgent: render-blocking requests. 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
13.7 s7.4 sMay 30Nov 149.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 202612.2 s
Jun 6, 202613.0 s
Jun 13, 202611.4 s
Jun 20, 202610.7 s
Jun 27, 202610.7 s
Jul 4, 202610.3 s
Jul 11, 202610.3 s
Jul 18, 20269.7 s
Jul 25, 20269.6 s
Aug 1, 20269.8 s
Aug 8, 20269.8 s
Aug 15, 202610.3 s
Aug 22, 202610.0 s
Aug 29, 20269.8 s
Sep 5, 20269.0 s
Sep 12, 20268.3 s
Sep 19, 20268.2 s
Sep 26, 20268.4 s
Oct 3, 20269.5 s
Oct 10, 202610.8 s
Oct 17, 202611.4 s
Oct 24, 202612.3 s
Oct 31, 202611.7 s
Nov 7, 202610.1 s
Nov 14, 20269.5 s
Real-visitor tap response (INP)75th percentile, phones
272 ms101 msMay 30Nov 14188 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026121 ms
Jun 6, 2026141 ms
Jun 13, 2026153 ms
Jun 20, 2026169 ms
Jun 27, 2026172 ms
Jul 4, 2026177 ms
Jul 11, 2026176 ms
Jul 18, 2026174 ms
Jul 25, 2026172 ms
Aug 1, 2026174 ms
Aug 8, 2026171 ms
Aug 15, 2026174 ms
Aug 22, 2026175 ms
Aug 29, 2026173 ms
Sep 5, 2026178 ms
Sep 12, 2026174 ms
Sep 19, 2026175 ms
Sep 26, 2026180 ms
Oct 3, 2026194 ms
Oct 10, 2026210 ms
Oct 17, 2026233 ms
Oct 24, 2026252 ms
Oct 31, 2026192 ms
Nov 7, 2026179 ms
Nov 14, 2026188 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 trustfundpensions.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. trustfundpensions.com at 1.6 s1.6 s
  2. trustfundpensions.com at 3.3 s3.3 s
  3. trustfundpensions.com at 4.9 s4.9 s
  4. trustfundpensions.com at 6.6 s6.6 s
  5. trustfundpensions.com at 8.2 s8.2 s
  6. trustfundpensions.com at 9.9 s9.9 s
  7. trustfundpensions.com at 11.5 s11.5 s
  8. trustfundpensions.com at 13.1 s13.1 s

Speed

6 to fix71
  • Render-blocking requests

    3.6 s

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

  • Font display

    1.6 s

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

  • Use efficient cache lifetimes

    19.9 MB

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

  • Improve image delivery

    7.6 MB

    11 images could be 7.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    440 ms · 70 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, zohocdn.com and zoho.com and others), adding 282 KiB and 153 ms of main-thread time.

  • Reduce unused JavaScript

    97 KiB

    About 97 KiB of JavaScript is downloaded but never used on this page.

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 40 ms

    40 ms

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

Core Web Vitals

9 to fix67
  • 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: 9.5 s

    9.5 s

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

  • Real-user FCP: 8.2 s

    8.2 s

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

  • Real-user TTFB: 4.8 s

    4.8 s

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

  • Speed Index: 21.2 s

    21.2 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Time to Interactive: 8.4 s

    8.4 s

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

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

    +40%

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Trustfund Pensions is more than just a pension fund manager…”. Most of its time is element render delay (9.8 s).

5 checks passed
  • Real-user INP: 188 ms

    188 ms

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

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

    -22%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 26 ms

    26 ms

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

Images and page weight

1 to fix0
  • Page weight: 31.8 MB in 118 requests

    31.8 MB

    Your homepage downloads 31.8 MB in 118 requests on a phone: media 19.6 MB (1), images 11.2 MB (23) and scripts 472 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • About 9.0 g of CO₂ per visit

    9.02 g

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

Accessibility

4 to fix87
  • 21 text elements with low contrast

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

  • 16 links without text

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

1 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

SEO

8 to fixGoogle 8357
  • 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 (22 characters)

    Your title is only 22 characters: “TrustFund Pensions LTD”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://trustfundpensions.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at trustfundpensions.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 101 internal links, 28 external

    The homepage links to 101 pages on trustfundpensions.com and 28 external pages.

1 checks passed
  • Canonical URL set

    The canonical URL is https://trustfundpensions.com/.

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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

1 to fixGoogle 9293
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • Thin social proof

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 763 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us” and “Learn more >”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on 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 trustfundpensions.com, 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
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on trustfundpensions.com, including 15 speed issues, 8 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