by brainrune 1 (0 reviews)

Uruz Cache Warmer

Name: Uruz Cache Warmer
Author: brainrune

Keeps your cache warm by visiting the URLs in your sitemap, in both the desktop and the mobile cache bucket.

Uruz Cache Warmer ranks #67,116 among WordPress.org plugins with 1+ active installations, is #1,015 of 1,634 in the Performance category, a 1/5 rating from 0 reviews, and was last updated Oct 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.2.4 Current Version v1.2.4

Updated 1 week ago Last Update on 12 Oct, 2026

Refreshed 6 hours ago Last Refreshed on

#1,015 of 1,634 in Performance Downloads -38.7% this week Actively maintained

View on WordPress.org

Rank

#67,116

— No change

Active Installs

— No change

KW Avg Position

— No change

Downloads

109

+2 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

54,179

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #67,116

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.2.4
Last Updated: Oct 12, 2026
Requires WP: 6.4+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: brainrune

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

cache cache warming litespeed performance sitemap

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,762

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Wordfence Security - Firewall, Malware Scan, and Login Security

Speed Optimizer - The All-In-One Performance-Boosting Plugin

1M+ installs

#44

WP Fastest Cache - WordPress Cache Plugin

1M+ installs

#47

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Performance plugins

Frequently Asked Questions

Common questions about Uruz Cache Warmer

No. A small batch per run, a delay between requests, a 45-second ceiling per run, and adaptive pacing that backs off when the site slows down or the machine is under load. All of these are settings.

WP-Cron only fires when somebody visits, which a quiet site rarely has at night. Add a real cron entry at your host calling wp brl-scw run, or hitting wp-cron.php.

Yes, if your cache serves separate mobile copies, which LiteSpeed and most CDNs do. It doubles the requests per cycle, and the first cycle after you enable it is slow, because every mobile page is built from scratch. The admin page hangs when I press "Run one batch now" Your site is serving one PHP request at a time. The warm requests queue up behind the admin request that started them, and neither can finish. It shows up on dev servers and on a php-fpm pool sized to a single worker. Let the background worker do the warming instead, or raise the number of PHP workers. On normal hosting this does not happen.

Only a real MISS. Bypass and no-cache are decisions your stack made on purpose, and unknown means no cache header could be read, so neither counts as cold.

It runs one batch and nothing else, and only when the request carries the random key generated on your site. A wrong key gets a 403, and you can replace the key from Settings at any time. A cron entry cannot send a login or a nonce, so the key is the credential.

Yes, and the plugin reads cf-cache-status. If you also run LiteSpeed, keep one purge strategy rather than two.