Website review, no card needed

mta.gov.tr logo

mta.gov.tr website review

Visit site (opens in a new tab)Reviewed 18 November 202626 issues · 74 checks

This review found 26 issues worth fixing on mta.gov.tr, 8 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.7 s1.7 sMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.3 s
Aug 1, 20263.9 s
Aug 8, 20264.9 s
Aug 15, 20265.2 s
Aug 22, 20265.2 s
Aug 29, 20265.1 s
Sep 5, 20264.4 s
Sep 12, 20264.0 s
Sep 19, 20263.5 s
Sep 26, 20263.2 s
Oct 3, 20262.8 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
325 ms240 msMay 30Nov 14260 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026315 ms
Jun 6, 2026314 ms
Jun 13, 2026306 ms
Jun 20, 2026302 ms
Jun 27, 2026305 ms
Jul 4, 2026303 ms
Jul 11, 2026304 ms
Jul 18, 2026301 ms
Jul 25, 2026296 ms
Aug 1, 2026284 ms
Aug 8, 2026264 ms
Aug 15, 2026254 ms
Aug 22, 2026250 ms
Aug 29, 2026256 ms
Sep 5, 2026277 ms
Sep 12, 2026284 ms
Sep 19, 2026289 ms
Sep 26, 2026303 ms
Oct 3, 2026308 ms
Oct 10, 2026308 ms
Oct 17, 2026308 ms
Oct 24, 2026302 ms
Oct 31, 2026298 ms
Nov 7, 2026283 ms
Nov 14, 2026260 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mta.gov.tr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mta.gov.tr at 1.7 s1.7 s
  2. mta.gov.tr at 3.4 s3.4 s
  3. mta.gov.tr at 5.1 s5.1 s
  4. mta.gov.tr at 6.8 s6.8 s
  5. mta.gov.tr at 8.5 s8.5 s
  6. mta.gov.tr at 10.2 s10.2 s
  7. mta.gov.tr at 11.9 s11.9 s
  8. mta.gov.tr at 13.7 s13.7 s

Speed

8 to fix63
  • Reduce unused JavaScript

    1.2 s · 179 KiB

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

  • Improve image delivery

    300 ms · 988 KiB

    9 images could be 988 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Reduce initial server response time

    971 ms

    Reduce initial server response time. Google estimates savings of 971 ms on a phone.

  • Document request latency

    950 ms

    The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Render-blocking requests

    750 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Main-thread work: 2.6 s

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

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

6 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 9.1 s

    9.1 s

    Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Yerkabuğu (Yüzey)”.

  • Speed Index: 13.5 s

    13.5 s

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

  • Time to Interactive: 10.1 s

    10.1 s

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

  • Real-user CLS: 0.16

    0.16

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

8 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 186 ms

    186 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 578 ms

    578 ms

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

  • Tap response (INP) got 14% faster for real visitors

    -14%

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

  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Total Blocking Time: 136 ms

    136 ms

    Scripts block the page for only 136 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 99 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 99 requests on a phone: images 2.6 MB (39), scripts 534 KiB (40) and fonts 250 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9394
  • 9 tap targets too small

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

  • Alternative text of images should not be repeated as text (25 elements)

    Alternative text of images should not be repeated as text: 25 elements on the page fail this check, rated minor by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 175 internal links, 29 external

    The homepage links to 175 pages on mta.gov.tr and 29 external pages.

8 checks passed
  • Meta description: 106 characters

    Your meta description is 106 characters: “Maden Tetkik ve Arama Genel Müdürlüğü — yerbilimleri, maden arama ve araştırma kurumunun resmî web sitesi.”.

  • One H1 headline

    Your main headline reads: “Ülkemizin enerji hammadde ve maden potansiyelini araştırıyoruz”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Maden Tetkik ve Arama Genel Müdürlüğü”.

  • Canonical URL set

    The canonical URL is https://www.mta.gov.tr/.

  • Structured data in place

    Structured data found: GovernmentOrganization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mta.gov.tr/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,130 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 3 pages share a meta description

    https://www.mta.gov.tr/kurumsal/hakkimizda/belgelerimiz, https://www.mta.gov.tr/kurumsal/hakkimizda/bilgi-guvenligi-politikasi and https://www.mta.gov.tr/kurumsal/hakkimizda/etik-komisyonu use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    https://www.mta.gov.tr/kurumsal/hakkimizda/misyon-ve-vizyon, https://www.mta.gov.tr/kurumsal/hakkimizda/yonetim-sistemleri-politikalari, https://www.mta.gov.tr/kurumsal/hakkimizda/belgelerimiz, https://www.mta.gov.tr/kurumsal/hakkimizda/bilgi-guvenligi-politikasi and https://www.mta.gov.tr/kurumsal/hakkimizda/etik-komisyonu took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 17 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix25
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 605 words of copy

    The homepage carries about 605 words of visible text.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mta.gov.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Turk Telekomunikasyon Anonim Sirketi

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on mta.gov.tr, including 14 speed issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25