midocean.com website review

About 1.7 MB 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.

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

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

About 261 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.

5 images could be 259 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Azure Web Services and others), adding 1.8 MB and 442 ms of main-thread time.

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

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

Azure Web Services costs a phone 69 ms of main-thread work and 651 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.

ctfassets.net costs a phone 0 ms of main-thread work and 580 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.

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

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.

Real visitors wait 596 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

Real visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

2 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-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 147 requests on a phone: scripts 3.4 MB (32), images 922 KiB (40) and other files 588 KiB (69). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example outlet-homepage-new-style-1-96dpi.jpg at 1,664 px wide, shown at 358 px. Resized copies would save about 75 KiB.

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

35 links have no real href, so search engines can't follow them.

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

Your meta description is only 20 characters: “Home description ...”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 73 pages on midocean.com and 7 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.

There is no https://www.midocean.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.

Your homepage links to https://www.midocean.com/export/us/eur/content/product-compliance and https://www.midocean.com/export/us/eur/compare, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.midocean.com/export/us/eur and https://www.midocean.com/export/us/eur/home all use the title “Solo midocean | Personalised Promotional Gifts”, 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://www.midocean.com/export/us/eur/content/challenging-all-lead-times, https://www.midocean.com/export/us/eur/content/your-unique-product-always, https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_MBTN07 and https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_ML1173 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.midocean.com/export/us/eur/mo3170-13-zid10248277, whose canonical is https://www.midocean.com/export/us/eur/drink-lunchware/mugs-tumblers/tumblers-double-wall/mo3170-13-zid10248277. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.midocean.com/export/us/eur/home, https://www.midocean.com/export/us/eur/content/challenging-all-lead-times, https://www.midocean.com/export/us/eur/content/your-unique-product-always, https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_MBTN07 and https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_ML1173 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_MBTN07 and https://www.midocean.com/export/us/eur/mto.yourchoice-zid1mto_ML1173 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

15 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies (measured from a US location before any click).

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.