by
Service2Client LLC
0 (0 reviews)
Memory Scan – PHP Memory Usage – No Crash
Warns before a low-memory crash, flags end-of-life PHP, and checks whether your plugins are ready for a PHP upgrade — all read-only.
Memory Scan ranks #62,899 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Aug 1, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7.0.8 (Current: 7.1.4)
v1.2.0
Current Version v1.2.0
Updated 3 months ago
Last Update on 01 Aug, 2026
Refreshed 1 week ago
Last Refreshed on
#3,855 of 5,058 in Security
Rank
#62,899
—
No change
Active Installs
0+
-100%
KW Avg Position
184
2 worse
Downloads
369
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
35,331
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
Need 8 more installs to reach 10+
Rank Changes
Current
#62,899
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.2.0
- Last Updated
- Aug 01, 2026
- Requires WP
- 5.0+
- Tested Up To
- 7.0.8
- PHP Version
- 7.0 or higher
- Author
- Service2Client LLC
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar 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
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about Memory Scan – PHP Memory Usage – No Crash
No. It records the memory peak at the end of each request (a couple of arithmetic operations), and only performs the heavier per-plugin scan on admin requests, cached hourly. Nothing extra runs on front-end page loads beyond recording a single number.
No, and it says so on screen. PHP cannot attribute runtime memory to an individual plugin from a single request, so the per-plugin figure is a conservative estimate based on each plugin's code size. It errs high on purpose, so you provision enough memory rather than too little. The overall verdict uses your real measured peak.
No. It reads WordPress.org's published data about each plugin — the declared PHP requirement, the WordPress "tested up to" version, and the last-updated date, the same information shown on each plugin's page. It never executes your plugin code, so it is safe, but a green result is a strong signal rather than a guarantee. The only certain test is running the upgrade on staging.
It looks plugins up on WordPress.org — the same service WordPress already uses to check for plugin updates. Those lookups happen only when you click the "Check compatibility" button on the Memory Scan page, are limited to a handful at a time, time out quickly, and are cached for a week. Nothing runs on your visitors' pages, and if WordPress.org is slow or unreachable the plugin simply shows "could not verify" rather than waiting.
Premium plugins and custom-built plugins are not hosted in the WordPress.org directory, so there is no published data to read. Those are shown as "could not verify" — check the developer's own PHP-compatibility information for them.
The plugin shows the exact line to add to wp-config.php. That setting lives outside any plugin, so Memory Scan can only detect and advise, not change it for you.
No. Memory Scan is read-only with respect to your content — it never touches posts, pages, or other plugins' settings, and it never changes your PHP version. It only detects and advises.
