Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼5.49ms] Passed 4 tests
A check of server-side resources used by Xposure Listings
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.76 ▲0.03 | 43.72 ▼8.35 |
| Dashboard /wp-admin | 3.59 ▲0.02 | 51.58 ▼5.71 |
| Posts /wp-admin/edit.php | 3.70 ▲0.02 | 53.91 ▼1.25 |
| Add New Post /wp-admin/post-new.php | 6.17 ▲0.02 | 91.52 ▼6.65 |
| Media Library /wp-admin/upload.php | 3.51 ▲0.02 | 45.76 ▲4.62 |
Server storage [IO: ▲1.57MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
These are issues you should consider
- You have illegally modified 1 file (0.00KB) outside of "wp-content/plugins/xposure-listings/" and "wp-content/uploads/"
- (new file) "wp-content/plugins/xposure-listings/assets/icon-256\303\227256.png"
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Xposure Listings
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.38 ▼0.20 | 1.86 ▲0.18 | 42.33 ▲0.88 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.56 ▼0.07 | 85.48 ▼14.11 | 39.70 ▼2.93 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 2.00 ▼0.05 | 39.03 ▲2.84 | 36.18 ▲2.06 |
| Add New Post /wp-admin/post-new.php | 6,368 ▲4,823 | 27.77 ▲4.63 | 921.52 ▲297.33 | 40.90 ▼21.77 |
| Media Library /wp-admin/upload.php | 1,403 ▲12 | 4.19 ▼0.13 | 96.81 ▼13.23 | 46.37 ▼1.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/xposure-listings/xposure-plugin.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
3 plugin tags: embed, real estate, listings
xposure-listings/xposure-plugin.php 92% from 13 tests
The main file in "Xposure Listings" v. 1.1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("xposure-listings.php" instead of "xposure-plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected544 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 31 | 13 | 330 |
| PHP | 1 | 49 | 16 | 98 |
| CSS | 2 | 6 | 1 | 84 |
| PO File | 1 | 1 | 1 | 20 |
| XML | 1 | 0 | 0 | 11 |
| JSON | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.19 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 6 | |
| ▷ Named functions | 5 | 83.33% |
| ▷ Anonymous functions | 1 | 16.67% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 1.57MB with 0.99MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 1,585.63KB | 503.61KB | ▼ 68.24% |
| assets/icon-256×256.png | 19.13KB | 8.06KB | ▼ 57.88% |