Website review, no card needed
efor.com.tr website review
Visit site (opens in a new tab)Reviewed 25 October 202654 issues · 89 checks
This review found 54 issues worth fixing on efor.com.tr, 22 of them high impact, across 89 checks. The most urgent: render-blocking 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 300 ms |
| May 9, 2026 | 295 ms |
| May 16, 2026 | 290 ms |
| May 23, 2026 | 284 ms |
| May 30, 2026 | 290 ms |
| Jun 6, 2026 | 303 ms |
| Jun 13, 2026 | 313 ms |
| Jun 20, 2026 | 324 ms |
| Jun 27, 2026 | 316 ms |
| Jul 4, 2026 | 314 ms |
| Jul 11, 2026 | 312 ms |
| Jul 18, 2026 | 295 ms |
| Jul 25, 2026 | 301 ms |
| Aug 1, 2026 | 306 ms |
| Aug 8, 2026 | 313 ms |
| Aug 15, 2026 | 327 ms |
| Aug 22, 2026 | 317 ms |
| Aug 29, 2026 | 303 ms |
| Sep 5, 2026 | 296 ms |
| Sep 12, 2026 | 285 ms |
| Sep 19, 2026 | 281 ms |
| Sep 26, 2026 | 273 ms |
| Oct 3, 2026 | 272 ms |
| Oct 10, 2026 | 269 ms |
| Oct 17, 2026 | 274 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.7 s
1.3 s
2.0 s
2.7 s
3.3 s
4.0 s
4.7 s
5.3 s
Speed
Render-blocking requests
2.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
750 ms · 1,015 KiB12 images could be 1,015 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (ticimax.cloud, Google Tag Manager and TikTok and others), adding 4.0 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
889 KiBAbout 889 KiB of JavaScript is downloaded but never used on this page.
ticimax.cloud adds 543 ms
543 msticimax.cloud costs a phone 543 ms of main-thread work and 2.7 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.
Reduce unused CSS
450 ms · 103 KiBAbout 103 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
425 KiB23 files are served with short cache lifetimes, so returning visitors download them again (425 KiB).
Google Tag Manager adds 263 ms
263 msGoogle Tag Manager costs a phone 263 ms of main-thread work and 481 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 294 ms. During a long task the page ignores taps.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
45 KiB45 KiB could be saved by minifying JavaScript.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 100 ms
100 msYour server sent the HTML in 100 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 FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “https://www.efor.com.tr/yeni-gelenler”.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.268
0.268The layout shifts by 0.268 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 260 ms
260 msScripts block taps and scrolling for 260 ms in total while the page loads. Good is under 200 ms.
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 300 ms to 274 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.2 MB in 119 requests
4.2 MBYour homepage downloads 4.2 MB in 119 requests on a phone: images 2.0 MB (56), scripts 1.6 MB (27) and fonts 370 KiB (6). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
614 KiB3 images are downloaded at several times the size a phone draws them, for example comfort-fit-bisiklet-yaka-gofre-pamukl--9d69f.jpg at 940 px wide, shown at 127 px. Resized copies would save about 614 KiB.
6 images below the first screen load straight away
6 images further down the page (359 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (174 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 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (7 elements)
Images must have alternative text: 7 elements on the page fail this check, rated critical by axe-core.
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (49 elements)
All page content should be contained by landmarks: 49 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.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
38 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: 38 passed and 11 failed. 3 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.
23 links crawlers can't follow
23 links have no real href, so search engines can't follow them.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
201 internal links, 7 external
The homepage links to 201 pages on efor.com.tr and 7 external pages.
5 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Slim fit erkek giyimin öncülerinden Efor; en şık erkek kıyafetleri ile gardırobunuzu şekillendiriyor. Damatlık, takım e…”.
Title: 35 characters
Your title is a healthy 35 characters: “Erkek Giyimde Modanın Adresi | EFOR”.
Canonical URL set
The canonical URL is https://www.efor.com.tr/.
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.efor.com.tr/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (723 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.efor.com.tr/llms.txt (22 KiB, 109 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 found) and read each the way a search engine does.
7 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.
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
26 small tap targets
26 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.personaclick.com/shop_css/b05e7aa80232af0ba083dd61bd5932.css' from origin 'htt…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
A 12-field form
Your longest form asks for 12 fields (0 required). Every extra field lowers completion.
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 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 351 words of copy
The homepage carries about 351 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, PostHog, TikTok Pixel and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
29 other companies contacted
Loading the homepage contacts 29 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 efor.com.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 © 2024.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on efor.com.tr, including 24 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.