FAQ
Frequently Asked Questions
Practical answers about fast.site, setup, caching, performance and website protection.
Performance and SEO
fast.site can serve reusable public responses from its edge cache, reducing repeated work at your origin. Private pages and dynamic requests need appropriate rules; not every request can be cached.
There is no fixed improvement for every website. Compare the same pages before and after activation, including cold and warm cache, and keep the device, network and location consistent. Your origin, frontend and cache configuration all affect the result.
Read more: How to measure website speed properly
Website performance can contribute to page experience, but a CDN, a PageSpeed score or passing Core Web Vitals does not guarantee a higher Google ranking. Useful content, relevance, crawlability and many other signals also matter.
Read more: Core Web Vitals explained: LCP, INP and CLS
Eligible images can be delivered in WebP when optimization is enabled and the browser supports it. File size and visual quality depend on the source and settings. Compare actual transferred bytes and inspect the result rather than assuming a fixed saving or identical quality.
Read more: Optimize images for the web: WebP, AVIF and sizing
Setup and security
You normally connect the domain through nameservers while keeping your hosting and application. Review DNS records, HTTPS, origin access and cache exclusions. Custom sessions, plugins or cache invalidation may need additional configuration.
Read more: Changing nameservers without downtime: a checklist
We provide guides for WordPress, WooCommerce, Magento, Shopware, Drupal, Joomla, TYPO3, PrestaShop, Laravel and custom applications. Compatibility depends on DNS control, origin access and cache behavior. Shopify and other hosted platforms need a setup review.
Read more: Platforms
Setup depends on DNS propagation, certificate readiness and your origin. Verify the domain and test public and private pages before relying on the service. Signing up is not the same as technical activation.
Read more: Step-by-step setup
Edge filtering can help mitigate malicious traffic and DDoS attacks. It does not replace application updates, secure credentials or origin security, and it cannot guarantee uninterrupted availability. Check the scope and limits of your plan.
Read more: DDoS protection for websites: what actually helps
Give your website 7 days. Let the results decide.
Start with your own domain, your own traffic and a clear understanding of what comes next.