tergan.com.tr website review

9 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Insider and Facebook and others), adding 2.2 MB and 2.1 s of main-thread time.

Google Tag Manager costs a phone 961 ms of main-thread work and 672 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.

Insider costs a phone 561 ms of main-thread work and 539 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.

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

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

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

streamable.com costs a phone 51 ms of main-thread work and 641 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 201 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

Desktop scores 52 but mobile only 16. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 31.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kadın Ayakkabı”.

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

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

The layout shifts by 0.66 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

4 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-17, real Chrome visitors' tap response (inp) went from 238 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.7 MB in 134 requests on a phone: images 4.2 MB (30), scripts 1.6 MB (27) and media 556 KiB (1). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example adgrey-logo_2.png at 5,077 px wide, shown at 30 px. Resized copies would save about 1.6 MB.

20 images (5.4 MB) 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.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Interactive controls must not be nested: 11 elements on the page fail this check, rated serious by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 11 elements on the page fail this check, rated serious by axe-core.

8 tap targets are too small or too close together to hit reliably with a finger.

Some list items are not inside a list.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

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

Your title is 72 characters, so Google will cut it off around 60: “TERGAN | Hakiki Deri, Ayakkabı, Çanta, Cüzdan, Aksesuar, Fırsat Ürünleri”.

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

The homepage links to 401 pages on tergan.com.tr and 11 external pages.

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

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

3 errors were logged to the browser console while the page loaded, for example “Error while parsing the 'sandbox' attribute: 'allow-autoplay' is an invalid sandbox flag.”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

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.

Social proof on the homepage: 5 trust badges. 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.

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

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