Website review, no card needed
inkilap.com website review
Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 88 checks
This review found 42 issues worth fixing on inkilap.com, 22 of them high impact, across 88 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 147 ms |
| May 9, 2026 | 150 ms |
| May 16, 2026 | 149 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 143 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 114 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 120 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
How it loaded on a phone
0.9 s
1.9 s
2.8 s
3.7 s
4.6 s
5.6 s
6.5 s
7.4 s
Speed
Improve image delivery
1.4 s · 11.6 MB118 images could be 11.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Use efficient cache lifetimes
2.9 s · 7.2 MB152 files are served with short cache lifetimes, so returning visitors download them again (7.2 MB).
Render-blocking requests
6.6 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.6 s.
Reduce unused CSS
3.0 s · 546 KiBAbout 546 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41 (desktop: 73). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,465 HTML elements
The page has 3,465 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 430 KiBAbout 430 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 992 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 268 ms
268 msGoogle Tag Manager costs a phone 268 ms of main-thread work and 338 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 469 KiB and 379 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Minify JavaScript
53 KiB53 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 73 but mobile only 41. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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: 144 ms
144 msYour server sent the HTML in 144 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Leo Buscaglia”.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.334
0.334The layout shifts by 0.334 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
84 images without width and height
84 images have no width and height attributes, so the layout jumps as each one loads.
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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 148 ms
148 msReal visitors wait 148 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 767 ms
767 msReal visitors wait 767 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 147 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 75 ms
75 msScripts block the page for only 75 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.7 MB in 181 requests
14.7 MBYour homepage downloads 14.7 MB in 181 requests on a phone: images 12.7 MB (124), scripts 937 KiB (19) and stylesheets 596 KiB (15). Under 2 MB keeps phones on slow connections fast.
26 images far larger than shown
2.4 MB26 images are downloaded at several times the size a phone draws them, for example leo-buscaglia-a36sp.webp at 1,800 px wide, shown at 366 px. Resized copies would save about 2.4 MB.
18 images in older formats
18 images (5.4 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
kocalar-696ce.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 4.2 g of CO₂ per visit
4.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.18 g of CO₂e: 501.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
82 tap targets too small
82 tap targets are too small or too close together to hit reliably with a finger.
40 text elements with low contrast
40 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
2 form fields without a label
2 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 132 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
460 internal links, 20 external
The homepage links to 460 pages on inkilap.com and 20 external pages.
6 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “İnkılâp Kitabevi | Online Satış - En Çok Satanlar & Yeni Çıkanlar”.
Canonical URL set
The canonical URL is https://www.inkilap.com/.
Structured data in place
Structured data found: 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.inkilap.com/sitemap.xml.
AI search readiness
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://www.inkilap.com/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,928 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.inkilap.com/sepet and https://www.inkilap.com/siparisler are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 179 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 14 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.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.inkilap.com/.
97 small tap targets
97 of 250 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: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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,685 words of copy
The homepage carries about 1,685 words of visible text.
3 checks passed
3 short forms
3 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
10 other companies contacted
Loading the homepage contacts 10 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 inkilap.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on inkilap.com, including 17 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.