Website review, no card needed

wcbs.co.uk logo

wcbs.co.uk website review

Visit site (opens in a new tab)Reviewed 18 October 202634 issues · 79 checks

This review found 34 issues worth fixing on wcbs.co.uk, 15 of them high impact, across 79 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

Full-page screenshot of wcbs.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wcbs.co.uk at 0.5 s0.5 s
  2. wcbs.co.uk at 1.0 s1.0 s
  3. wcbs.co.uk at 1.6 s1.6 s
  4. wcbs.co.uk at 2.1 s2.1 s
  5. wcbs.co.uk at 2.6 s2.6 s
  6. wcbs.co.uk at 3.1 s3.1 s
  7. wcbs.co.uk at 3.6 s3.6 s
  8. wcbs.co.uk at 4.2 s4.2 s

Speed

7 to fix57
  • Render-blocking requests

    3.4 s

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

  • Improve image delivery

    1.3 s · 905 KiB

    10 images could be 905 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Font display

    1.3 s

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

  • 3,645 HTML elements

    The page has 3,645 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 190 KiB

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

  • Main-thread work: 2.7 s

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

  • Reduce unused JavaScript

    150 ms · 116 KiB

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

  • 5 long tasks on the main thread

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (cdn-cookieyes.com, Google Fonts and Google Tag Manager), adding 361 KiB and 49 ms of main-thread time.

  • Legacy JavaScript

    19 KiB

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

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

1 checks passed
  • Server response: 94 ms

    94 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 12.8 s

    12.8 s

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

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 105 ms

    105 ms

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

  • Cumulative Layout Shift: 0.047

    0.047

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

Images and page weight

5 to fix28
  • Page weight: 9.9 MB in 197 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 197 requests on a phone: images 8.8 MB (109), scripts 651 KiB (73) and stylesheets 222 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    devices-with-popouts3.png weighs 2.1 MB. On a phone connection a single image that size takes seconds.

  • 22 images in older formats

    22 images (3.8 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.

  • 11 images below the first screen load straight away

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

  • 6 images far larger than shown

    52 KiB

    6 images are downloaded at several times the size a phone draws them, for example Untitled-design-2022-03-25T115807.693.png at 390 px wide, shown at 120 px. Resized copies would save about 52 KiB.

  • About 2.8 g of CO₂ per visit

    2.80 g

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

Accessibility

9 to fixGoogle 8288
  • 22 text elements with low contrast

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

  • 3 tap targets too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo 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.

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

  • 25 links without text

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

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

SEO

3 to fixGoogle 7786
  • No H1 headline

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

  • 15 links crawlers can't follow

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

  • 4 links with vague text

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

  • 197 internal links, 104 external

    The homepage links to 197 pages on wcbs.co.uk and 104 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “WCBS is a leading supplier of school admissions, MIS and finance software, providing integrated solutions to independen…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “School Admissions, MIS and Finance Software | WCBS | Home”.

  • Canonical URL set

    The canonical URL is https://www.wcbs.co.uk/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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.wcbs.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 sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix81
  • 2 linked pages hidden from search

    https://www.wcbs.co.uk/hub/hubpay-school-fee-collection and https://www.wcbs.co.uk/hub-international-schools are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a meta description

    https://www.wcbs.co.uk/finance-experts, https://www.wcbs.co.uk/finance-experts/pass-in-the-cloud and https://www.wcbs.co.uk/finance-on-premise-2 use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.wcbs.co.uk/admissions, whose canonical is https://www.wcbs.co.uk/hub/admissions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.wcbs.co.uk/hub, https://www.wcbs.co.uk/hubincome, https://www.wcbs.co.uk/hub/hubpay-school-fee-collection, https://www.wcbs.co.uk/hub-independent-schools and https://www.wcbs.co.uk/hub-international-schools have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 1 distorted image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 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 653 words of copy

    The homepage carries about 653 words of visible text.

4 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Contact Us” and “Download”.

  • Social proof on the page

    Social proof on the homepage: 21 testimonial or review blocks, 20 customer or partner logos and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 5 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 wcbs.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
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on wcbs.co.uk, including 11 speed issues, 3 SEO issues and 1 conversion gap. 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