Website review, no card needed

kolcuoglu.av.tr logo

kolcuoglu.av.tr website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 74 checks

This review found 33 issues worth fixing on kolcuoglu.av.tr, 7 of them high impact, across 74 checks. The most urgent: page weight: 17.8 MB in 29 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
1.7 s402 msMay 2Oct 17564 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 2026724 ms
May 16, 2026653 ms
May 23, 2026642 ms
May 30, 2026695 ms
Jun 6, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 2026937 ms
Jul 11, 2026834 ms
Jul 18, 2026834 ms
Jul 25, 2026854 ms
Aug 1, 20261.0 s
Aug 8, 20261.3 s
Aug 15, 20261.6 s
Aug 22, 2026934 ms
Aug 29, 2026931 ms
Sep 5, 2026934 ms
Sep 12, 2026889 ms
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 2026797 ms
Oct 10, 2026557 ms
Oct 17, 2026564 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 kolcuoglu.av.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kolcuoglu.av.tr at 0.6 s0.6 s
  2. kolcuoglu.av.tr at 1.1 s1.1 s
  3. kolcuoglu.av.tr at 1.6 s1.6 s
  4. kolcuoglu.av.tr at 2.2 s2.2 s
  5. kolcuoglu.av.tr at 2.7 s2.7 s
  6. kolcuoglu.av.tr at 3.3 s3.3 s
  7. kolcuoglu.av.tr at 3.8 s3.8 s
  8. kolcuoglu.av.tr at 4.4 s4.4 s

Speed

6 to fix71
  • Use efficient cache lifetimes

    450 ms · 1.8 MB

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

  • Mobile performance score: 71

    71/100

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

  • Font display

    750 ms

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

  • Improve image delivery

    681 KiB

    7 images could be 681 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • Reduce unused JavaScript

    300 ms · 60 KiB

    About 60 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

    150 ms · 24 KiB

    About 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 71. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Time to Interactive: 5.9 s

    5.9 s

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

  • 6 images without width and height

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

9 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: 0.6 s

    0.6 s

    Real visitors wait 0.6 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: 0.3 s

    0.3 s

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

  • Real-user TTFB: 260 ms

    260 ms

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

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

    -44%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 9 ms

    9 ms

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

Images and page weight

1 to fix70
  • Page weight: 17.8 MB in 29 requests

    17.8 MB

    Your homepage downloads 17.8 MB in 29 requests on a phone: media 14.4 MB (2), images 2.5 MB (20) and fonts 801 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (93 KiB) is 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.

  • About 5.1 g of CO₂ per visit

    5.05 g

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

2 checks passed
  • 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 8890
  • 9 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

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

1 checks passed
  • 22 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

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

  • Title is short (10 characters)

    Your title is only 10 characters: “Home | KDK”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (43 characters)

    Your meta description is only 43 characters: “Kolcuoglu Demirkan Koçaklı Attorneys at Law”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 7 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 33 internal links, 2 external

    The homepage links to 33 pages on kolcuoglu.av.tr and 2 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.kolcuoglu.av.tr/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kolcuoglu.av.tr/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    53%

    The HTML your server sends has 1,952 of the 3,663 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.kolcuoglu.av.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
  • 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.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://www.kolcuoglu.av.tr/home 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.

  • 2 pages share a title

    / and https://www.kolcuoglu.av.tr/home all use the title “Home | KDK”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.kolcuoglu.av.tr/fr has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages share a meta description

    https://www.kolcuoglu.av.tr/home, https://www.kolcuoglu.av.tr/who-we-are, https://www.kolcuoglu.av.tr/the-team, https://www.kolcuoglu.av.tr/practice-areas, https://www.kolcuoglu.av.tr/german-desk and https://www.kolcuoglu.av.tr/french-desk and 5 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.kolcuoglu.av.tr/home, https://www.kolcuoglu.av.tr/who-we-are, https://www.kolcuoglu.av.tr/the-team, https://www.kolcuoglu.av.tr/practice-areas, https://www.kolcuoglu.av.tr/german-desk and https://www.kolcuoglu.av.tr/french-desk and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.kolcuoglu.av.tr/practice-areas, https://www.kolcuoglu.av.tr/contact, https://www.kolcuoglu.av.tr/careers and https://www.kolcuoglu.av.tr/recent-promotions 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.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 10087
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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.

  • 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 3,663 words of copy

    The homepage carries about 3,663 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 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 kolcuoglu.av.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on kolcuoglu.av.tr, including 10 speed issues, 6 SEO issues and 3 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