Performance terms
Every millisecond matters — here is how to win them back
Slow software costs money, loses users, and erodes trust. Performance engineering covers profiling, caching strategies, database query optimisation, network latency, memory management, and the architectural patterns that keep systems fast under real-world load. Most performance problems are invisible until they are not — these terms help you find and fix them before your users do.
Redis PHP 7.0+
An in-memory key-value data store used in PHP applications for caching, session storage, queues, rate limiting, and pub/sub — providing sub-millisecond data access compared to database queries.
2mo ago
performance beginner
Asset Versioning & Browser Cache Strategy Serving static assets with immutable long-lived cache headers plus content-hash filenames — maximising cache hits while guaranteeing instant cache-busting on change.
2mo ago
performance beginner
CDN (Content Delivery Network) A geographically distributed network of servers that caches and delivers static assets from locations close to end users.
2mo ago
performance beginner
Gzip / Brotli Compression
Compressing HTTP responses server-side reduces transfer size significantly, especially for text-based assets.
2mo ago
performance beginner
Pagination Strategies PHP 5.0+
Techniques for splitting large result sets across pages to avoid loading unbounded data in a single query.
2mo ago
performance beginner
Slow Query Log PHP 5.0+
A database log of queries exceeding a time threshold — the first place to look when diagnosing PHP application performance problems.
2mo ago
performance beginner
Lazy Loading HTML5
Defer loading or initialising a resource until it is actually needed, reducing startup cost and memory usage.
2mo ago
performance beginner