seaveg.com website review

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

27 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

8 third-party services load with your homepage (minmaxify.com, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 875 KiB and 778 ms of main-thread time.

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

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

minmaxify.com costs a phone 386 ms of main-thread work and 9 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.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Shopify costs a phone 63 ms of main-thread work and 328 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.

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

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

19 KiB could be saved by minifying JavaScript.

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

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 11.7 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 11.8 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 4.7 MB in 218 requests on a phone: images 2.2 MB (34), other files 1.3 MB (124) and scripts 920 KiB (48). Under 2 MB keeps phones on slow connections fast.

Building2_66aba67c-c063-4f2e-9c32-1ea226e2f800.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).

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

ARIA dialog and alertdialog nodes should 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: 3 elements on the page fail this check, rated moderate by axe-core.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 69 characters, so Google will cut it off around 60: “Maine Coast Sea Vegetables - Bulk Certified Organic Seaweeds and More”.

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

The homepage links to 210 pages on seaveg.com and 13 external pages.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ipinfo.io/json?hash=0.4299417223216918' from origin 'https://seaveg.com' has been …”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

The homepage shows no opening hours. If customers visit or call, show when.

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 1,470 words of visible text.

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