A CMS for Fast Websites
Building a good website is hard enough and you shouldn't have to spend as much time designing as making sure your website loads quickly. gpEasy's flat-file data storage system is the first step towards fast websites. Without the need to fetch content from a database server, there's no risk of encountering a database bottleneck, and the page content can be processed and delivered to the client quickly.
Efficiently storing and transmitting your data is just the beginning. gpEasy implements a number of additional optimisations to get your content to your visitors faster. These optimisations allow you to build and expand your website with the assurance that it will continue to operate with the speed you expect.
| Optimization Technique | Pages | CSS Files | JavaScript Files |
|---|---|---|---|
| Gzip Compress to Reduce Payload Size |
 |
|
|
| Combine Files to Reduce HTTP Round-Trips |
|
|
|
| Add Etags for Client Caching |
|
|
|
| Extend the Client Cache |
|
|
|
| Minimize to Reduce Payload Size |
|
Gzip Compressing to Reduce Payload Size
All modern browsers support gzip compression, and when used it significantly reduces the number of bytes downloaded. The benefits are most noticeable with text content including HTML, CSS, and JavaScript. When gpEasy detects a browser that does not support gzip compression it sends the uncompressed content instead, ensuring your website downloads correctly for all visitors.
Combining Files to Reduce HTTP Round-Trips
When a visitor requests a page that has multiple CSS or JavaScript resources, gpEasy can combine these files into a single file to reduce the number of HTTP round-trips. Reducing the number of round-trips minimizes total round-trip time and addresses a number potential bottlenecks in page loading. Our CMS enables this feature by default. For CSS resources, files specified using @import are also resolved.
You can read more about the benefits of minimizing round-trip times on Google's page speed documentation.
Adding ETags for Client Caching
All of the combined and optimized files are given an Etag that identifies the content uniquely. If the content has not changed after a visitor makes multiple requests, the server will send a 304 Not Modified response instead of resending all of the content again. This significantly reduces the amount of data visitors must download with each page request.
Extending the Client Cache
The combined and optimized files are also appended with a unique identifier in the URL then served with an extended max-age value in the Cache-Control header. gpEasy monitors the combined files for changes and will prompt the browser to load new content by using a new unique identifier. Monitoring and improving the cacheability of your site content will reduce the number of requests to your server while also ensuring the newest content is being delivered to the client.
Minimizing to Reduce Payload Size
Minifying is used to remove unnecessary strings and characters in order to reduce the overall size of your CSS files. Removal of comments and white-spaces will not affect the functionality of the code and will improve page load times by reducing the amount of data sent to the browser.
Find out more about the benefits of using gpEasy by reviewing the feature highlights of Our CMS.
