vocalink.com website review

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

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

About 269 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

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

4 third-party services load with your homepage (Optanon, azure.com and Twitter and others), adding 430 KiB and 210 ms of main-thread time.

1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

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

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 KiB could be saved by minifying CSS.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies (‘Cookies’) on our …”. Most of its time is element render delay (4.9 s).

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

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

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

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

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.

Your homepage downloads 8.0 MB in 49 requests on a phone: media 6.4 MB (1), images 943 KiB (18) and scripts 381 KiB (9). Under 2 MB keeps phones on slow connections fast.

5 images (718 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.

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

3 images are downloaded at several times the size a phone draws them, for example 2880x1440_uk_bacs.jpg at 1,140 px wide, shown at 351 px. Resized copies would save about 33 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

<object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 47 pages on vocalink.com and 16 external pages.

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.

There is no https://vocalink.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://vocalink.com/tools/extended-industry-sort-code-directory, https://vocalink.com/tools/direct-debit-originators-extract and https://vocalink.com/tools/modulus-checking have no <title>, so Google invents the link text in results.

https://vocalink.com/tools/extended-industry-sort-code-directory, https://vocalink.com/tools/direct-debit-originators-extract, https://vocalink.com/tools/modulus-checking and https://vocalink.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 22 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 331 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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