Website review, no card needed
aygaz.com.tr website review
Visit site (opens in a new tab)Reviewed 29 October 202651 issues · 83 checks
This review found 51 issues worth fixing on aygaz.com.tr, 26 of them high impact, across 83 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 269 ms |
| May 16, 2026 | 267 ms |
| May 23, 2026 | 270 ms |
| May 30, 2026 | 267 ms |
| Jun 6, 2026 | 266 ms |
| Jun 13, 2026 | 264 ms |
| Jun 20, 2026 | 264 ms |
| Jun 27, 2026 | 269 ms |
| Jul 4, 2026 | 274 ms |
| Jul 11, 2026 | 277 ms |
| Jul 18, 2026 | 278 ms |
| Jul 25, 2026 | 282 ms |
| Aug 1, 2026 | 289 ms |
| Aug 8, 2026 | 292 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 300 ms |
| Aug 29, 2026 | 288 ms |
| Sep 5, 2026 | 281 ms |
| Sep 12, 2026 | 278 ms |
| Sep 19, 2026 | 275 ms |
| Sep 26, 2026 | 278 ms |
| Oct 3, 2026 | 276 ms |
| Oct 10, 2026 | 272 ms |
| Oct 17, 2026 | 269 ms |
| Oct 24, 2026 | 267 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.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.4 s
9.6 s
Speed
Reduce unused JavaScript
23.6 s · 3.6 MBAbout 3.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 23.6 s faster on a phone.
Improve image delivery
1.9 s · 1.2 MB16 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
YouTube adds 2.0 s
2.0 sYouTube costs a phone 2.0 s of main-thread work and 5.8 MB 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.
Reduce unused CSS
2.1 s · 128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Main-thread work: 16.3 s
A phone's processor spends 16.3 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
1.1 s · 359 KiB13 files are served with short cache lifetimes, so returning visitors download them again (359 KiB).
11,661 HTML elements
The page has 11,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 11
11/100Your mobile performance score is 11. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 7.0 MB and 3.1 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 703 ms. During a long task the page ignores taps.
Document request latency
650 msThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
637 msReduce initial server response time. Google estimates savings of 637 ms on a phone.
Google Tag Manager adds 491 ms
491 msGoogle Tag Manager costs a phone 491 ms of main-thread work and 527 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
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Server response: 737 ms
737 msYour server takes 737 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 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.
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: 761 ms
761 msReal visitors wait 761 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
First Contentful Paint: 16.4 s
16.4 sThe first text or image appears after 16.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 50.7 s
50.7 sYour largest element takes 50.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kamp Mobilyaları'nda %30'a Varan İndirim”.
Speed Index: 23.7 s
23.7 sVisually, the page fills in at 23.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 63.7 s
63.7 sThe page becomes fully interactive after 63.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.464
0.464The layout shifts by 0.464 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 LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 933 ms
933 msReal visitors wait 933 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 269 ms to 267 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.0 MB in 296 requests
12.0 MBYour homepage downloads 12.0 MB in 296 requests on a phone: scripts 6.7 MB (67), images 3.9 MB (104) and HTML 604 KiB (11). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
663 KiB6 images are downloaded at several times the size a phone draws them, for example 825-web-202610010745422.webp at 3,600 px wide, shown at 328 px. Resized copies would save about 663 KiB.
An image on the first screen is lazy-loaded
0-web-202610180131251.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.4 g of CO₂ per visit
3.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.41 g of CO₂e: 409.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
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.
All page content should be contained by landmarks (1,407 elements)
All page content should be contained by landmarks: 1,407 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (19 elements)
Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 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.
Structured data has 2 problems
Structured data found (untyped) but with 2 problems, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 1 (line 1 )”.
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.
105 internal links, 23 external
The homepage links to 105 pages on aygaz.com.tr and 23 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “AYGAZ Resmi Sitesi. Doğalgaz, LPG, Tüp, Otogaz, Tüpgaz, Dökme Gaz ve Cihaz fiyatları ve özellikleri, Kampanyalar, Satış…”.
Title: 58 characters
Your title is a healthy 58 characters: “AYGAZ | Tüp - LPG - Otogaz - Tüpgaz - Doğalgaz - Dökme Gaz”.
Canonical URL set
The canonical URL is https://www.aygaz.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.aygaz.com.tr/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
13%A phone browser shows 5,117 words, but the HTML your server sends has only 659. 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 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.
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.
llms.txt published
The site publishes https://www.aygaz.com.tr/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
/ and https://www.aygaz.com.tr/fiyatlar/tupgaz all use the title “AYGAZ | Tüp - LPG - Otogaz - Tüpgaz - Doğalgaz - Dökme Gaz”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.aygaz.com.tr/kampanyalar/aygazdan-ekim-ayi-firsati-cmp-1161036 and https://www.aygaz.com.tr/kampanyalar/sonbahara-sicak-bir-dokunus-cmp-1161036 use the same meta description. A description written for each page earns more clicks.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://www.aygaz.com.tr/fiyatlar/otogaz, whose canonical is //fiyatlar/otogaz. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.aygaz.com.tr/kampanyalar, https://www.aygaz.com.tr/kampanyalar/aygazdan-ekim-ayi-firsati-cmp-1161036, https://www.aygaz.com.tr/kampanyalar/sonbahara-sicak-bir-dokunus-cmp-1161036, https://www.aygaz.com.tr/kampanyalar/kamp-mobilyalarinda-30a-varan-indirim-cmp-1161103, https://www.aygaz.com.tr/kampanyalar/25-indirim-kampanyasi-cmp-1139494 and https://www.aygaz.com.tr/kampanyalar/aygaz-tiri-sehrinizde-cmp-1139650 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.aygaz.com.tr/kampanyalar, https://www.aygaz.com.tr/fiyatlar/tupgaz, https://www.aygaz.com.tr/kampanyalar/kamp-mobilyalarinda-30a-varan-indirim-cmp-1161103, https://www.aygaz.com.tr/kampanyalar/aygaz-tiri-sehrinizde-cmp-1139650 and https://www.aygaz.com.tr/kampanyalar/pesin-fiyatina-taksit-imkani-cmp-1130317 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 third-party cookies
6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Framing 'https://www.youtube.com/' violates the following report-only Content Security Policy directive: "frame-src 'se…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
170 of 186 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 5,117 words of copy
The homepage carries about 5,117 words of visible text.
2 checks passed
1 short form
A short form (0 fields at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 2 mores (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 of them by other companies (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.
27 other companies contacted
Loading the homepage contacts 27 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 aygaz.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
- Next.js
- Hosting
- Borusantelekom
Company
- Founded
- 1961
- Headquarters
- Istanbul
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on aygaz.com.tr, including 27 speed issues, 3 SEO issues and 4 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.