ted.org.tr website review

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

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

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

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 791 KiB and 558 ms of main-thread time.

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

Google Tag Manager costs a phone 389 ms of main-thread work and 301 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 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.

17 KiB could be saved by minifying CSS.

37 KiB could be saved by minifying JavaScript.

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

Desktop scores 73 but mobile only 44. 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.

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

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

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

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Türk Eğitim Derneği”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 103 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

39 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 20.8 MB in 329 requests on a phone: images 17.6 MB (106), fonts 1.6 MB (22) and scripts 1.1 MB (82). Under 2 MB keeps phones on slow connections fast.

39 images are downloaded at several times the size a phone draws them, for example Onur-Bugdayci.jpg at 2,136 px wide, shown at 100 px. Resized copies would save about 11.2 MB.

10 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.

40 images (16.2 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.

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

1 button has no accessible name, so screen readers announce just “button”.

Some list items are not inside a list.

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

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 436 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.

The homepage links to 126 pages on ted.org.tr and 16 external pages.

The HTML your server sends has 2,388 of the 4,324 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

There is no https://ted.org.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://ted.org.tr/tedokullari, https://ted.org.tr/en, https://ted.org.tr/hakkimizda, https://ted.org.tr/bagis, https://ted.org.tr/burslar and https://ted.org.tr/projeler and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ted.org.tr/tedokullari, https://ted.org.tr/en, https://ted.org.tr/hakkimizda, https://ted.org.tr/bagis, https://ted.org.tr/tedmem and https://ted.org.tr/deprem-gelecegimizi-yikmasin took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://themexriver.com/prysm-theme/web-agency/wp-content/uploads/sites/28/2022/02/counter-8.png.

2 images are served at too low a resolution for sharp phone screens.

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

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.