yonka.com website review

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

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

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

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

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

8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and variantnow.com and others), adding 1.2 MB and 172 ms of main-thread time.

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

Shopify costs a phone 14 ms of main-thread work and 705 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 235 KiB of JavaScript is downloaded but never used on this page.

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.

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

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

23 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.

3 KiB could be saved by minifying CSS.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Yon-Ka holiday sets”.

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

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

1 image 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 166 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 280 requests on a phone: other files 1.1 MB (146), images 1,013 KiB (50) and scripts 711 KiB (53). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Yon-Ka_Paris_-_collection_noel_2026_-_WebBanner_-_mobile_-_5 at 2,133 px wide, shown at 390 px. Resized copies would save about 198 KiB.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 26 characters: “Yon-Ka Paris International”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization, SoftwareApplication and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https:files/logo_yonka_svg.svg")”.

The homepage links to 285 pages on yonka.com and 17 external pages.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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