shipowners.com website review

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

The page goes through 1 redirect before it starts loading, costing about 1.1 s. Link and advertise the final URL directly.

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

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

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

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

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

8 third-party services load with your homepage (Facebook, Parse.ly and Quantcast and others), adding 215 KiB and 66 ms of main-thread time.

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

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.

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

Real visitors see the first content after 2.3 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.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Insurance costs still a shipowner concern despite current b…”. Most of its time is element render delay (2.1 s).

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

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

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

Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

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

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

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

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

Your title is only 10 characters: “Shipowners”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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://shipowners.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.

49 of 67 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 “Failed to load resource: the server responded with a status of 404 ()”.

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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