Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
You still need to fix the following installer errors
- The plugin cannot be installed
- > Warning in wp-content/plugins/engap/lib/class-engap-customposttype.php+113
Declaration of ENGAP_CustomPostType::get_posts($filter = Array, $context = 'view', $type = NULL, $page = 1) should be compatible with ENGAP_Posts::get_posts($filter = Array, $context = 'view', $type = 'post', $page = 1, $limit = 3)
Server metrics [RAM: ▼1.86MB] [CPU: ▼46.83ms] Passed 4 tests
A check of server-side resources used by enGap
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.06 ▼1.40 | 5.56 ▼30.63 |
| Dashboard /wp-admin | 2.16 ▼1.14 | 10.00 ▼35.81 |
| Posts /wp-admin/edit.php | 2.16 ▼1.19 | 6.48 ▼40.62 |
| Add New Post /wp-admin/post-new.php | 2.16 ▼3.72 | 5.78 ▼78.68 |
| Media Library /wp-admin/upload.php | 2.16 ▼1.06 | 5.41 ▼32.21 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| engap_plugin_version |
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by enGap
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲54 | 13.44 ▼0.84 | 1.91 ▼0.12 | 42.32 ▼2.06 |
| Dashboard /wp-admin | 2,209 ▲18 | 4.86 ▼0.03 | 103.31 ▲2.46 | 39.09 ▼1.99 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.00 ▼0.03 | 38.29 ▼3.74 | 34.56 ▼1.77 |
| Add New Post /wp-admin/post-new.php | 1,538 ▼129 | 23.24 ▲0.89 | 699.92 ▲44.56 | 54.82 ▲10.03 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.22 ▲0.01 | 94.30 ▼6.48 | 43.55 ▼2.46 |
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
- This plugin cannot be uninstalled
- > Warning in wp-content/plugins/engap/lib/class-engap-customposttype.php+113
Declaration of ENGAP_CustomPostType::get_posts($filter = Array, $context = 'view', $type = NULL, $page = 1) should be compatible with ENGAP_Posts::get_posts($filter = Array, $context = 'view', $type = 'post', $page = 1, $limit = 3)
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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
The following issues need your attention
- 10× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/engap/page/index.php
- > /wp-content/plugins/engap/page/page/listview.php
- > /wp-content/plugins/engap/page/blog.php
- > /wp-content/plugins/engap/page/post/listview.php
- > /wp-content/plugins/engap/page/post/fullview.php
- > /wp-content/plugins/engap/page/pages.php
- > /wp-content/plugins/engap/page/more.php
- > /wp-content/plugins/engap/page/portfolio.php
- > /wp-content/plugins/engap/page/products.php
- > /wp-content/plugins/engap/page/page/fullview.php
- 11× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/admin.php' (include_path='.:/usr/share/php') in wp-content/plugins/engap/lib/class-engap-server.php on line 10
- > ID =
- > PHP Fatal error
Uncaught Error: Class 'ENGAP_CustomPostType' not found in wp-content/plugins/engap/lib/class-engap-pages.php:21
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/engap/lib/class-engap-server.php on line 10
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/admin.php' (include_path='.:/usr/share/php') in wp-content/plugins/engap/lib/class-engap-server.php on line 10
- > PHP Warning
require_once(ABSPATHwp-admin/includes/admin.php): failed to open stream: No such file or directory in wp-content/plugins/engap/lib/class-engap-server.php on line 10
- > PHP Fatal error
Uncaught Error: Interface 'ENGAP_ResponseInterface' not found in wp-content/plugins/engap/lib/class-engap-response.php:3
- > PHP Fatal error
Uncaught Error: Class 'ENGAP_Posts' not found in wp-content/plugins/engap/lib/class-engap-customposttype.php:13
- > PHP Warning
require_once(ABSPATHwp-admin/includes/admin.php): failed to open stream: No such file or directory in wp-content/plugins/engap/lib/class-engap-server.php on line 10
- > ID =
- > PHP Fatal error
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
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Tags: There are too many tags (46 tag instead of maximum 10)
engap/plugin.php 92% from 13 tests
"enGap" version 0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("engap.php" instead of "plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,459 lines of code in 19 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 17 | 458 | 971 | 1,458 |
| CSS | 1 | 3 | 0 | 1 |
| JavaScript | 1 | 3 | 2 | 0 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 23.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 78.00 |
| Average method complexity | 3.81 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 2 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 1 | 16.67% |
| ▷ Concrete classes | 5 | 83.33% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 69 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 57 | 82.61% |
| ▷ Protected methods | 12 | 17.39% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 25 | |
| ▷ Named functions | 25 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 16 | |
| ▷ Global constants | 3 | 18.75% |
| ▷ Class constants | 13 | 81.25% |
| ▷ Public constants | 13 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected