Website review, no card needed

ipa.istanbul logo

ipa.istanbul website review

Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 87 checks

This review found 39 issues worth fixing on ipa.istanbul, 12 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
1.5 s1.0 sMay 2Oct 171.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
101 ms76 msMay 2Oct 1783 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202689 ms
May 9, 202694 ms
May 16, 202698 ms
May 23, 202695 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202693 ms
Jun 20, 202690 ms
Jun 27, 202688 ms
Jul 4, 202690 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202688 ms
Aug 1, 202687 ms
Aug 8, 202685 ms
Aug 15, 202680 ms
Aug 22, 202680 ms
Aug 29, 202679 ms
Sep 5, 202681 ms
Sep 12, 202687 ms
Sep 19, 202692 ms
Sep 26, 202686 ms
Oct 3, 202685 ms
Oct 10, 202684 ms
Oct 17, 202683 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 ipa.istanbul (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ipa.istanbul at 0.5 s0.5 s
  2. ipa.istanbul at 1.0 s1.0 s
  3. ipa.istanbul at 1.5 s1.5 s
  4. ipa.istanbul at 2.0 s2.0 s
  5. ipa.istanbul at 2.5 s2.5 s
  6. ipa.istanbul at 3.1 s3.1 s
  7. ipa.istanbul at 3.6 s3.6 s
  8. ipa.istanbul at 4.1 s4.1 s

Speed

7 to fix65
  • Use efficient cache lifetimes

    1.6 s · 2.4 MB

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

  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    200 ms · 2.0 MB

    16 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    620 ms · 119 KiB

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

  • Reduce unused CSS

    310 ms · 50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 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).

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, gtranslate.net and Cloudflare CDN and others), adding 385 KiB and 215 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 134 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.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 458 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “İPA, İstanbul Büyükşehir Belediyesi, sivil toplum, üniversi…”.

  • Cumulative Layout Shift: 0.233

    0.233

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

  • Time to Interactive: 5.4 s

    5.4 s

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

  • 22 images without width and height

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

  • Speed Index: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 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: 1.0 s

    1.0 s

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

  • Real-user INP: 91 ms

    91 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 311 ms

    311 ms

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

  • Total Blocking Time: 144 ms

    144 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

Images and page weight

5 to fix31
  • 1 image over 500 KB

    istanbul-ve-inovasyon-konusmalari-vi-00277.jpeg weighs 885 KiB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    1.1 MB

    6 images are downloaded at several times the size a phone draws them, for example istanbul-ve-inovasyon-konusmalari-vi-00277.jpeg at 4,500 px wide, shown at 177 px. Resized copies would save about 1.1 MB.

  • Page weight: 2.8 MB in 41 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 41 requests on a phone: images 2.1 MB (22), fonts 327 KiB (3) and scripts 280 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.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.

  • An image on the first screen is lazy-loaded

    tcl5slnj-32497.webp 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).

  • About 0.8 g of CO₂ per visit

    0.79 g

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

Accessibility

10 to fixGoogle 7886
  • 1 button without a name

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

  • 18 text elements with low contrast

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

  • 12 tap targets too small

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

  • 8 images without alt text

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

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

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 100 internal links, 13 external

    The homepage links to 100 pages on ipa.istanbul and 13 external pages.

6 checks passed
  • Meta description: 85 characters

    Your meta description is 85 characters: “İstanbul'un bilgisini üreten ve geleceğini birlikte planlayan ortak akıl mekanizaması”.

  • One H1 headline

    Your main headline reads: “İstanbul'un bilgisini üreten ve geleceğini birlikte planlayan ortak akıl mekanizaması”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Anasayfa | İstanbul Planlama Ajansı”.

  • Canonical URL set

    The canonical URL is https://ipa.istanbul/.

  • 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://ipa.istanbul/sitemap.xml.

AI search readiness

1 to fix88
  • 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://ipa.istanbul/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 (465 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 9 pages without a meta description

    https://ipa.istanbul/genel-mudur-mesaji, https://ipa.istanbul/hakkimizda, https://ipa.istanbul/organizasyon-semasi, https://ipa.istanbul/duyurular, https://ipa.istanbul/kvkk/kisisel-veri-koruma and https://ipa.istanbul/hizmetlerimiz/planlama-ve-katilim and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ipa.istanbul/Kurumsal, whose canonical is https://ipa.istanbul/kurumsal. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages slow to respond

    https://ipa.istanbul/Kurumsal, https://ipa.istanbul/genel-mudur-mesaji and https://ipa.istanbul/hakkimizda took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • 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 14 pages that loaded have a <title>.

Best practices

Google 96100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    25 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 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 331 words of copy

    The homepage carries about 331 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 ipa.istanbul, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on ipa.istanbul, including 12 speed issues, 3 SEO issues and 5 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