Website review, no card needed

firstactuarial.co.uk logo

firstactuarial.co.uk website review

Visit site (opens in a new tab)Reviewed 31 October 202623 issues · 77 checks

This review found 23 issues worth fixing on firstactuarial.co.uk, 6 of them high impact, across 77 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
1.8 s1.4 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
79 ms64 msMay 9Oct 2474 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202666 ms
May 16, 202666 ms
May 23, 202669 ms
May 30, 202667 ms
Jun 6, 202670 ms
Jun 13, 202676 ms
Jun 20, 202671 ms
Jun 27, 202677 ms
Jul 4, 202671 ms
Jul 11, 202670 ms
Jul 18, 202675 ms
Jul 25, 202674 ms
Aug 1, 202674 ms
Aug 8, 202677 ms
Aug 15, 202669 ms
Aug 22, 202673 ms
Aug 29, 202672 ms
Sep 5, 202672 ms
Sep 12, 202673 ms
Sep 19, 202671 ms
Sep 26, 202671 ms
Oct 3, 202671 ms
Oct 10, 202673 ms
Oct 17, 202671 ms
Oct 24, 202674 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 firstactuarial.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. firstactuarial.co.uk at 0.4 s0.4 s
  2. firstactuarial.co.uk at 0.8 s0.8 s
  3. firstactuarial.co.uk at 1.1 s1.1 s
  4. firstactuarial.co.uk at 1.5 s1.5 s
  5. firstactuarial.co.uk at 1.9 s1.9 s
  6. firstactuarial.co.uk at 2.3 s2.3 s
  7. firstactuarial.co.uk at 2.6 s2.6 s
  8. firstactuarial.co.uk at 3.0 s3.0 s

Speed

2 to fix94
  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    450 ms · 306 KiB

    6 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Use efficient cache lifetimes

    250 ms · 26 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (26 KiB).

  • Font display

    200 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cookiebot and jQuery CDN), adding 62 KiB and 179 ms of main-thread time.

  • Reduce unused JavaScript

    85 KiB

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

  • Reduce unused CSS

    81 KiB

    About 81 KiB of CSS is downloaded but never applied on this page.

  • 2 long tasks on the main thread

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

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

3 checks passed
  • Mobile performance score: 94

    94/100

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

  • Main-thread work: 0.9 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

3 to fix100
  • 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.

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • 3 images without width and height

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

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

    +10%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • 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: 0.9 s

    0.9 s

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

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

    -16%

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

  • Time to Interactive: 2.8 s

    2.8 s

    The page is fully interactive after 2.8 s.

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.014

    0.014

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

2 to fix60
  • Page weight: 4.1 MB in 59 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 59 requests on a phone: media 2.5 MB (1), images 995 KiB (12) and fonts 252 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    55 KiB

    1 image is downloaded at several times the size a phone draws it, for example First-Actuarial-Full-Reverse_Large_FINAL-scaled.png at 2,560 px wide, shown at 200 px. Resized copies would save about 55 KiB.

  • 5 images in older formats

    5 images (290 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

Accessibility

5 to fixGoogle 8492
  • 6 text elements with low contrast

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

  • 6 tap targets too small

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

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 7786
  • Title is short (22 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

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

  • 162 internal links, 8 external

    The homepage links to 162 pages on firstactuarial.co.uk and 8 external pages.

6 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Learn about First Actuarial’s pension services for scheme trustees and sponsors. We’re fair on fees and we put people f…”.

  • One H1 headline

    Your main headline reads: “Helping trustees and employers get the best out of their pension schemes, with actuarial, administration and investment…”.

  • Canonical URL set

    The canonical URL is https://firstactuarial.co.uk/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, 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://firstactuarial.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,384 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://firstactuarial.co.uk/llms.txt (195 KiB, 642 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 2 pages without a meta description

    https://firstactuarial.co.uk/db and https://firstactuarial.co.uk/dc have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://firstactuarial.co.uk/insights/first-actuarial-annual-conference-thursday-25-june-2026-2, https://firstactuarial.co.uk/insights/first-actuarial-annual-conference-thursday-19-june-2025-2, https://firstactuarial.co.uk/insights/first-actuarial-annual-conference-2024 and https://firstactuarial.co.uk/insights/first-actuarial-client-conference-2022 use the same meta description. A description written for each page earns more clicks.

  • 7 pages slow to respond

    https://firstactuarial.co.uk/insights/training, https://firstactuarial.co.uk/insights/first-actuarial-annual-conference-thursday-19-june-2025-2, https://firstactuarial.co.uk/insights/first-actuarial-annual-conference-2024, https://firstactuarial.co.uk/insights/first-actuarial-client-conference-2022, https://firstactuarial.co.uk/db and https://firstactuarial.co.uk/dc 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 88 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Contact us” and “Find a contact”.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and 2 customer or partner logos.

  • Direct contact links

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

Privacy and tracking

  • 3 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • 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 firstactuarial.co.uk, 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
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on firstactuarial.co.uk, including 5 speed issues, 4 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