Website review, no card needed
ipekyol.com.tr website review
Visit site (opens in a new tab)Reviewed 28 October 202646 issues · 91 checks
This review found 46 issues worth fixing on ipekyol.com.tr, 16 of them high impact, across 91 checks. The most urgent: page weight: 14.6 MB in 128 requests. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 616 ms |
| May 16, 2026 | 598 ms |
| May 23, 2026 | 597 ms |
| May 30, 2026 | 566 ms |
| Jun 6, 2026 | 551 ms |
| Jun 13, 2026 | 546 ms |
| Jun 20, 2026 | 549 ms |
| Jun 27, 2026 | 567 ms |
| Jul 4, 2026 | 577 ms |
| Jul 11, 2026 | 584 ms |
| Jul 18, 2026 | 578 ms |
| Jul 25, 2026 | 578 ms |
| Aug 1, 2026 | 574 ms |
| Aug 8, 2026 | 581 ms |
| Aug 15, 2026 | 593 ms |
| Aug 22, 2026 | 553 ms |
| Aug 29, 2026 | 509 ms |
| Sep 5, 2026 | 472 ms |
| Sep 12, 2026 | 432 ms |
| Sep 19, 2026 | 437 ms |
| Sep 26, 2026 | 438 ms |
| Oct 3, 2026 | 421 ms |
| Oct 10, 2026 | 401 ms |
| Oct 17, 2026 | 392 ms |
| Oct 24, 2026 | 384 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
1.6 s
3.2 s
4.7 s
6.3 s
7.9 s
9.5 s
11.0 s
12.6 s
Speed
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 688 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.
Main-thread work: 11.5 s
A phone's processor spends 11.5 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,855 HTML elements
The page has 4,855 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
900 ms · 10.5 MB37 files are served with short cache lifetimes, so returning visitors download them again (10.5 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Insider and mindbehind.com and others), adding 13.1 MB and 3.8 s of main-thread time.
Reduce unused JavaScript
910 ms · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.
mncdn.com adds 0 ms
0 msmncdn.com costs a phone 0 ms of main-thread work and 9.9 MB 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.
Insider adds 929 ms
929 msInsider costs a phone 929 ms of main-thread work and 504 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.
mindbehind.com adds 759 ms
759 msmindbehind.com costs a phone 759 ms of main-thread work and 1.2 MB 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 871 ms. During a long task the page ignores taps.
Google CDN adds 556 ms
556 msGoogle CDN costs a phone 556 ms of main-thread work and 738 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.
Render-blocking requests
600 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Improve image delivery
300 ms · 90 KiB4 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 298 ms
298 msYour server sent the HTML in 298 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user CLS: 0.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
Time to Interactive: 31.0 s
31.0 sThe page becomes fully interactive after 31.0 s. Good is under 3.8 s.
Total Blocking Time: 3.7 s
3.7 sScripts block taps and scrolling for 3.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 418 ms
418 msReal visitors wait 418 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 510 ms
510 msReal visitors wait 510 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 616 ms to 384 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.6 MB in 128 requests
14.6 MBYour homepage downloads 14.6 MB in 128 requests on a phone: media 9.6 MB (2), scripts 3.8 MB (47) and other files 491 KiB (37). Under 2 MB keeps phones on slow connections fast.
About 4.1 g of CO₂ per visit
4.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.13 g of CO₂e: 495.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
28 form fields without a label
28 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.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 3 failed. 4 mores 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.
28 links crawlers can't follow
28 links have no real href, so search engines can't follow them.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
175 internal links, 9 external
The homepage links to 175 pages on ipekyol.com.tr and 9 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “En çok sevilen Kadın Giyim, Ayakkabı ve Aksesuar Modellerini ipekyol.com.tr'de bulabilirsiniz. Türkiye'nin en sevilen m…”.
Title: 51 characters
Your title is a healthy 51 characters: “Ipekyol | Kadın Giyim, Ayakkabı ve Aksesuar Markası”.
Canonical URL set
The canonical URL is https://www.ipekyol.com.tr/.
Structured data in place
Structured data found: Organization and WebSite.
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.ipekyol.com.tr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.ipekyol.com.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.
3 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (410 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://www.ipekyol.com.tr/sezon-seckileri-reklam and https://www.ipekyol.com.tr/kadin-dis-giyim have no <title>, so Google invents the link text in results.
3 pages without a meta description
https://www.ipekyol.com.tr/sepette-indirim, https://www.ipekyol.com.tr/sezon-seckileri-reklam and https://www.ipekyol.com.tr/kadin-dis-giyim 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://www.ipekyol.com.tr/giyim/triko-modelleri, whose canonical is https://www.ipekyol.com.tr/giyim/triko-kazak-modelleri. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.ipekyol.com.tr/sezon-seckileri-reklam and https://www.ipekyol.com.tr/kadin-dis-giyim have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.ipekyol.com.tr/koleksiyon, https://www.ipekyol.com.tr/sepette-indirim, https://www.ipekyol.com.tr/kadin-dis-giyim and https://www.ipekyol.com.tr/rahat-ve-konforlu took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 126 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.
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.
Best practices
12 small tap targets
12 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “[EmosAI] Request timeout after 3000 ms”.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
Missing source maps
Large scripts ship without source maps.
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.
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: 1 trust badge. 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.
Only about 152 words
The homepage has only about 152 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
32 other companies contacted
Loading the homepage contacts 32 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 ipekyol.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Hwclouds As Ap Huawei Clouds
Company
- Founded
- 1986
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on ipekyol.com.tr, including 22 speed issues, 4 SEO issues and 7 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.