Why site speed matters
A slow site costs you visitors and sales: most people leave a page that takes more than about three seconds to load, and Google uses Core Web Vitals — how fast and stable your pages feel — as a ranking signal. Faster pages mean better rankings, lower bounce, and more conversions from the same traffic.
The two biggest speed levers are serving content from close to the visitor and sending fewer, smaller bytes. A CDN does both, without you rewriting your site or moving your hosting.
How a CDN cuts your load time and TTFB
cdn.com.tr caches your pages, images and assets on edge servers in Türkiye and Europe and serves each visitor from the nearest one. That shortens the round trip and drops your Time to First Byte (TTFB) — the delay before the browser gets anything. Your origin server also does far less work, so it stays fast under load.
With edge locations inside Turkey, Turkish visitors are served from an edge in-country — the shortest possible round trip — while European edge locations keep audiences abroad fast too.
Automatic image optimization and compression
Images are usually the heaviest part of a page. Image optimization is a switch for your whole account or a single delivery rule: the edge converts JPEG and PNG images to WebP, or to AVIF and WebP if you choose WebP + AVIF for the account, and each browser gets a format it accepts; browsers that accept neither get the image in its original format. At full size, a newly converted image goes out only when it is smaller than the original, and if a conversion fails the edge serves the original image instead. There is no plugin to install, no media library to re-export and no image URL to change; processing counts toward your monthly quota. Our image CDN guide explains what happens to an image on its way through the edge. HTML, CSS, JavaScript, JSON and SVG are compressed with Brotli or Gzip, whichever the browser supports, and HTTP/2 and HTTP/3 keep requests flowing in parallel.
The result is fewer, smaller bytes over the wire and a measurably faster Largest Contentful Paint (LCP) — the Core Web Vital most sites struggle with — all handled for you at the edge.
Two ways to do this: leave the site alone, or take control
For most sites the first is the right answer. You point a DNS record at us, set the cache durations in the panel under Delivery Rules, and image conversion and compression happen at the edge. Nothing in your code changes and you do not need a developer.
If you do have a developer, the second way works out cleaner: publish the right Cache-Control header from your own server. On a rule with Use browser cache time on, the edge follows that header — and the header reaches the visitor's browser unchanged, so the same visitor's second request never touches the network at all. A fixed duration set in the panel cannot do that: it speeds up the edge only, and rewrites the header the browser sees with our value.
One or the other per rule, never both — but you can split the rules by content type: a year for versioned filenames, a few minutes for listing pages that change often. Which directive to use when is covered in the Cache-Control and max-age guide.
Works with any site — WordPress, WooCommerce, OpenCart, custom
You do not need a special platform or a rebuild. Whether you run WordPress, WooCommerce, OpenCart, a headless front end or a hand-built site, you keep it where it is and route it through the CDN with a single DNS change. Static content is served fast from the edge while dynamic pages like cart and checkout keep working normally.
For stores this matters most: faster product and category pages lift conversion directly, and the same edge blocks bots and attacks that slow a shop down.
Simple setup, honest pricing
Getting faster is a short DNS change, not a migration: create an account, add your domain, point one record at the edge, and SSL is issued automatically. Most sites are live within minutes, and the speed gain shows up immediately in your PageSpeed and Core Web Vitals scores.
Plans start at $9/month with WAF, DDoS protection and automatic SSL included, plus a risk-free trial. Cancel any time and keep the trial, or get a same-day refund. No lock-in.
Website Speed FAQ
How does a CDN make my website faster?
A CDN serves cached copies of your pages, images and assets from an edge server near each visitor instead of one distant origin. That lowers Time to First Byte and load time, offloads your server, and — with cdn.com.tr — adds automatic WebP and AVIF images, Brotli compression and HTTP/3 on top.
Will it improve my Core Web Vitals and PageSpeed score?
Almost always. Serving from a nearby edge improves TTFB, and automatic image optimization and compression improve LCP — the two vitals most sites fail. You keep your site as-is; the gains come from the edge.
Do I need to change my hosting or rebuild my site?
No. You keep your current hosting and site. Routing through the CDN is a single DNS change; static content is served from the edge while dynamic pages keep working normally. Most sites are live within minutes.
Does it work with WordPress, WooCommerce or OpenCart?
Yes — with any platform. WordPress, WooCommerce, OpenCart, custom PHP or headless sites all work. For stores, faster product and category pages lift conversion, and the same edge blocks bots and attacks.
How much does it cost?
Plans start at $9/month with the CDN, WAF, DDoS protection and automatic SSL included, plus a risk-free trial. You can cancel any time and keep the trial, or get a same-day refund.
I set my own Cache-Control headers. Will the CDN respect them?
Yes — that is the default on new accounts. On a rule with Use browser cache time on, your origin's Cache-Control, s-maxage or Expires sets the edge duration, and the header reaches the browser unchanged. Enter a Cache Expire Time on that rule and the origin headers are ignored, and the header the browser gets is rewritten with our value. Two things to watch: a response carrying Set-Cookie is never cached, and where Image Optimization is on, for the account or for that rule, images are held for 365 days whatever the origin says.