oceansales.ca website review

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

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

11 images could be 335 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

4 third-party services load with your homepage (rebuyengine.com, Shopify and addons.business and others), adding 1.4 MB and 461 ms of main-thread time.

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

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

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

rebuyengine.com costs a phone 228 ms of main-thread work and 711 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.

Shopify costs a phone 196 ms of main-thread work and 649 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,930 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

3 files are served with short cache lifetimes, so returning visitors download them again (5 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.

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

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

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

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

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

12 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' tap response (inp) went from 105 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 366 requests on a phone: scripts 1.1 MB (185), images 882 KiB (53) and other files 841 KiB (90). Under 2 MB keeps phones on slow connections fast.

ocean_sales_modern_living_room_steam_mop_ultra.png 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 is downloaded at several times the size a phone draws it, for example Ocean_Home_and_Lifestyle_Logo_Web_Grey_XL.png at 6,077 px wide, shown at 195 px. Resized copies would save about 85 KiB.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 77 characters, so Google will cut it off around 60: “Ocean | Home + Lifestyle Canada | Ocean Sales Group since 1983 – Ocean Canada”.

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

The homepage links to 65 pages on oceansales.ca and 16 external pages.

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.

The HTML your server sends has 568 of the 1,054 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.oceansales.ca/pages/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

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 ()”.

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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