pamukkale.com.tr

Readiness by lane

Green: pamukkale.com.tr. Thin bar: Trains & Public Transport peer median.

Priority fixes for pamukkale.com.tr

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 38 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   28% of Trains & Public Transport peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 19 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   43% of Trains & Public Transport peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 38 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   43% of Trains & Public Transport peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   9.5% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

What pamukkale.com.tr already does well

Practices fewer than half of Trains & Public Transport peers use.

• HTTP/3 advertisedHTTP/3 advertised.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• Structured data presentJSON-LD structured data found.33% of peers

What we saw

Homepage checked

https://www.pamukkale.com.tr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-01

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

81 KB, gzip

Images on homepage

38 (png 26)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Trains & Public Transport sites

• at-bus.it78
• infobus.eu79
• ns.nl84
• transilien.com79
• zditm.szczecin.pl84

Trains & Public Transport readiness benchmark