Speed up a site that uses the Stax theme
Start with the two performance options in the theme, then work on images, caching and hosting, which usually weigh more than the theme itself.
Turn on the theme performance options
Section titled “Turn on the theme performance options”- Go to Appearance > Customize > Performance.
- Switch on CSS Preload, which lets the browser prioritize the theme CSS files.
- Switch on Lazy Load Images, which loads images only when they scroll into view.
- Click Publish.
If content jumps while images load on slow connections, turn Lazy Load Images off again. Details are in Performance.
Serve images at the right size
Section titled “Serve images at the right size”- Upload images no larger than you need. The largest size the theme uses for featured images is 1100 by 620 pixels, see Image sizes.
- Compress images before uploading, or use an image optimization plugin that converts them to WebP.
- After switching to Stax on an existing site, regenerate the thumbnails so lists use the small sizes instead of full images.
Add page caching
Section titled “Add page caching”A caching plugin stores the finished HTML of each page, so WordPress does not rebuild it on every visit. Use one caching plugin only, or the caching your host provides, and enable:
- page cache
- browser cache headers and gzip or Brotli compression
- CSS and JavaScript minification, tested page by page, because aggressive settings can break a layout
Clear the cache after you change Customizer settings, or you will keep seeing the old design.
Check hosting and plugins
Section titled “Check hosting and plugins”- Use a supported PHP version (the theme needs PHP 7.4 or newer; newer versions are faster). Tools > Site Health shows yours.
- Deactivate plugins you do not use. Each active plugin can add scripts and database queries to every page.
- If the first response from the server is slow even with caching on, the hosting plan is the limit, not the theme.
Measure the result
Section titled “Measure the result”Test a page with PageSpeed Insights before and after each change, so you know which step helped. Test while logged out, since logged-in users usually bypass the page cache.