sanko.com.tr website review

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

47 files are served with short cache lifetimes, so returning visitors download them again (7.5 MB).

15 images could be 4.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 65 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

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

binclusive.io costs a phone 225 ms of main-thread work and 332 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.

6 third-party services load with your homepage (binclusive.io, Google Tag Manager and Cloudflare and others), adding 534 KiB and 377 ms of main-thread time.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Geçmişimizden aldığımız güçle geleceğe doğru güvenle ilerli…”. Most of its time is element render delay (4.2 s).

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

3 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-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 74 requests on a phone: images 7.1 MB (30), scripts 687 KiB (25) and fonts 161 KiB (5). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example banner-1-scaled-2.webp at 2,560 px wide, shown at 390 px. Resized copies would save about 4.4 MB.

3 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

15 images (3.3 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.

14 images further down the page (3.3 MB) 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 2.27 g of CO₂e: 272.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

Your title is only 25 characters: “Ana Sayfa - SANKO Holding”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 53 pages on sanko.com.tr and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://sanko.com.tr/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.

https://sanko.com.tr/hakkimizda, https://sanko.com.tr/tarihcemiz, https://sanko.com.tr/kurucumuz, https://sanko.com.tr/onursal-baskanlarimiz, https://sanko.com.tr/yonetim-kurulu and https://sanko.com.tr/faaliyet-alanlarimiz and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sanko.com.tr/hakkimizda, https://sanko.com.tr/tarihcemiz, https://sanko.com.tr/onursal-baskanlarimiz, https://sanko.com.tr/yonetim-kurulu, https://sanko.com.tr/faaliyet-alanlarimiz and https://sanko.com.tr/faaliyet-alanlarimiz/tekstil and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sanko.com.tr/onursal-baskanlarimiz and https://sanko.com.tr/yonetim-kurulu have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

12 of 54 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 “Failed to load resource: net::ERR_FAILED”.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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