Mobile audit · April 2026

Care UK mobile site: what the audit found.

Six pages assessed on iPhone 12 Pro against the brief's seven dimensions: density, scroll depth, truncation, touch targets, layout shift, horizontal scroll, and typography. This is the diagnosis. It covers what's there today, where the problems concentrate, and the patterns that propagate across templates.

58
Findings total
11 High 30 Medium 16 Low
91
Phone-screens of scrolling across six pages
58,636 pixels of content in total
87
Buttons and links too small to tap reliably
Plus 119 more that work but feel cramped on a phone
77%
Images cause the page to jump as they load
390 of 504 images · hurts Google ranking and feels broken to users
How to read the cards High density P01 Show legend ↓

Severity

How critical the issue is

  • High Significant impact on usability or accessibility
  • Medium Real issue, not a blocker on its own
  • Low Minor or polish-level
  • Note Informational, sets context for other findings

Dimension

Which area of the brief the finding falls under

  • density Page length, scrolling, content compactness
  • layout Layout shift, horizontal scroll, truncation
  • touch Button / link / tap-target sizes
  • typography Text size, contrast, readability
  • navigation Wayfinding, primary actions, page hierarchy
  • accessibility Heading structure, screen-reader behaviour

Page

Which of the six audited pages a finding applies to

The six pages assessed

Each page audited against the brief's four dimensions: density & scroll, layout & truncation, navigation & touch, typography & readability. Click any page for the detailed breakdown.

01

Care Home Detail

A prospective customer (or their adult children) is evaluating whether this home is right for a relative.

27 phone-screens 17,910 pixels of content
11 page-specific findings
1 High 8 Medium 2 Low

+ 9 cross-page findings also affect this page

02

Care Home List

Find a Care UK home near a postcode, optionally filtered by care type, sortable by distance or drive time.

15 phone-screens 9,785 pixels of content
7 page-specific findings
1 High 3 Medium 3 Low

+ 10 cross-page findings also affect this page

03

Promo Landing

Someone searching "Epsom care home" lands here and decides whether Care UK serves the area, and which homes are nearby.

14 phone-screens 8,968 pixels of content
5 page-specific findings
4 Medium 1 Low

+ 10 cross-page findings also affect this page

04

Careers Home

A prospective applicant, care assistant, nurse, hospitality role, wants to understand what working at Care UK is like and find a job to apply for.

17 phone-screens 10,907 pixels of content
7 page-specific findings
1 High 4 Medium 2 Low

+ 6 cross-page findings also affect this page

05

Vacancy List

Find a Care UK vacancy near a postcode, optionally filtered by role type, sortable by distance or drive time.

6 phone-screens 3,569 pixels of content
8 page-specific findings
4 Medium 3 Low

+ 8 cross-page findings also affect this page

06

Job Detail

A candidate has clicked through from the vacancy list and wants to read the role and apply.

12 phone-screens 7,497 pixels of content
9 page-specific findings
2 High 3 Medium 4 Low

+ 6 cross-page findings also affect this page

Patterns that recur across pages

14 cross-page findings: issues that aren't unique to one template but propagate across multiple. These represent the highest-leverage problems in the audit. Browse all cross-page findings →

C-CARD-LIST.1 High density P02P03 3

Care-home result card is 1,000–1,200 px tall on mobile

Each card stacks a full-width image (~280 px), title row, CQC line, 7-row care-type matrix showing offered + not-offered services with similar visual weight, phone number row, and a full-width "VIEW HOME" button. Total ~1,000–1,200 logical px. The same template renders only one card per fold on a 844 px viewport.

On the page
C-PANEL.1 High density P01 3

Inverse-purple section-intro panels are content-light, space-heavy

Each panel contains a heading + 2–3 line body + single CTA. Panel itself is 280–520 px tall on mobile. Across 8 instances on page 01 that's ~3.2 viewport heights of section-introduction framing before any actual content is shown inside.

On the page
C-CAROUSEL.1 High touch P01P04 3

Slick.js pagination dots are 20×20 px (sub WCAG AA touch minimum)

The dots are 20×20 logical px, below the WCAG 2.5.8 AA minimum of 24×24 px. They are the primary affordance for paginating image carousels on mobile, where swipe is the alternative but discoverability of swipe vs the dots is mixed.

On the page
C-CHAT.1 High layout P01P02P03P04P05P06 2

Two persistent bottom-anchored widgets compound on every screen

Two competing always-on bottom widgets reduce the effective scrollable viewport by ~80–200 logical px on every screen of content the user reads. WCAG 2.4.11 (Focus Not Obscured), content under a persistent widget cannot be focused without scrolling around it. Per page: - P01, Olark chat icon + Recently Viewed (2 widgets) - P02–P03, Recently Viewed only - P04, Recruiting Assistant + Recently Viewed (2 widgets) - P05–P06, Recently Viewed only

On the page
C-IMG.1 High layout P01P02P03P04P05P06 2

77% of images across the audit are missing width / height / aspect-ratio

Images without explicit dimensions cause **layout shift** as they load, content jumps as the browser reserves space. This produces a poor Core Web Vitals CLS score (a Google ranking signal) and a janky perceived performance. The brief explicitly calls this out. Per page: - P01: 242 / 297 (81%) - P02: 13 / 15 (87%) - P03: 10 / 12 (83%) - P04: 18 / 69 (26%) - P05: 3 / 5 (60%) - P06: 104 / 106 (98%)

On the page

What the audit covers

44
Page-specific findings

Issues unique to a single template: content prioritisation, hierarchy, page-only touch problems.

14
Cross-page findings

Component-level patterns that propagate across pages. Browse →

4
Brief dimensions

Density · Layout & truncation · Navigation & touch · Typography. Methodology →

Looking ahead

There's a meaningful improvement opportunity here.

Today, the user scrolls through 91 phone-screens of content across the six pages (58,636 pixels in total). Based on the issues identified above, our early estimate is that the equivalent of around 42 phone-screens of scrolling could be reclaimed across the site, alongside resolving the touch-target and layout-shift issues.

That's a forward-looking signal, not a commitment to a specific approach. How best to act on these findings is a separate conversation; the deliverable here is the diagnosis above.