Website review, no card needed
aksa.com.tr website review
Visit site (opens in a new tab)Reviewed 30 October 202645 issues · 89 checks
This review found 45 issues worth fixing on aksa.com.tr, 16 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 3.4 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 136 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
Use efficient cache lifetimes
1.8 s · 9.5 MB69 files are served with short cache lifetimes, so returning visitors download them again (9.5 MB).
Render-blocking requests
2.2 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Reduce unused JavaScript
1.2 s · 493 KiBAbout 493 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Improve image delivery
150 ms · 2.3 MB23 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, jQuery CDN and LinkedIn Ads and others), adding 815 KiB and 518 ms of main-thread time.
Reduce unused CSS
480 ms · 72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 480 ms faster on a phone.
Google Tag Manager adds 358 ms
358 msGoogle Tag Manager costs a phone 358 ms of main-thread work and 719 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
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
1,541 HTML elements
The page has 1,541 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
270 ms · 48 KiB48 KiB could be saved by minifying JavaScript.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Minify CSS
120 ms · 6 KiB6 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 549 ms of it running JavaScript. That is comfortably low.
Server response: 113 ms
113 msYour server sent the HTML in 113 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.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Diesel Generators”.
Time to Interactive: 16.4 s
16.4 sThe page becomes fully interactive after 16.4 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
47 images without width and height
47 images have no width and height attributes, so the layout jumps as each one loads.
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.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 144 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 615 ms
615 msReal visitors wait 615 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 43% faster for real visitors
-43%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 119 ms
119 msScripts block the page for only 119 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.0 MB in 100 requests
14.0 MBYour homepage downloads 14.0 MB in 100 requests on a phone: media 9.4 MB (2), images 3.3 MB (48) and scripts 1,020 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
buyuk.webp weighs 764 KiB. On a phone connection a single image that size takes seconds.
17 images below the first screen load straight away
17 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
23 KiB1 image is downloaded at several times the size a phone draws it, for example buyuk.webp at 600 px wide, shown at 150 px. Resized copies would save about 23 KiB.
1 image in older formats
1 image (57 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 4.0 g of CO₂ per visit
3.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.97 g of CO₂e: 476.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Aksa Jeneratör”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (14 characters)
Your meta description is only 14 characters: “Aksa Generator”. 70 to 160 characters is enough to sell the click.
3 H1 headlines
There are 3 <h1> headlines (“Power Your Future”, “Sectors” and “News”). One clear main headline is easier for people and search engines.
26 links crawlers can't follow
26 links have no real href, so search engines can't follow them.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 robots.txt
There is no robots.txt at aksa.com.tr/robots.txt, the first file search crawlers ask for.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
184 internal links, 13 external
The homepage links to 184 pages on aksa.com.tr and 13 external pages.
2 checks passed
Structured data in place
Structured data found: Organization.
XML sitemap found
Your XML sitemap is reachable at https://aksa.com.tr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://aksa.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
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 (1,427 words), so crawlers that don't run JavaScript still read it.
Other pages
14 linked pages are broken
Your homepage links to https://aksa.com.tr/tr/corporate/kazanci-holding, https://aksa.com.tr/tr/corporate/about-us, https://aksa.com.tr/tr/corporate/our-founder, https://aksa.com.tr/tr/corporate/executive-board, https://aksa.com.tr/tr/corporate/corporate-identity and https://aksa.com.tr/tr/corporate/publications and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://aksa.com.tr/tr/en and https://aksa.com.tr/tr-en/products/12465 all use the title “Aksa Jeneratör”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
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 1 page that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://webcdn.aksa.com.tr/CDN/tr-en/images/menu/132.webp.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
84 of 85 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,641 words of copy
The homepage carries about 1,641 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Contact Form”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Contact Form” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and LinkedIn Insight (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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 aksa.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
- Hosting
- AWS
Company
- Founded
- 1968
- Headquarters
- Beykoz
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on aksa.com.tr, including 18 speed issues, 8 SEO issues and 2 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.