Website review, no card needed

abdullahkigili.com logo

abdullahkigili.com website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 90 checks

This review found 40 issues worth fixing on abdullahkigili.com, 17 of them high impact, across 90 checks. The most urgent: main-thread work: 14.0 s. 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.9 s1.6 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
232 ms189 msMay 9Oct 24212 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026194 ms
May 16, 2026201 ms
May 23, 2026210 ms
May 30, 2026215 ms
Jun 6, 2026227 ms
Jun 13, 2026219 ms
Jun 20, 2026215 ms
Jun 27, 2026211 ms
Jul 4, 2026203 ms
Jul 11, 2026203 ms
Jul 18, 2026204 ms
Jul 25, 2026210 ms
Aug 1, 2026215 ms
Aug 8, 2026218 ms
Aug 15, 2026215 ms
Aug 22, 2026211 ms
Aug 29, 2026214 ms
Sep 5, 2026219 ms
Sep 12, 2026216 ms
Sep 19, 2026212 ms
Sep 26, 2026210 ms
Oct 3, 2026202 ms
Oct 10, 2026200 ms
Oct 17, 2026210 ms
Oct 24, 2026212 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 abdullahkigili.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abdullahkigili.com at 1.9 s1.9 s
  2. abdullahkigili.com at 3.8 s3.8 s
  3. abdullahkigili.com at 5.8 s5.8 s
  4. abdullahkigili.com at 7.7 s7.7 s
  5. abdullahkigili.com at 9.6 s9.6 s
  6. abdullahkigili.com at 11.5 s11.5 s
  7. abdullahkigili.com at 13.4 s13.4 s
  8. abdullahkigili.com at 15.3 s15.3 s

Speed

10 to fix34
  • Main-thread work: 14.0 s

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 524 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 34

    34/100

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

  • 7,059 HTML elements

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

  • Improve image delivery

    500 ms · 1.6 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, yapaytech.com and Shopify and others), adding 1.1 MB and 1.7 s of main-thread time.

  • Render-blocking requests

    600 ms

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

  • 20 long tasks on the main thread

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

  • Reduce unused JavaScript

    567 KiB

    About 567 KiB of JavaScript is downloaded but never used on this page.

  • yapaytech.com adds 250 ms

    250 ms

    yapaytech.com costs a phone 250 ms of main-thread work and 265 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Use efficient cache lifetimes

    185 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (185 KiB).

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 64 but mobile only 34. 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

8 to fix33
  • 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: 19.0 s

    19.0 s

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

  • Time to Interactive: 29.6 s

    29.6 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

    Scripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 9.1 s

    9.1 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 477 ms

    477 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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: 566 ms

    566 ms

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

  • Cumulative Layout Shift: 0.072

    0.072

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

Images and page weight

2 to fix64
  • Page weight: 9.5 MB in 293 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 293 requests on a phone: images 7.1 MB (97), scripts 1.2 MB (56) and other files 856 KiB (96). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1_Mobil-Ana-Banner-1125x1440_smokin-tr.jpg 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).

  • 2 images in older formats

    2 images (367 KiB) 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.

  • About 2.7 g of CO₂ per visit

    2.69 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

7 to fixGoogle 7689
  • 16 buttons without a name

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

  • 30 tap targets too small

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

  • 3 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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 (30 elements)

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

  • 27 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 9293
  • Title is short (29 characters)

    Your title is only 29 characters: “Abdullah Kiğılı Exclusive Cut”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 561 internal links, 3 external

    The homepage links to 561 pages on abdullahkigili.com and 3 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Elit bir konsepti tercih eden erkeklerin online alışveriş adresi. Abdullah Kiğılı Exclusive Cut ile erkek modasında zir…”.

  • One H1 headline

    Your main headline reads: “Abdullah Kiğılı Exclusive Cut”.

  • Canonical URL set

    The canonical URL is https://www.abdullahkigili.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.abdullahkigili.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.abdullahkigili.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 6 pages without an H1

    https://www.abdullahkigili.com/pages/favoriler, https://www.abdullahkigili.com/collections/100-wool, https://www.abdullahkigili.com/collections/erkek-kasmir-karisimli-modeller, https://www.abdullahkigili.com/collections/erkek-takim-elbise, https://www.abdullahkigili.com/collections/yunlu-takim-elbise-modelleri and https://www.abdullahkigili.com/collections/erkek-kruvaze-takim-elbise 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 181 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

4 to fixGoogle 6583
  • 17 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'HeroSlideshow' has already been declared”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

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

  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

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

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

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

2 checks passed
  • 37 short forms

    37 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 abdullahkigili.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on abdullahkigili.com, including 18 speed issues, 1 SEO issue and 6 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