yunsa.com website review

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

10 images could be 644 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Fonts and others), adding 676 KiB and 520 ms of main-thread time.

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

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

69 KiB could be saved by minifying JavaScript.

About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

13 KiB could be saved by minifying CSS.

Desktop scores 85 but mobile only 49. 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.

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 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bu internet sitesinde sizlere daha iyi hizmet sunulabilmesi…”.

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

The page becomes fully interactive after 11.0 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.

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 2.5 MB in 75 requests on a phone: images 1.4 MB (26), scripts 853 KiB (27) and stylesheets 90 KiB (11). Under 2 MB keeps phones on slow connections fast.

4 images (460 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.

3 images further down the page (255 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 0.69 g of CO₂e: 83.4 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: 2 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 27 characters: “Yünsa - Creation of Fabrics”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 7 <h1> headlines (“YATIRIMCI TAZMİN MERKEZİNE BAŞVURU SÜRESİ HAKKIND…”, “Hakkımızda” and “KİLOMETRE TAŞLARI”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No XML sitemap at https://www.yunsa.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 86 pages on yunsa.com and 11 external pages.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.yunsa.com/hakkimizda, https://www.yunsa.com/misyon-vizyon-degerler, https://www.yunsa.com/politikalarimiz, https://www.yunsa.com/kurumsal-uyeliklerimiz, https://www.yunsa.com/kilometre-taslari and https://www.yunsa.com/urunlerimiz and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.yunsa.com/hakkimizda, https://www.yunsa.com/misyon-vizyon-degerler, https://www.yunsa.com/politikalarimiz, https://www.yunsa.com/kurumsal-uyeliklerimiz, https://www.yunsa.com/kilometre-taslari and https://www.yunsa.com/urunlerimiz and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.yunsa.com/politikalarimiz took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://www.yunsa.com/#.

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

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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

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

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