Website review, no card needed
addax.com.tr website review
Visit site (opens in a new tab)Reviewed 19 October 202658 issues · 92 checks
This review found 58 issues worth fixing on addax.com.tr, 26 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
51FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.7 s |
| May 2, 2026 | 4.7 s |
| May 9, 2026 | 4.7 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 252 ms |
| May 2, 2026 | 250 ms |
| May 9, 2026 | 246 ms |
| May 16, 2026 | 245 ms |
| May 23, 2026 | 242 ms |
| May 30, 2026 | 241 ms |
| Jun 6, 2026 | 242 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 251 ms |
| Jun 27, 2026 | 256 ms |
| Jul 4, 2026 | 262 ms |
| Jul 11, 2026 | 262 ms |
| Jul 18, 2026 | 260 ms |
| Jul 25, 2026 | 259 ms |
| Aug 1, 2026 | 256 ms |
| Aug 8, 2026 | 262 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 275 ms |
| Aug 29, 2026 | 282 ms |
| Sep 5, 2026 | 280 ms |
| Sep 12, 2026 | 277 ms |
| Sep 19, 2026 | 275 ms |
| Sep 26, 2026 | 271 ms |
| Oct 3, 2026 | 269 ms |
| Oct 10, 2026 | 266 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.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Reduce unused JavaScript
7.3 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.
Use efficient cache lifetimes
6.8 s · 1.9 MB64 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Render-blocking requests
3.1 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Mobile performance score: 7
7/100Your mobile performance score is 7 (desktop: 19). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Facebook and others), adding 3.3 MB and 2.5 s of main-thread time.
Reduce unused CSS
750 ms · 193 KiBAbout 193 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 744 ms
744 msGoogle Tag Manager costs a phone 744 ms of main-thread work and 678 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.
Minify JavaScript
600 ms · 202 KiB202 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 766 ms. During a long task the page ignores taps.
Cloudflare CDN adds 589 ms
589 msCloudflare CDN costs a phone 589 ms of main-thread work and 30 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.
Legacy JavaScript
350 ms · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Facebook adds 274 ms
274 msFacebook costs a phone 274 ms of main-thread work and 325 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.
biens.ai adds 257 ms
257 msbiens.ai costs a phone 257 ms of main-thread work and 325 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.
farktorcdn.com adds 125 ms
125 msfarktorcdn.com costs a phone 125 ms of main-thread work and 1.5 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
26 KiB26 KiB could be saved by minifying CSS.
Improve image delivery
22 KiB2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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 LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.74
0.74For real visitors the layout shifts by 0.74 (75th percentile). Good is under 0.1.
First Contentful Paint: 12.7 s
12.7 sThe first text or image appears after 12.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 27.9 s
27.9 sYour largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.0 s
35.0 sThe page becomes fully interactive after 35.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.053
1.053The layout shifts by 1.053 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user INP: 269 ms
269 msReal visitors wait 269 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 825 ms
825 msReal visitors wait 825 ms for your server to start answering (75th percentile). Good is under 800 ms.
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 252 ms to 266 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.7 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.0 MB in 175 requests
6.0 MBYour homepage downloads 6.0 MB in 175 requests on a phone: scripts 2.8 MB (64), images 1.3 MB (11) and fonts 935 KiB (5). Under 2 MB keeps phones on slow connections fast.
18 images far larger than shown
1.9 MB18 images are downloaded at several times the size a phone draws them, for example Fr-55002182242024133908_logo.svg-addax.svg-beyaz-1.svg at 17,078 px wide, shown at 224 px. Resized copies would save about 1.9 MB.
3 images below the first screen load straight away
3 images further down the page (496 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (226 KiB) is 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.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 204.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
12 buttons without a name
12 buttons have no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (50 elements)
All page content should be contained by landmarks: 50 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.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
27 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 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.
Meta description is long (165 characters)
Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 4 problems
Structured data found (Organization and WebSite) but with 4 problems, for example “WebSite: missing name”.
73 internal links, 7 external
The homepage links to 73 pages on addax.com.tr and 7 external pages.
5 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Yeni Sezon Kıyafetler | Son Moda Kıyafet Modelleri addax`ta!”.
Canonical URL set
The canonical URL is https://www.addax.com.tr/.
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.addax.com.tr/sitemap.xml.
AI search readiness
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 description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (176 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.addax.com.tr/llms.txt (3 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.addax.com.tr/sepet has no <title>, so Google invents the link text in results.
2 pages share a title
/ and https://www.addax.com.tr/yeni-urunler all use the title “Yeni Sezon Kıyafetler | Son Moda Kıyafet Modelleri addax`ta!”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.addax.com.tr/sepet has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.addax.com.tr/yeni-urunler, https://www.addax.com.tr/sweatshirt, https://www.addax.com.tr/hirka, https://www.addax.com.tr/triko-kazak, https://www.addax.com.tr/bluz and https://www.addax.com.tr/sepet and 9 others 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 45 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.addax.com.tr/.
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…”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
67 of 82 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 254 words of copy
The homepage carries about 254 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Türkiye - TRY”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, TikTok Pixel and Cloudflare Web Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 1 more (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
40 other companies contacted
Loading the homepage contacts 40 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 addax.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 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 58 issues on addax.com.tr, including 28 speed issues, 3 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.