shokz.com.tr website review

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

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

5 third-party services load with your homepage (Clarity, Shopify and Yandex Metrica and others), adding 455 KiB and 572 ms of main-thread time.

About 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

7 images could be 204 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

4 KiB could be saved by minifying JavaScript.

9 long tasks block the main thread while loading, the longest for 128 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).

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 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

17 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 111 ms to 106 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 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.1 MB in 220 requests on a phone: media 16.7 MB (4), images 1.1 MB (91) and scripts 637 KiB (61). Under 2 MB keeps phones on slow connections fast.

9 images (358 KiB) are 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 5.41 g of CO₂e: 648.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

40 images have no alt text, which hurts accessibility and image search.

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

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

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

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

The homepage links to 168 pages on shokz.com.tr and 5 external pages.

https://shokz.com.tr/pages/shokz-garanti-kaydi declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://shokz.com.tr/pages/shokz-garanti-kaydi all use the title “Shokz Türkiye Resmi Online Satış Mağazası – Shokz Turkiye”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://shokz.com.tr/products/shokz-openrun-pro-2-kemik-iletimli-bluetooth-kulaklik and https://shokz.com.tr/products/shokz-openrun-kemik-i%CC%87letimli-bluetooth-kulaklik use the same meta description. A description written for each page earns more clicks.

https://shokz.com.tr/pages/shokz-garanti-kaydi and https://shokz.com.tr/pages/acik-kulaklik-konsepti have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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