Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsTo make a Grav website faster, first check PHP OPcache and an available user cache such as APCu, then measure whether the bottleneck is caching, storage, shared server resources, or the site’s workload. Grav stores content in plain-text files and does not require a database, but that does not make every deployment fast by default. Its performance depends on PHP, cache availability, storage, hosting resources, site size, and how often content changes.
Why a flat-file CMS still needs performance tuning
Grav’s flat-file design means it stores content in files rather than requiring a database. That simplifies the storage model, but a live site still needs suitable PHP and web-server configuration, writable locations for cache and logs, and reliable backups. PHP execution, file access, cache behavior, and available server resources all affect response time. See Grav’s overview of its basic architecture and its requirements documentation.
There is no single setting that guarantees faster page loads. A change that helps a large site with infrequent edits may be a poor fit for a small site that changes constantly. Start with the actual deployment and workload, and validate changes there.
Check the PHP and hosting foundations
Grav’s performance guidance highlights PHP OPcache and a PHP user cache such as APCu. OPcache can avoid repeatedly compiling PHP scripts; a user cache can support cached data. These are recommendations, not guaranteed speedups: availability and results depend on the PHP setup, host, and site workload. Grav also documents integrations such as Memcache, Redis, and WinCache alongside file-based and automatic cache options. Consult the Grav performance and caching guide for options and tradeoffs.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Brand New in box. The product ships with all relevant accessories
Storage and resource allocation matter too. Grav’s guidance favors SSD storage and cautions against network file systems such as NFS; processor and memory capacity, as well as contention for shared resources, also affect performance. Check what your host actually provides before changing application settings or upgrading a plan.
Choose hosting for the bottleneck
Grav says it can run well on shared hosting and describes dedicated hosting as the route to ultimate speed. That is general project guidance, not a provider comparison or a promise about a particular service. Shared resources may be sufficient for a modest site; dedicated resources may help when measurements point to resource contention. Consider cache support, storage and filesystem arrangement, CPU and memory behavior, site size, and content-change frequency together rather than assuming a hosting upgrade is necessary.
Configure caching with the edit-versus-speed tradeoff in mind
Grav has multiple cache layers, and the cache driver and change-check method influence both performance and how quickly edits appear. Its system configuration exposes cache enablement, cache driver, and cache check method. Available options can vary by Grav version, so use the settings documentation and configuration for the installed release rather than copying a path or value from another version. The system configuration documentation describes these controls.
In some production circumstances, checking for changes less often—or disabling a check—can reduce work. The tradeoff is that edits may not appear until you clear the cache manually. Before using a less frequent check, test how page changes are detected on your actual deployment and establish a reliable cache-clearing procedure. Do not apply a production cache setting without confirming its effect on both response time and content freshness.
What Grav’s 2.2 performance report measured
Grav’s article published September 24, 2026 compares Grav 2.2.0 with 2.1.10. It reports results on the project’s own 1,081-page site and a 10,321-page copy. Grav defines a cold start as the first request after clearing the cache and a warm start as later requests after the cache has been built. These are project-reported benchmarks, not independent measurements or a prediction for another site. The report is at Grav 2.2 release and benchmark report.
| Reported measure | Grav 2.1.10 | Grav 2.2.0 | Context |
|---|---|---|---|
| Cold-start time, smaller site | 1,047 ms | 526 ms | Grav’s 1,081-page site; first request after cache clearing. |
| Cold-start time, larger site | 4,633 ms | 2,326 ms | Grav’s 10,321-page copy; first request after cache clearing. |
| Memory per page view, larger site | 241.8 MB | 9.6 MB | Reported for the 10,321-page copy. |
| First page view after saving a page in Admin | 1,075 ms | 67.9 ms | Grav’s reported measurement following an Admin page save. |
The report’s figures describe those versions and workloads; they do not establish how a different site will perform, nor should cold-start results be read as warm-request timings. Grav’s release notes also describe changes to page-cache rebuilding, page indexing, and CSS minification, which help explain why version changes can affect performance. The official downloads page lists v2.2.4 as the latest stable release in its indexed result and recommends it for new sites and upgrades; release listings can change, so check the live page when choosing a version.
Quick Recap
A practical order for investigating a slow Grav site
- Establish a baseline. Measure response times on the deployment you want to improve, noting whether the request follows a cache clear or comes from an already-built cache. Record site size and how frequently content changes.
- Check the PHP setup. Confirm with your host or server configuration whether OPcache and APCu or another suitable user cache are available and enabled. Do not assume a module is active merely because the hosting plan advertises it.
- Inspect cache behavior. Review the installed Grav release’s cache driver and change-check settings. Test that edits show up as expected before and after any cache clear, especially if adjusting checks for production.
- Look at storage and resources. Verify the storage type and filesystem arrangement, and investigate CPU, memory, and shared-resource contention. Compare these observations with Grav’s performance guidance before changing hosts.
- Change one thing at a time and measure again. Recheck the same workload after each change, distinguishing first requests after a cache clear from later cached requests. Keep a way to revert settings if the site’s freshness or stability worsens.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
