organicocean.com website review

21 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Google CDN and others), adding 1.8 MB and 605 ms of main-thread time.

Google Tag Manager costs a phone 301 ms of main-thread work and 498 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.

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

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

Stamped.io costs a phone 58 ms of main-thread work and 814 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.

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

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

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

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

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

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

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

Your largest element takes 25.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 26.2 s. Good is under 3.8 s.

Visually, the page fills in at 9.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 97 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 9.7 MB in 246 requests on a phone: media 3.8 MB (2), images 3.6 MB (69) and scripts 1.1 MB (72). Under 2 MB keeps phones on slow connections fast.

grilledorckfish.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).

2 images are downloaded at several times the size a phone draws them, for example oo-transition-logo-1.gif at 390 px wide, shown at 80 px. Resized copies would save about 386 KiB.

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

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

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

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

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.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 86 characters, so Google will cut it off around 60: “Wild-Caught BC Seafood Delivered Across Canada | Seafood Naturally · Seafood Naturally”.

There are 6 <h1> headlines (“Wild Caught Seafood”, “Customer favourites” and “Wild Sockeye Salmon Fillet”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 110 pages on organicocean.com and 3 external pages.

https://seafoodnaturally.com/pages/standing-order, https://seafoodnaturally.com/collections/white-fish, https://seafoodnaturally.com/collections/squid-octopus, https://seafoodnaturally.com/collections/pantry-items, https://seafoodnaturally.com/collections/gift-cards and https://seafoodnaturally.com/pages/our-story and 1 other use the same meta description. A description written for each page earns more clicks.

https://seafoodnaturally.com/pages/standing-order, https://seafoodnaturally.com/collections/salmon, https://seafoodnaturally.com/collections/all, https://seafoodnaturally.com/collections/red-fish and https://seafoodnaturally.com/collections/tuna took over 3 s to send their HTML from our server.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 513 words of visible text.

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