Public file inventory
We identify images, stylesheets, scripts and public downloads, then assess their size and update frequency.
Administration
Your website’s static files delivered through a CDN
We connect distributed delivery for images, stylesheets, scripts and public files. Caching and content updates are configured around your website architecture and visitor locations.
- Static file delivery
- Controlled caching
- TLS and loading checks
Different content, different routes
Files closer to your visitors. Private data under control.
A CDN stores copies of suitable public files. Shopping carts and account pages need a separate path without shared caching.
VisitorRequests a file
CDN cachePublic copy
Origin serverStores the original
Image: a cached public copy can be served by the CDN. If no copy is available, the file is fetched from the origin.
A conceptual route. Actual results depend on file cacheability, network conditions and visitor locations.
Cache with clear rules
Public images, stylesheets, scripts and files, with suitable retention periods and checked response headers.
Keep private content separate
We exclude carts, authentication and personalised responses from shared caching, and check cookies and connected APIs.
Keep updates consistent
Make sure your new website version reaches visitors
Speed is only half the task. We define how to update files and retire old copies so that the website’s design stays consistent.
Plan your CDN setupPublishing workflow
Classify the content
Each file type has its own rules. Personalised responses stay outside shared caching.
Prepare the new version
We agree file versioning or selective cache purging to match your website’s release process.
Check the result
After publishing, we check file freshness, page loading and critical user journeys.
Pricing and setup
Start with your website’s files and traffic
Send your domain, approximate traffic volume and main visitor regions. We will identify which assets suit CDN delivery and prepare a setup and support proposal.
The scope of work
What we configure when connecting a CDN
Domain and secure connections
We agree DNS changes, verify TLS certificates and check file retrieval from the origin server.
Caching rules
We configure cache lifetimes and query parameter handling, and review headers that affect caching.
Private data exclusions
We separate public static assets from authenticated requests, carts, APIs and personalised responses.
Updates and invalidation
We agree the available invalidation process and file versioning approach to keep releases manageable.
Post-connection checks
We check file loading, errors and cache usage using the available data, then compare performance with the baseline.
CDN and static asset caching configuration
CDN setup should be considered alongside page composition and visitor geography. Large images and frequently requested public files can create significant load even when server-side code is fast. General iT analyses these assets, configures CDN delivery and compares loading times before and after connection.
Caching needs clear boundaries: public files can use shared caches, while private data and user-specific responses must follow application rules. We check exclusions, TLS, asset loading and the file update process. Where needed, CDN setup can be coordinated with website support, server optimisation and DDoS protection for web traffic.
Before we begin
Your questions answered
Which files are suitable for CDN delivery?
Public images, stylesheets, scripts, fonts and downloads that do not vary by user are the primary candidates. We define the exact asset list after reviewing the website and its access rules.
Will carts and account pages be cached?
Our default configuration excludes authentication, carts, account pages, APIs and responses with personal data from shared caching. Extending caching beyond public assets requires a separate review of application behaviour.
How do file updates work after connecting a CDN?
We agree cache lifetimes, versioned file URLs and the available invalidation procedure for updates. We test the process on your website so that releases do not depend solely on waiting for cached copies to expire.
Will a CDN speed up the entire website?
A CDN can speed up cached file delivery and reduce the load of serving those files repeatedly. Database operations, server-side code and third-party integrations need a separate assessment, so we measure the effect on your project.
What determines the cost of CDN setup?
Pricing depends on traffic volume, the number of resources, caching rules and support requirements. After reviewing your domain and traffic, we propose a suitable configuration and service terms.
The next step
See where a CDN can help your website
Share your domain, main audience regions and file delivery goals. General iT will prepare a connection plan and an estimate.