You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
increase page-load performance by pre-compressing your static website
content saving up to 70% of bandwith consumption and 80% in Azure
Blob Storage
- use brotli in the CD pipeline to to compress the static website
content without losing data
- upload-batch separaterly per type and also compress json files
| | Downloaded Bytes | Document Complete Time | Fully Loaded Time | First Byte | Start Render |
|---------------------------|------------------|------------------------|-------------------|------------|--------------|
| wo/ compression | 680 KB | 1.708s | 1.829s | 0.221s | 0.900s |
| Blob compression (Brotli) | 202 KB | 0.797s | 0.955s | 0.208s | 0.800s |
| CDN compression (gZip) | 229 KB | 0.815s | 1.055s | 0.220s | 0.800s |
Pros
- no size limits when compressing. CDNs limits the size for compression
files pre-compressed approach avoid performance hit over the edge server
when caching new content
- more control over content compression
freely choose between CDNs without caring about compression support
- don not wait your CDN profile to implement the new compression tool you
need. CDN Akamai profile does not support Brotli (Google)
- save more space in the origin
- it offers the fastest page load speed
Cons
- more heavy lifting from the deployment pipeline: tooling + files
manipulation
- multiple uploads are required to indicate content type and encoding. It
is recommended to be implemented along with versioning using directories
solved: #115214
0 commit comments