Website review, no card needed

akdeniz.edu.tr logo

akdeniz.edu.tr website review

Visit site (opens in a new tab)Reviewed 18 October 202647 issues · 89 checks

This review found 47 issues worth fixing on akdeniz.edu.tr, 18 of them high impact, across 89 checks. The most urgent: page weight: 58.6 MB in 83 requests. 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
2.1 s1.7 sApr 25Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.9 s
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
118 ms90 msApr 25Oct 10104 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026100 ms
May 9, 202693 ms
May 30, 2026105 ms
Jun 6, 2026105 ms
Jun 13, 2026100 ms
Jun 20, 202697 ms
Jun 27, 2026102 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026108 ms
Aug 15, 2026104 ms
Aug 22, 2026105 ms
Aug 29, 2026106 ms
Sep 5, 2026112 ms
Sep 12, 2026115 ms
Sep 19, 2026115 ms
Sep 26, 2026110 ms
Oct 3, 2026110 ms
Oct 10, 2026104 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 akdeniz.edu.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akdeniz.edu.tr at 1.2 s1.2 s
  2. akdeniz.edu.tr at 2.4 s2.4 s
  3. akdeniz.edu.tr at 3.7 s3.7 s
  4. akdeniz.edu.tr at 4.9 s4.9 s
  5. akdeniz.edu.tr at 6.1 s6.1 s
  6. akdeniz.edu.tr at 7.3 s7.3 s
  7. akdeniz.edu.tr at 8.5 s8.5 s
  8. akdeniz.edu.tr at 9.8 s9.8 s

Speed

9 to fix44
  • Render-blocking requests

    4.1 s

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

  • Mobile performance score: 44

    44/100

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

  • Use efficient cache lifetimes

    600 ms · 58.3 MB

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

  • Improve image delivery

    55.4 MB

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

  • Reduce unused JavaScript

    300 ms · 73 KiB

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

  • Reduce unused CSS

    300 ms · 46 KiB

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

  • Font display

    300 ms

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

  • Main-thread work: 2.5 s

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

  • 1,699 HTML elements

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

  • Minify CSS

    150 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 308 KiB and 126 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • 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.

1 checks passed
  • Server response: 155 ms

    155 ms

    Your server sent the HTML in 155 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 21.4 s

    21.4 s

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

  • Cumulative Layout Shift: 1.067

    1.067

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bağlantılar HASTANE E-POSTA EBYS AVES OBS KURUMSAL KALİTE E…”.

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • 43 images without width and height

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.00

    0.00

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

  • 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: 562 ms

    562 ms

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

  • Total Blocking Time: 52 ms

    52 ms

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

Images and page weight

4 to fix25
  • Page weight: 58.6 MB in 83 requests

    58.6 MB

    Your homepage downloads 58.6 MB in 83 requests on a phone: images 58.0 MB (54), scripts 269 KiB (8) and fonts 241 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 24 images over 500 KB

    24 images weigh 52.3 MB together. On a phone connection a single image that size takes seconds.

  • 25 images far larger than shown

    34.9 MB

    25 images are downloaded at several times the size a phone draws them, for example e889951f-902a-4e01-9e6f-623c9765a70a.png at 4,000 px wide, shown at 390 px. Resized copies would save about 34.9 MB.

  • 26 images in older formats

    26 images (52.6 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.

  • 5 images below the first screen load straight away

    5 images further down the page (130 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 16.6 g of CO₂ per visit

    16.62 g

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

Accessibility

12 to fixGoogle 7685
  • 10 buttons without a name

    10 buttons have no accessible name, so screen readers announce just “button”.

  • 22 text elements with low contrast

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

  • 2 tap targets too small

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

  • 27 images without alt text

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

  • All page content should be contained by landmarks (13 elements)

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

  • No main landmark

    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)

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

  • 56 links without text

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

  • ARIA role should be appropriate for the element (11 elements)

    ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

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

  • Elements marked as presentational should be consistently ignored (10 elements)

    Elements marked as presentational should be consistently ignored: 10 elements on the page fail this check, rated minor by axe-core.

  • 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.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

7 to fixGoogle 7561
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    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

    No XML sitemap at https://akdeniz.edu.tr/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at akdeniz.edu.tr/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 128 internal links, 281 external

    The homepage links to 128 pages on akdeniz.edu.tr and 281 external pages.

1 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Ana Sayfa - Akdeniz Üniversitesi”.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://akdeniz.edu.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.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix83
  • 3 pages share a title

    /, https://akdeniz.edu.tr/en and https://akdeniz.edu.tr/tr all use the title “Ana Sayfa - Akdeniz Üniversitesi”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://akdeniz.edu.tr/en, https://akdeniz.edu.tr/tr/tanitim-1050, https://akdeniz.edu.tr/tr/misyonumuz_ve_vizyonumuz-1105, https://akdeniz.edu.tr/tr/tarihcemiz-1104, https://akdeniz.edu.tr/tr/kampuste_yasam-1106 and https://akdeniz.edu.tr/tr/2021_yili_idare_faaliyet_raporu-1108 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://akdeniz.edu.tr/en and https://akdeniz.edu.tr/tr have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    265 of 285 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,609 words of copy

    The homepage carries about 1,609 words of visible text.

3 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 akdeniz.edu.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
jQuery
Analytics
Google Analytics

Company

Employees
1,578
Founded
1982

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on akdeniz.edu.tr, including 15 speed issues, 7 SEO 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