overseaspayments.com website review

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

Google CDN costs a phone 1.1 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Squarespace and Google Tag Manager and others), adding 3.2 MB and 1.9 s of main-thread time.

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

Squarespace costs a phone 520 ms of main-thread work and 970 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.

8 images could be 287 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).

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

32 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Seamless international money transfers for property, emigra…”.

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

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

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

1 image 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 5.6 MB in 156 requests on a phone: scripts 2.9 MB (65), images 1.3 MB (54) and other files 816 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

3 dropdowns have no label.

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

There are 9 <h1> headlines (“Expertly Managed. Seamless Transfers.”, “Loved By Our Clients Worldwide” and “Get the Support You Need”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/685d15707c1914395d5…”.

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

The homepage links to 41 pages on overseaspayments.com and 11 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description 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.

There is no https://www.overseaspayments.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://www.overseaspayments.com/news-and-insights, https://www.overseaspayments.com/news-and-insights/gbp/eur-forecast-2026-what-property-buyers-need-to-know, https://www.overseaspayments.com/news-and-insights/how-interest-rate-decisions-affect-exchange-rates, https://www.overseaspayments.com/news-and-insights/what-documents-are-needed-to-transfer-large-amounts-of-money-internationally, https://www.overseaspayments.com/news-and-insights/spains-3-withholding-tax-when-selling-property-what-uk-sellers-need-to-know-in-2026 and https://www.overseaspayments.com/news-and-insights/buying-property-in-switzerland-in-2026 and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/685d15707c1914395d59547a/393/5c5…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 947 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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