oceanairuk.com website review

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

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

26 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

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

Shopify costs a phone 119 ms of main-thread work and 348 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.

6 third-party services load with your homepage (Clarity, Shopify and cookiefirst.com and others), adding 519 KiB and 336 ms of main-thread time.

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

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

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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Oceanair is a specialist UK supplier of air conditioning, h…”. Most of its time is element render delay (2.5 s).

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

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

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

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

Your homepage downloads 2.3 MB in 219 requests on a phone: images 832 KiB (30), other files 688 KiB (79) and scripts 592 KiB (67). Under 2 MB keeps phones on slow connections fast.

Accent-Bath-Lifestyle-Landscape-0607-copy.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images (243 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.

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

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

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

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

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

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

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

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

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

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

The homepage links to 464 pages on oceanairuk.com and 10 external pages.

There is no https://www.oceanairuk.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.oceanairuk.com/pages/account-application has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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 1,071 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 11 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.