Build with fast.site
Tools, APIs and docs to wire fast.site into your stack.
Sub-200ms TTFB
Time to First Byte drops from 800ms or more to under 200ms. Edge caching removes the origin round-trip on warm requests.
LCP under 2 seconds
Largest Contentful Paint improves by up to 60% with cached assets and automatic WebP conversion.
FCP under 1 second
First Contentful Paint drops below 1 second once HTML is served from the edge.
See how Fast improves your PageSpeed score
Visualize how Fast Edge Cache™ boosts your Google PageSpeed Insights score and Core Web Vitals in real-time.
Before
Typical WordPress site
After
With Fast Edge Cache™
Performance by Platform
Average improvements across our customer base. See how your platform stacks up.
Based on average customer data from production sites. Individual results may vary depending on origin server configuration, content type, and visitor location.
Time to First Byte (TTFB)
Server Response Time
What it measures
TTFB measures the time from when a visitor requests your page to when the first byte of data arrives at their browser. It reflects your server's processing speed and network latency.
Why it matters
Google uses TTFB as a ranking signal. A slow TTFB (over 600ms) triggers the 'Reduce initial server response time' warning in PageSpeed Insights and can drop your performance score by 10-20 points.
How fast.site helps
- Edge caching serves responses from 6 global locations
- 98% cache hit rate eliminates origin server round-trips
- HTTP/2 and HTTP/3 reduce connection overhead
- Smart cache warming keeps popular content ready
Typical WordPress server response
Edge-cached response
Largest Contentful Paint (LCP)
Visual Loading Speed
What it measures
LCP measures when the largest visible element (usually a hero image or heading) finishes rendering. It's the primary indicator of perceived loading speed.
Why it matters
LCP is the #1 reason for poor PageSpeed scores. Google requires LCP under 2.5s for a 'Good' rating. Every 100ms delay reduces conversions by up to 7%.
How fast.site helps
- Automatic WebP conversion reduces image size by 25-50% typically, up to 80%
- Hero images served from nearest edge location
- Lazy loading for below-fold images
- Responsive image delivery based on device
Heavy images from origin
WebP from edge
First Contentful Paint (FCP)
Initial Render Speed
What it measures
FCP measures when the browser renders the first visible content (text, images, or canvas elements) on the page. It tells users 'something is happening.'
Why it matters
FCP directly impacts bounce rate. Users expect content within 1 second. Sites with FCP over 3s see bounce rates increase by 90% compared to sub-1-second sites.
How fast.site helps
- HTML cached and served from edge
- Gzip compression cuts HTML payload size significantly
- Critical CSS delivered inline
- Render-blocking resources minimized
Round-trip to origin server
HTML from nearest edge
Built to disappear into your workflow
No infrastructure to babysit. Add the domain, confirm the platform, delegate nameservers.
Zero config
Works out of the box. Add your domain, confirm the auto-detected platform, delegate nameservers, and the site is served from the edge.
Full API access
REST API for cache purging, analytics, and zone management. Automate from your CI, your monitoring, or anything else that speaks HTTP.
Real-time analytics
Bandwidth, requests, cache hit rate, and response times. Live, per domain, per region.
*Values reflect typical results from our own testing and may vary based on origin, geography, and site implementation.
