bluewater.com website review

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

5 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

7 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 284 KiB and 88 ms of main-thread time.

About 69 KiB of JavaScript is downloaded but never used on this page.

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

Polyfills for old browsers add 14 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.

5 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.672 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Bluewater we use our decades of experience to provide sa…”. Most of its time is element render delay (5.1 s).

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Bluewater_Oceans-of-Knowledge_corporate-video-2560.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

Your homepage downloads 2.2 MB in 75 requests on a phone: images 1.4 MB (8), scripts 359 KiB (30) and fonts 262 KiB (10). Under 2 MB keeps phones on slow connections fast.

4 images (1.3 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.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

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

The homepage links to 51 pages on bluewater.com and 4 external pages.

Your Organization JSON-LD is missing 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 /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.

/corporate-about-us, /corporate-about-us/vision-mission, /corporate-about-us/management-team, /corporate-about-us/company-profile, /corporate-responsibility and /hseq and 9 others use the same meta description. A description written for each page earns more clicks.

/corporate-about-us, /corporate-about-us/vision-mission, /corporate-about-us/management-team, /corporate-about-us/company-profile, /corporate-responsibility and /hseq and 8 others took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “jQuery(...).slick is not a function”.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bluewater.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bluewater.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 271 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics 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 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.