Website review, no card needed

wearejust.co.uk logo

wearejust.co.uk website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 88 checks

This review found 36 issues worth fixing on wearejust.co.uk, 10 of them high impact, across 88 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
1.4 s998 msMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
103 ms92 msMay 16Oct 3199 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202697 ms
May 23, 202697 ms
May 30, 2026102 ms
Jun 6, 2026102 ms
Jun 13, 202694 ms
Jun 20, 202694 ms
Jun 27, 202694 ms
Jul 4, 202697 ms
Jul 11, 202696 ms
Jul 18, 2026101 ms
Jul 25, 202699 ms
Aug 1, 202697 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202695 ms
Sep 12, 202693 ms
Sep 19, 202693 ms
Sep 26, 202694 ms
Oct 3, 202694 ms
Oct 10, 202695 ms
Oct 17, 2026100 ms
Oct 24, 202696 ms
Oct 31, 202699 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 wearejust.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix63
  • Use efficient cache lifetimes

    1.9 s · 2.1 MB

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

  • Improve image delivery

    1.9 s · 2.1 MB

    16 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    2.1 s

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

  • Reduce unused JavaScript

    920 ms · 521 KiB

    About 521 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

  • Mobile performance score: 63

    63/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, Google Tag Manager and Facebook and others), adding 1.2 MB and 831 ms of main-thread time.

  • Font display

    450 ms

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

  • Reduce unused CSS

    310 ms · 57 KiB

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

  • Hotjar adds 294 ms

    294 ms

    Hotjar costs a phone 294 ms of main-thread work and 430 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.

  • Google Tag Manager adds 231 ms

    231 ms

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 7.5 s

    7.5 s

    Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “When can I retire?”.

  • Time to Interactive: 13.5 s

    13.5 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • Total Blocking Time: 234 ms

    234 ms

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

    1.6 s

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

  • Real-user INP: 95 ms

    95 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 514 ms

    514 ms

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

  • Cumulative Layout Shift: 0.053

    0.053

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

Images and page weight

4 to fix43
  • Page weight: 4.1 MB in 91 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 91 requests on a phone: images 2.5 MB (26), scripts 1.2 MB (29) and fonts 288 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.1 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.

  • 5 images below the first screen load straight away

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

  • 1 image far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example just_angel-lane_london_high_39a7455-1.jpg at 1,280 px wide, shown at 320 px. Resized copies would save about 68 KiB.

  • About 1.2 g of CO₂ per visit

    1.18 g

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

Accessibility

4 to fixGoogle 8993
  • 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.

  • 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 42 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: 42 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7780
  • Title is short (11 characters)

    Your title is only 11 characters: “We Are Just”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (200 characters)

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

  • Structured data has 5 problems

    Structured data found (BreadcrumbList, FinancialService, Organization and WebPage) but with 5 problems, for example “Organization: missing name”.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 79 internal links, 10 external

    The homepage links to 79 pages on wearejust.co.uk and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “We help people achieve a better later life”.

  • Canonical URL set

    The canonical URL is http://www.wearejust.co.uk/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.wearejust.co.uk/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.wearejust.co.uk/llms.txt (33 KiB, 200 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

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

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=22005980&tm=gtm002&Ver=2&mid=b47af656-2807-4b82-9180-d31a2b62c26a&bo=1&sid=e8a012d0d95411f193b3e1cb1bdb15f3&vid=e8a04ab0d95411f1a3394d986e488c96&vids=1&msclkid=N&pi=91.

  • 3 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix80
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

    The homepage carries about 442 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact us”, “Learn More” and “Learn more”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

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

  • 26 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 wearejust.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

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Optimizely AB

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on wearejust.co.uk, including 16 speed issues, 5 SEO issues and 3 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