oceaneva.com website review

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

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

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

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

8 third-party services load with your homepage (loox.io, Shopify and Klaviyo and others), adding 1.2 MB and 370 ms of main-thread time.

loox.io costs a phone 135 ms of main-thread work and 571 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.

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

1 image could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 44 KiB of CSS is downloaded but never applied on this page.

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.

Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Your homepage downloads 2.6 MB in 218 requests on a phone: scripts 966 KiB (83), other files 733 KiB (79) and images 502 KiB (22). Under 2 MB keeps phones on slow connections fast.

Oceaneva_Dodeca_Trench_GMT_Series_960x.jpg 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).

1 image (114 KiB) is 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.75 g of CO₂e: 89.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

4 frames have no title, so screen-reader users cannot tell what they contain.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Headings should not be empty: 11 elements on the page fail this check, rated minor by axe-core.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Oceaneva Diver Watches | 10 bar Water Resistance & NH34GMT Movement”.

There are 12 <h1> headlines (“Our Collections”, “SW210 Swiss Manual Wind Tempus Pure Series” and “Oceaneva Power Reserve Automatic”). One clear main headline is easier for people and search engines.

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

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

The homepage links to 179 pages on oceaneva.com and 7 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://oceaneva.com/collections/grade-5-titanium-sw210-manual-wind-watche and https://oceaneva.com/collections/grade-5-titanium-sw210-manual-wind-watch all use the title “Grade 5 Titanium SW210 Manual Wind Watches | Oceaneva”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://oceaneva.com/collections/grade-5-titanium-sw210-manual-wind-watche and https://oceaneva.com/collections/grade-5-titanium-sw210-manual-wind-watch use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://oceaneva.com/collections/oceaneva-dodeca-trench-600m-gmt-titanium-automatic, whose canonical is https://oceaneva.com/collections/oceaneva-dodeca-trench-6000m-gmt-titanium-automatic. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://oceaneva.com/collections/grade-5-titanium-sw210-manual-wind-watch, https://oceaneva.com/collections/worldtime-gmt-watch-worldtimer, https://oceaneva.com/collections/oceaneva-6000m-power-reserve and https://oceaneva.com/collections/mechanical-chronograph-watch-automatic took over 3 s to send their HTML from our server.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage carries about 1,115 words of visible text.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 18 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.