Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼5.79ms] Passed 4 tests
Server-side resources used by WP Project Essentials
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 36.87 ▼7.03 |
Dashboard /wp-admin | 3.33 ▲0.03 | 51.91 ▼1.17 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 46.33 ▲0.73 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 85.99 ▼14.80 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.40 ▼0.17 |
Project Essentials /wp-admin/options-general.php?page=wp-project-essentials | 3.29 | 39.82 |
Server storage [IO: ▲0.46MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 26 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-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Project Essentials
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲32 | 14.28 ▲0.07 | 1.67 ▼0.33 | 41.69 ▼8.24 |
Dashboard /wp-admin | 2,202 ▲22 | 5.54 ▼0.16 | 88.76 ▼1.83 | 38.77 ▼0.69 |
Posts /wp-admin/edit.php | 2,104 ▲1 | 2.14 ▲0.15 | 35.61 ▼5.18 | 34.69 ▼5.05 |
Add New Post /wp-admin/post-new.php | 1,529 ▼25 | 17.45 ▼1.05 | 668.96 ▲5.86 | 59.18 ▲5.02 |
Media Library /wp-admin/upload.php | 1,401 ▲4 | 4.21 ▼0.00 | 101.94 ▼1.44 | 45.91 ▲2.34 |
Project Essentials /wp-admin/options-general.php?page=wp-project-essentials | 1,442 | 3.73 | 62.92 | 38.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
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
Please take a closer look at the following
- 3× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-project-essentials/about/modal-other-plugins.php
- > /wp-content/plugins/wp-project-essentials/about/about-html.php
- > /wp-content/plugins/wp-project-essentials/about/modal-about-us.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_enqueue_style() in wp-content/plugins/wp-project-essentials/about/admin-enqueue-script.php:4
- > 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 93% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need to be fixed:
- Screenshots: Please add descriptions for these screenshots #1, #2, #3 in wp-project-essentials/assets to your readme.txt
- Tags: Too many tags (13 tag instead of maximum 10); only the first 5 tags are used in your directory listing
wp-project-essentials/wp-project-essentials.php Passed 13 tests
"WP Project Essentials" version 1.0.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
98 characters long description:
A plugin that gather many minor admin-side customization that often needed for a WordPress project
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
Good job! No executable or dangerous file extensions detected1,394 lines of code in 23 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 19 | 169 | 103 | 826 |
CSS | 4 | 43 | 11 | 568 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 5.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 11.00 |
Average method complexity | 1.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 16 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 14 | 87.50% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 12.50% |
Functions | 22 | |
▷ Named functions | 22 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 8 | |
▷ Global constants | 8 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.42MB with 0.28MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
about/assets/about-image.png | 364.66KB | 95.69KB | ▼ 73.76% |
assets/logo.png | 61.35KB | 23.10KB | ▼ 62.34% |