supplementhane.net website review

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

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

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

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

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

5 third-party services load with your homepage (Shopify, kaktusapp.com and Judge.me and others), adding 1.1 MB and 370 ms of main-thread time.

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

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

19 KiB could be saved by minifying JavaScript.

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

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

About 27 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB JavaScript is shipped twice across bundles.

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 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Supplementhane Fırsatlar mobile banner”.

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

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

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

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

Your homepage downloads 3.8 MB in 277 requests on a phone: images 1.7 MB (62), other files 1.0 MB (107) and scripts 811 KiB (84). Under 2 MB keeps phones on slow connections fast.

bayi-mobil_285197c8-8a02-4ab1-a933-260c842e5ad9.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “Supplementhane® | Türkiye'nin En Büyük Supplement ve Vitamin Mağazası”.

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

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

The homepage links to 915 pages on supplementhane.net and 10 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.supplementhane.net/collections/skt-yaklasanlar, https://www.supplementhane.net/collections/advanced-bionetix and https://www.supplementhane.net/collections/animal-factory have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.supplementhane.net/collections/amazi%CC%87ng-muscle, whose canonical is https://www.supplementhane.net/collections/amazi%cc%87ng-muscle. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.supplementhane.net/collections/yeni-urunler, https://www.supplementhane.net/collections/firsatlar, https://www.supplementhane.net/collections/skt-yaklasanlar, https://www.supplementhane.net/collections/allmax and https://www.supplementhane.net/collections/amix have no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,327 words of visible text.

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