by 漫步白月光 0 (0 reviews)

AT8 Site Accelerator

Name: AT8 Site Accelerator
Author: 漫步白月光

Lightweight full-page cache with surgical invalidation, smart preloading, HTML minification, WebP conversion and database cleanup.

AT8 Site Accelerator ranks #59,345 among WordPress.org plugins with 0+ active installations, is #1,311 of 1,658 in the Performance category, and was last updated Oct 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v3.0.7.1 Current Version v3.0.7.1

Updated 2 weeks ago Last Update on 12 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#1,311 of 1,658 in Performance Actively maintained

View on WordPress.org

Rank

#59,345

— No change

Active Installs

— No change

KW Avg Position

158

— No change

Downloads

179

+4 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

31,777

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 7 more installs to reach 10+

Rank Changes

Current #59,345

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

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 3.0.7.1
Last Updated: Oct 12, 2026
Requires WP: 5.8+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: 漫步白月光

Support & Rating

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

Keywords

cache lazy load page cache redis webp

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,757

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 AT8 Site Accelerator

Check the first item on the "Diagnostics" tab. The three most common causes are: the wp-content directory is not writable, WP_CACHE is not enabled in wp-config.php, or another caching plugin on the same server is already occupying the advanced-cache.php drop-in slot.

That is by design - see "Why surgical invalidation" above. If you really want a full purge, switch the strategy to "purge everything" on the "Invalidation" tab.

No. Every key carries a per-site salt prefix - the plugin's own namespace plus the site's blog ID, its home URL and the cache version - so invalidation only deletes keys under this site's prefix, and FLUSHDB does not appear anywhere in the codebase.

Because a cache entry is not tied to a specific person. Caching a page for a signed-in visitor would mean one visitor could be served a page that was generated for another. Since 3.0.5 signed-in visitors always bypass the cache. The old "also cache logged-in users" switch is gone from the settings screen, and any value an older version saved for it is ignored rather than acted upon.

No. The Free version never sends Cache-Control: public (or a long Expires) for an HTML page - not on cache misses, not on cache hits, and regardless of any value an older version saved for the former "browser cache for HTML" switch, which has been removed. Static assets (CSS, JS, images, fonts) can still get long-lived cache rules, because they contain no visitor-specific content.

Yes. Each site gets its own cache directory and its own Redis key prefix.