WordPress Performance - Introduction
Naar navigatie springen
Naar zoeken springen
WordPress Performance, WordPress site tuning, WordPress site performance optimization, etc., refers to the various practices, techniques, and tools used to optimize the speed and efficiency of a WordPress website. A well-performing WordPress site not only provides a better user experience but also ranks higher in search engine results. In the articles on this wiki, this topic mostly relates to the performance of WooCommerce webshops, where both factors should translate into increased sales. Also: caching is only one aspect of 'site performance.
Some aspects
Some aspects of WordPress performance, roughly in order from measurement » server » client:
- Develop performance policy: Explicitly state goals, measurement approaches and resources. E.g.: To what price is performance improvement important?
- Procedures for continuous measurement & optimization. E.g.: Regular site & plugin updates, server updates, reviews & discussions, dashboarding
- External performance measuring: External tools like Google PageSpeed, GTmetrix and Pingdom
- Internal performance measuring: Tools like plugin Query Monitor
- External site monitoring: E.g., tools that monitor if a site is down
- Internal site monitoring: E.g., Bash scripts that track performance indicators
- DNS optimization: Fast & reliable DNS providers like CloudFlare or Amazon Route 53
- DNS Prefetching, preloading & preconnecting
- Server: Distributed functionality. E.g.: external firewall, Varnish, load balancing
- Server: Hardware & location
- Server: Stack design. E.g.: Apache vs. Nginx, RDBMS, PHP version
- Server: Apache: Directives at the most efficient location (global, site config files, .htaccess)
- Server: In-memory vs. in-storage?
- Internal caching: Transients, page caching, object caching, in-memory caching vs. database-cacing
- External caching: External caching, Varnish? CloudFlare? CDN?
- Traffic management (firewall?): Bot visits
- Database optimization: Cleanup, query optimization, adding indexes, custom functionality
- Traffic compression: Use e.g., GZip for sending files
- Site: Heartbeat API control
- Site: Asset optimization: Defer JavaScript
- Site: Asset optimization: Asynchronous JavaScript loading
- Site: Asset optimization: Asynchronous loading of third-party analytics tools
- Site: Image size optimization
- Site: Minification & concatenation
- Site: Reduce number of HTTP requests (?)
- Site: Plugins: Optimize amount & resources, document this, disable/delete plugins that are only needed incidentially
- Site: Theme: Optimize theme. E.g.: custom vs. off-the-shelf
- Site: Have a responsive theme with separate content optimizations for desktop & mobile
- Site: Mobile-specific optimization: AMP (Accelerated Mobile Pages)
- Site: Mobile-specific optimization: E.g., touch-friendly buttons, less content because of smaller screens, etc.
- Site: Optimize security infrastructure. E.g.: WAF needed? If so, what? External firewall? Captcha, etc.
- Site: Limit external services (fonts, ads, libraries?)
- Site: WooCommerce: Number of taxonomies + elements, complexity of shop page, shop page caching
- Site: WooCommerce: Number of products
- Site: Speed perception: Optimize above-the-fold content
- Site: Speed perception: Ensure quick user experience
- Site: Speed perception: Don't use "wait screens"
- Site: Speed perception: Lazy loading: Delay loading of non-essential images & iframes until they are needed
- Browser caching
Sources
Some really nice sources, if this stuff is new to you: