hekimzade.com website review

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

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

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

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

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

5 third-party services load with your homepage (loox.io, Shopify and kaktusapp.com and others), adding 411 KiB and 215 ms of main-thread time.

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

About 89 KiB of JavaScript is downloaded but never used on this page.

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

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

9 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hekvir gıda takviyesi”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.0 MB in 125 requests on a phone: images 738 KiB (17), other files 562 KiB (41) and scripts 379 KiB (44). Under 2 MB keeps phones on slow connections fast.

cilt-bakim-serumlari-mob.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 0.58 g of CO₂e: 69.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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: 5 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4 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. (11 elements).

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 319 pages on hekimzade.com and 24 external pages.

Your homepage links to https://www.hekimzade.com.tr/collections/types, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.hekimzade.com.tr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.hekimzade.com.tr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.hekimzade.com.tr/customer_authentication/redirect, https://www.hekimzade.com.tr/collections/solusyonlar, https://www.hekimzade.com.tr/collections/bal, https://www.hekimzade.com.tr/collections/sac-bakimi and https://www.hekimzade.com.tr/collections/sac-serumu have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.hekimzade.com.tr/customer_authentication/redirect, https://www.hekimzade.com.tr/collections/gida-takviyeleri, https://www.hekimzade.com.tr/collections/bitkisel-caylar, https://www.hekimzade.com.tr/collections/solusyonlar, https://www.hekimzade.com.tr/collections/bitkisel-yaglar and https://www.hekimzade.com.tr/collections/bal and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 94 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.

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

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.

The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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 16 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.