u/cl0wnfire

Hi everyone,

I just released a new update for WP Optimizer.

The latest version focuses on safer performance tuning and better diagnostics, especially when testing cache and optimization settings on real WordPress sites.

What’s new:

• Added a new Page Test tool to compare the current WP Optimizer configuration against baseline, to help tuning the plugin options.
• Added automatic configuration backups on plugin settings changes.
• Added recovery mode for WP Optimizer if any related fatal errors occurs.
• Improved cache configuration and diagnostics.
• Fixed several bugs and UI/UX issues.

The goal of this update is to make aggressive cache/minify/PageSpeed tuning safer: you can test changes, keep automatic backups, and recover more easily if a bad configuration causes issues.

Plugin page: https://wordpress.org/plugins/wp-optimizer/

The goal is to bring meaningful performance and maintenance improvements to WordPress sites in a single plugin, without needing to install several separate plugins and risk reducing the overall benefits.

Feedback and suggestions are very welcome.

I recently pushed a huge update focused on usability, diagnostics and background performance, see it here https://wordpress.org/plugins/wp-optimizer/.

WP Optimizer is a free modular WordPress optimization plugin. The idea is to keep performance, maintenance and technical tools in one place, while allowing each module to load only when and if you need it.

The latest updates focus mainly on:

New UI / UX
I redesigned the admin interface to make the plugin easier to navigate and less cluttered. The goal was to make modules, settings and diagnostics clearer, especially for users who do not want to dig through many separate plugin pages.

I also added a PageSpeed module to improve page loading speed, and a Cron module to manage scheduled tasks and cron-related module operations. This is meant to help reduce unnecessary background work and make WordPress cron behavior easier to inspect and control.

Background improvements
A lot of the recent work was also internal: better module initialization, lazy dependency loading, reduced unnecessary work during requests, and general performance improvements in the plugin core.

WP Optimizer also includes modules for:

• Cache
• Minify
• Media optimization and WebP conversion
• Database cleanup and optimization
• Performance monitoring
• Activity logging
• Server / WordPress diagnostics
• Security hardening
• Update controls
• Mail logging / SMTP
• Admin cleanup and WordPress feature toggles
• Settings import / export / restore

The direction I’m trying to take is not just “another cache plugin”, but a modular optimization and maintenance panel where site owners can enable only the parts they actually need.

I’d appreciate honest feedback from people who work with WordPress performance regularly:

• What would you expect from a PageSpeed module?
• Would a Cron Manager be useful in your workflow?
• Do you prefer optimization plugins to expose more technical controls, or keep everything simplified with safer defaults?
• What would make you trust or try a free optimization plugin on a production site?

Any feedback on the positioning, feature set or UI direction would be very useful.

What feature you like most? What am I missing? Tips for the UI/UX?

A recently published REQL on GitHub, after working on it for some time, a local repository context engine designed for coding agents and developer tools.

To clarify its positioning: REQL is not another graph database, graph framework, or graph visualization tool. It uses a graph internally to represent relationships between files, symbols, imports, calls, tests, documentation, and other repository elements, but the graph itself is not the product.

The project is intended to be embedded into existing workflows as a structured, end-to-end pipeline for repository indexing, incremental updates, querying, and context generation. The goal is to let tools and agents retrieve a compact, connected, and source-grounded view of a codebase instead of scanning the entire repository or relying only on whatever fits into a prompt.

REQL currently includes:

• Tree-sitter-based analysis for more than 30 languages;
• deeper extraction for Python, JavaScript, and TypeScript;
• incremental compilation, caching, deletion handling, and watch mode;
• a dedicated query language;
• local storage without requiring an external graph database;
• a CLI, Python API, and optional MCP server.

There are no mandatory LLM calls in the core indexing and retrieval pipeline.

The project is still in alpha and there are certainly areas that need improvement, but I decided to publish it because I hope it can already be useful to people working on coding agents, repository analysis tools, or structured context pipelines.

GitHub: https://github.com/sh1zen/reql

I would really appreciate feedback from anyone willing to test it on a real repository, especially regarding retrieval quality, unsupported project structures, integration issues, or anything that feels unnecessarily complicated.

I also hope some of you may find it useful enough to participate in its development. Issues, pull requests, and contributions are very welcome.

I recently pushed a huge update focused on usability, diagnostics and background performance, see it here https://wordpress.org/plugins/wp-optimizer/.

WP Optimizer is a free modular WordPress optimization plugin. The idea is to keep performance, maintenance and technical tools in one place, while allowing each module to load only when and if you need it.

The latest updates focus mainly on:

New UI / UX
I redesigned the admin interface to make the plugin easier to navigate and less cluttered. The goal was to make modules, settings and diagnostics clearer, especially for users who do not want to dig through many separate plugin pages.

I also added a PageSpeed module to improve page loading speed, and a Cron module to manage scheduled tasks and cron-related module operations. This is meant to help reduce unnecessary background work and make WordPress cron behavior easier to inspect and control.

Background improvements
A lot of the recent work was also internal: better module initialization, lazy dependency loading, reduced unnecessary work during requests, and general performance improvements in the plugin core.

WP Optimizer also includes modules for:

• Cache
• Minify
• Media optimization and WebP conversion
• Database cleanup and optimization
• Performance monitoring
• Activity logging
• Server / WordPress diagnostics
• Security hardening
• Update controls
• Mail logging / SMTP
• Admin cleanup and WordPress feature toggles
• Settings import / export / restore

The direction I’m trying to take is not just “another cache plugin”, but a modular optimization and maintenance panel where site owners can enable only the parts they actually need.

I’d appreciate honest feedback from people who work with WordPress performance regularly:

• What would you expect from a PageSpeed module?
• Would a Cron Manager be useful in your workflow?
• Do you prefer optimization plugins to expose more technical controls, or keep everything simplified with safer defaults?
• What would make you trust or try a free optimization plugin on a production site?

Any feedback on the positioning, feature set or UI direction would be very useful.