oka-b.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, accessibilityassistant.com and Clarity and others), adding 1.1 MB and 1.3 s of main-thread time.

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

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

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

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

accessibilityassistant.com costs a phone 465 ms of main-thread work and 292 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.

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

5 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 183 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 227 requests on a phone: scripts 1.4 MB (86), other files 884 KiB (106) and images 701 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example mary-jane-ballet-flats-licorice-oka-b-267962_1024x1024.jpg at 1,024 px wide, shown at 278 px. Resized copies would save about 84 KiB.

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

18 elements hidden from screen readers can still receive keyboard focus.

ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 18 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found (ShoeStore and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.oka-b.com")”.

1 link has no real href, so search engines can't follow it.

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

Your <h1> is empty.

The homepage links to 158 pages on oka-b.com 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.

https://www.oka-b.com/collections/mary-jane and https://www.oka-b.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.oka-b.com/collections/new-arrivals and https://www.oka-b.com/collections/all-oka-b-shoes use the same meta description. A description written for each page earns more clicks.

https://www.oka-b.com/pages/loyalty-and-referral-program has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.oka-b.com/.

6 errors were 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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 89 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage carries about 922 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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