sebit.com.tr website review

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

About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.1 s faster on a phone.

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

YouTube costs a phone 4.7 s of main-thread work and 8.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

1.3 MB could be saved by minifying JavaScript.

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

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

About 5.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 9.7 MB and 5.2 s of main-thread time.

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

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

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

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

Google Fonts costs a phone 0 ms of main-thread work and 329 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.

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

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

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.

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 49.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “YKS'de 35 Dakika Kazan”.

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

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

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

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

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

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

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

Your homepage downloads 28.2 MB in 653 requests on a phone: images 13.9 MB (248), scripts 10.7 MB (262) and stylesheets 1.9 MB (39). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example 1080x480px_Web_1_1_4.png at 1,080 px wide, shown at 228 px. Resized copies would save about 936 KiB.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 69 characters, so Google will cut it off around 60: “Eğitim Teknolojileri, Dijital Öğrenme ve Yapay Zekâ Çözümleri | SEBİT”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

Your meta description is 309 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://sebit.com.tr/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 245 pages on sebit.com.tr and 140 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 /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.

/cerez-politikasi, /vitamin, /sebit-vcloud, /egitim-setleri, /egitim-seviyesi/universite-hazirlik and /yapay-zeka and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/yapay-zeka, /hakkimizda, /kisaca-sebit and /misyonumuz-ve-vizyonumuz have no <h1> headline, so visitors and search engines get no clear main topic.

/egitim-setleri, /hizligo-lisans-urunu-12-sinif, /yapay-zeka, /urunler/hizligo-urunleri, /hakkimizda and /kisaca-sebit and 1 other took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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

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