Website review, no card needed
evshop.com.tr website review
Visit site (opens in a new tab)Reviewed 23 October 202643 issues · 76 checks
This review found 43 issues worth fixing on evshop.com.tr, 17 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
72C- #90,689 of 116,487 reviewed websitesbeats 19%
- #56,840 of 66,776 online storesbeats 12%
- #31 of 54 OpenCart storesbeats 36%
Closest competitors among OpenCart stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 227 ms |
| May 9, 2026 | 217 ms |
| May 16, 2026 | 215 ms |
| May 23, 2026 | 215 ms |
| May 30, 2026 | 214 ms |
| Jun 6, 2026 | 214 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 209 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 207 ms |
| Jul 18, 2026 | 205 ms |
| Jul 25, 2026 | 206 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 244 ms |
| Aug 29, 2026 | 310 ms |
| Sep 5, 2026 | 286 ms |
| Sep 12, 2026 | 305 ms |
| Sep 19, 2026 | 318 ms |
| Sep 26, 2026 | 325 ms |
| Oct 3, 2026 | 337 ms |
| Oct 10, 2026 | 349 ms |
| Oct 17, 2026 | 349 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
Speed
5,636 HTML elements
The page has 5,636 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 578 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Improve image delivery
450 ms · 302 KiB3 images could be 302 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 821 KiB and 533 ms of main-thread time.
Reduce unused CSS
300 ms · 244 KiBAbout 244 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 354 ms
354 msGoogle Tag Manager costs a phone 354 ms of main-thread work and 497 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.
Reduce unused JavaScript
299 KiBAbout 299 KiB of JavaScript is downloaded but never used on this page.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
245 KiB36 files are served with short cache lifetimes, so returning visitors download them again (245 KiB).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
1 checks passed
Server response: 295 ms
295 msYour server sent the HTML in 295 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 INP: 625 ms
625 msReal visitors wait 625 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “+3 TAKSİT”.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 57% slower for real visitors
+57%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 227 ms to 349 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 63% slower for real visitors
+63%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 235 ms
235 msScripts block taps and scrolling for 235 ms in total while the page loads. Good is under 200 ms.
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image far larger than shown
15 KiB1 image is downloaded at several times the size a phone draws it, for example de-milano-mutfak-gereçleri-mobil-1080x1080.jpg.webp at 1,080 px wide, shown at 312 px. Resized copies would save about 15 KiB.
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 56.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 70 requests
1.7 MBYour homepage downloads 1.7 MB in 70 requests on a phone: scripts 823 KiB (20), images 445 KiB (34) and fonts 216 KiB (6). That is a lean page.
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.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
787 links without text
787 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (184 elements)
All page content should be contained by landmarks: 184 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 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.
Structured data has 2 problems
Structured data found (Organization, Store and WebSite) but with 2 problems, for example “Organization: missing name”.
No XML sitemap
No XML sitemap at https://evshop.com.tr/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
4 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Alışveriş sitemizden peşinatsız kredi kartsız elden taksitle cep telefonu, taksitle telefon, bilgisayar, televizyon, el…”.
Title: 56 characters
Your title is a healthy 56 characters: “Elden Taksitle Alışveriş - Taksitle Telefon | Evshop AVM”.
Canonical URL set
The canonical URL is https://www.evshop.com.tr/?route=common/home.
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 603 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://evshop.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.evshop.com.tr/.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.evshop.com.tr/catalog/view/theme/journal3/lib/swiper-latest/swiper-bundle.min.…”.
2 checks passed
Tap targets are thumb-sized
866 of 965 tappable elements near the top are at least 24 px.
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 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 603 words of copy
The homepage carries about 603 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Meta Pixel.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
9 other companies contacted
Loading the homepage contacts 9 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 evshop.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
- Framework
- jQuery
- 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 43 issues on evshop.com.tr, including 21 speed issues, 5 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.