Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Please fix the following installer errors
- The plugin cannot be installed
- > Warning in wp-includes/class-wp-hook.php+310
call_user_func_array() expects parameter 1 to be a valid callback, function 'fmtcpod_activate' not found or invalid function name
Server metrics [RAM: ▼0.91MB] [CPU: ▼36.99ms] Passed 4 tests
A check of server-side resources used by FMTC Pods
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 37.86 ▼3.08 |
| Dashboard /wp-admin | 3.05 ▼0.30 | 22.19 ▼42.66 |
| Posts /wp-admin/edit.php | 3.05 ▼0.31 | 23.40 ▼24.27 |
| Add New Post /wp-admin/post-new.php | 3.05 ▼2.84 | 23.75 ▼72.63 |
| Media Library /wp-admin/upload.php | 3.05 ▼0.19 | 23.56 ▼8.41 |
| FMTC Pods /wp-admin/options-general.php?page=fmtcpods | 3.05 | 27.02 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for FMTC Pods
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.18 ▼1.50 | 1.71 ▼0.30 | 43.29 ▼12.87 |
| Dashboard /wp-admin | 2,210 ▲22 | 5.85 ▲0.98 | 105.20 ▼11.54 | 41.28 ▼1.66 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.01 ▼0.03 | 39.19 ▲2.92 | 38.22 ▲2.54 |
| Add New Post /wp-admin/post-new.php | 6,448 ▲4,912 | 25.03 ▲1.93 | 886.16 ▲233.99 | 53.12 ▼6.63 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.19 ▲0.01 | 106.28 ▲8.32 | 50.15 ▲7.57 |
| FMTC Pods /wp-admin/options-general.php?page=fmtcpods | 805 | 2.03 | 27.32 | 33.41 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These errors were triggered by the plugin
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=fmtcpods
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- > GET request to /wp-admin/options-general.php?page=fmtcpods
- > Notice in wp-content/plugins/fmtc-pods/fmtcpods.php+205
Trying to access array offset on value of type null
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 fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function FMTC\\PODS\\get_file_data() in wp-content/plugins/fmtc-pods/fmtcpods.php:31
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
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 important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== fmtc-pods ===)
fmtc-pods/fmtcpods.php 92% from 13 tests
Analyzing the main PHP file in "FMTC Pods" version 1.5.2
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("fmtc-pods.php" instead of "fmtcpods.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin191 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 36 | 43 | 154 |
| JavaScript | 2 | 7 | 1 | 37 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| 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 | 1 | |
| 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 | 8 | |
| ▷ Named functions | 7 | 87.50% |
| ▷ Anonymous functions | 1 | 12.50% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin