Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.08MB] [CPU: ▼6.32ms] Passed 4 tests
Analyzing server-side resources used by Purge Cloud Flare
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.08 | 41.20 ▼3.96 |
| Dashboard /wp-admin | 3.42 ▲0.08 | 48.09 ▼3.48 |
| Posts /wp-admin/edit.php | 3.54 ▲0.14 | 53.61 ▲3.64 |
| Add New Post /wp-admin/post-new.php | 6.03 ▲0.10 | 92.90 ▼21.49 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.08 | 39.90 ▲3.82 |
Server storage [IO: ▲0.28MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 14 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| cf-purger |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Purge Cloud Flare: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,003 ▲242 | 13.85 ▼0.52 | 8.16 ▲6.63 | 55.45 ▲13.48 |
| Dashboard /wp-admin | 2,265 ▲90 | 5.70 ▲0.04 | 83.48 ▼23.66 | 76.11 ▲38.49 |
| Posts /wp-admin/edit.php | 2,176 ▲73 | 2.03 ▲0.06 | 38.73 ▲2.52 | 39.49 ▲3.66 |
| Add New Post /wp-admin/post-new.php | 1,598 ▲72 | 22.86 ▼0.54 | 609.34 ▼69.69 | 156.72 ▲103.42 |
| Media Library /wp-admin/upload.php | 1,473 ▲73 | 4.16 ▼0.04 | 111.91 ▲12.01 | 85.88 ▲43.32 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/purge-cloud-flare/purge-cloud-flare.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: Please add an image for screenshot #6 (Purge individual files modal)
purge-cloud-flare/purge-cloud-flare.php 92% from 13 tests
The entry point to "Purge Cloud Flare" version 1.6 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected636 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 60 | 135 | 317 |
| CSS | 1 | 23 | 2 | 218 |
| JavaScript | 1 | 9 | 4 | 101 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.33 |
| Average class complexity | 33.00 |
| ▷ Minimum class complexity | 33.00 |
| ▷ Maximum class complexity | 33.00 |
| Average method complexity | 2.28 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 25 | |
| ▷ Static methods | 4 | 16.00% |
| ▷ Public methods | 25 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 7 | |
| ▷ Global constants | 3 | 42.86% |
| ▷ Class constants | 4 | 57.14% |
| ▷ Public constants | 4 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
8 PNG files occupy 0.25MB with 0.14MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/spinner.png | 0.41KB | 0.33KB | ▼ 20.28% |
| screenshot2.png | 21.65KB | 9.66KB | ▼ 55.40% |
| screenshot1.png | 34.33KB | 15.91KB | ▼ 53.66% |
| screenshot4.png | 44.71KB | 11.73KB | ▼ 73.77% |
| screenshot5.png | 59.80KB | 16.43KB | ▼ 72.52% |