Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼11.15ms] Passed 4 tests
Analyzing server-side resources used by Custom Menu Driven Prev/Next Links
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 37.04 ▼2.35 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 46.09 ▼23.07 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.07 ▼2.60 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.40 ▼16.57 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 35.64 ▲3.27 |
Server storage [IO: ▲0.26MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Custom Menu Driven Prev/Next Links
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲43 | 14.58 ▲0.15 | 1.61 ▲0.09 | 38.00 ▼0.43 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.60 ▼0.04 | 86.25 ▼7.02 | 38.30 ▼3.69 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.03 ▼0.00 | 37.25 ▲0.54 | 37.87 ▼0.29 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼9 | 23.35 ▲5.19 | 629.54 ▲0.94 | 54.07 ▼13.17 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.19 ▲0.01 | 96.94 ▼3.92 | 44.30 ▲2.71 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
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: Screenshot #1 (This plugin introduces prev/next links which complements the custom menu, and makes it easier for your readers to go to the previous/next without the need to scroll back up to the menu again.) image missing
custom-menu-driven-prevnext-links/Custom-Menu-Driven-Prev-Next-links.php 92% from 13 tests
The primary PHP file in "Custom Menu Driven Prev/Next Links" version 0.2 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("custom-menu-driven-prevnext-links.php" instead of "Custom-Menu-Driven-Prev-Next-links.php")
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
Good job! No executable or dangerous file extensions detected81 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 11 | 8 | 81 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| 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 | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.25MB with 0.19MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-1.png | 259.06KB | 64.69KB | ▼ 75.03% |