Benchmarks
Plugin footprint 83% 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: ▼1.66ms] Passed 4 tests
This is a short check of server-side resources used by Content Parts
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.99 ▼3.25 |
Dashboard /wp-admin | 3.33 ▲0.03 | 45.77 ▼5.10 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 47.93 ▲1.26 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 96.75 ▲6.53 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 37.94 ▲0.45 |
Content Parts /wp-admin/themes.php?page=content_parts | 3.21 | 30.94 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 18 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
content_parts_auto_format_post_types |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Content Parts
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,813 ▲78 | 14.47 ▲0.09 | 1.76 ▼0.03 | 43.74 ▼5.77 |
Dashboard /wp-admin | 2,219 ▲31 | 4.86 ▼1.02 | 114.55 ▼1.45 | 40.99 ▼1.64 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.05 ▲0.08 | 39.44 ▲2.59 | 35.66 ▲1.70 |
Add New Post /wp-admin/post-new.php | 1,536 ▲19 | 23.31 ▲5.62 | 666.10 ▲19.63 | 54.69 ▼2.80 |
Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.16 ▼0.13 | 96.75 ▼1.77 | 43.09 ▲0.82 |
Content Parts /wp-admin/themes.php?page=content_parts | 795 | 2.03 | 26.75 | 31.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 7 options in the database
- theysaidso_admin_options
- content_parts_auto_format_post_types
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/content-parts/admin/settings.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/content-parts/admin/editor.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/content-parts/content-parts.php:94
- > PHP Fatal error
Uncaught Error: Class 'Content_Parts_Plugin' not found in wp-content/plugins/content-parts/includes/content-parts.php:32
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 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
6 plugin tags: content, the_content, theme, templates, editor...
content-parts/content-parts.php Passed 13 tests
The main file in "Content Parts" v. 1.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
96 characters long description:
Divide your post content into parts that you can use in different areas of your theme templates.
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
No dangerous file extensions were detected655 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 239 | 489 | 413 |
Markdown | 2 | 45 | 0 | 97 |
SVG | 2 | 0 | 2 | 81 |
JavaScript | 1 | 26 | 16 | 61 |
CSS | 1 | 1 | 0 | 3 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 10.40 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 27.00 |
Average method complexity | 2.15 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 41 | |
▷ Static methods | 27 | 65.85% |
▷ Public methods | 37 | 90.24% |
▷ Protected methods | 2 | 4.88% |
▷ Private methods | 2 | 4.88% |
Functions | 6 | |
▷ Named functions | 6 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
js/tinymce/plugins/contentparts/img/button.png | 0.23KB | 0.12KB | ▼ 47.26% |