tusdata.com website review

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

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

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

About 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

25 KiB could be saved by minifying CSS.

4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Fonts and others), adding 327 KiB and 221 ms of main-thread time.

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

7 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.60 (75th percentile). Good is under 0.1.

Your largest element takes 35.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

14 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 100 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.8 MB in 73 requests on a phone: images 7.6 MB (37), fonts 640 KiB (10) and scripts 378 KiB (13). Under 2 MB keeps phones on slow connections fast.

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

8 images are downloaded at several times the size a phone draws them, for example mobile-05-20260917142439.png at 1,200 px wide, shown at 390 px. Resized copies would save about 1,000 KiB.

12 images (4.7 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.

mobile-05-20260917142439.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

Headings skip levels (h2 → h6, h2 → h5 and h3 → h6), 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 title is only 7 characters: “TUSDATA”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 67 pages on tusdata.com and 171 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://www.tusdata.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.

https://www.tusdata.com/nasil-soru-yakaliyoruz-arsivi declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://www.tusdata.com/kamp-seciniz, https://www.tusdata.com/canli-ve-online-kamplarimiz-kamp-kategorisi-36 and https://www.tusdata.com/online-kamplarimiz-kamp-kategorisi-35 all use the title “Eğitimlerimiz | TUSDATA”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tusdata.com/kurumsal/hakkimizda-icerik-9 and https://www.tusdata.com/kurumsal/eski-tus-sinavlari-icerik-2516 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tusdata.com/kamp-seciniz, https://www.tusdata.com/canli-ve-online-kamplarimiz-kamp-kategorisi-36 and https://www.tusdata.com/online-kamplarimiz-kamp-kategorisi-35 use the same meta description. A description written for each page earns more clicks.

https://www.tusdata.com/videolar and https://www.tusdata.com/nasil-soru-yakaliyoruz-arsivi 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 22 found) and read each the way a search engine does.

10 of 34 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.

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.

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

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