oofos.international website review

About 581 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 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 Shopify and others), adding 1.3 MB and 595 ms of main-thread time.

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

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

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

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

4 images could be 265 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 162 ms of main-thread work and 311 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,588 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

13 KiB could be saved by minifying JavaScript.

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.

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.

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW OOMY ROAM SHOP ALL WOMEN'S SHOP ALL MEN'S”.

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

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

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

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

22 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 102 ms to 104 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 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 412 requests on a phone: scripts 1.7 MB (94), other files 1.4 MB (257) and images 1.3 MB (43). Under 2 MB keeps phones on slow connections fast.

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

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

Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

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

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

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

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

The homepage links to 225 pages on oofos.international and 20 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.

Your homepage links to https://www.oofos.international/pages/our-technology-old, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.oofos.international/policies/shipping-policy, https://www.oofos.international/collections/new-arrivals, https://www.oofos.international/collections/best-sellers, https://www.oofos.international/collections/womens-sandals, https://www.oofos.international/collections/ooahh-fused-collection and https://www.oofos.international/collections/ooahh-sport-flex-rally and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.oofos.international/collections/new-arrivals, https://www.oofos.international/collections/best-sellers, https://www.oofos.international/collections/womens-sandals, https://www.oofos.international/collections/ooyea, https://www.oofos.international/collections/ooahh-fused-collection and https://www.oofos.international/collections/ooahh-sport-flex-rally and 1 other have 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.

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

6 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'title')”.

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

Large scripts ship without source maps.

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

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

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