Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.88ms] Passed 4 tests
Analyzing server-side resources used by ProcessingJS for WordPress
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 38.83 ▼0.30 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 50.77 ▼12.76 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.97 ▲0.45 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 91.94 ▼1.94 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.02 | 33.34 ▼4.51 |
| ProcessingJS for WP /wp-admin/options-general.php?page=pjs4wp_instructions | 3.22 | 29.52 |
Server storage [IO: ▲0.23MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for ProcessingJS for WordPress
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,841 ▲95 | 13.37 ▼1.19 | 4.78 ▲3.09 | 42.55 ▼0.58 |
| Dashboard /wp-admin | 2,215 ▲29 | 5.85 ▲0.89 | 98.51 ▼12.46 | 38.16 ▼7.00 |
| Posts /wp-admin/edit.php | 2,095 ▲3 | 2.00 ▼0.03 | 37.72 ▲1.68 | 33.05 ▲0.81 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲22 | 23.40 ▲5.71 | 593.33 ▼56.16 | 52.48 ▼16.29 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.25 ▲0.02 | 98.54 ▼9.18 | 40.57 ▼1.01 |
| ProcessingJS for WP /wp-admin/options-general.php?page=pjs4wp_instructions | 910 | 2.01 | 28.02 | 31.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/processingjs-for-wp/processingjs-for-wp.php:125
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
7 plugin tags: pjs4wp, processingjs, jquery, processingorg, processing...
processingjs-for-wp/processingjs-for-wp.php Passed 13 tests
This is the main PHP file of "ProcessingJS for WordPress" version 1.2.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
88 characters long description:
Directly write Processing.js code in your post / page or include an existing .pde sketch
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
No dangerous file extensions were detected593 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 0 | 0 | 431 |
| PHP | 1 | 20 | 92 | 128 |
| CSS | 2 | 0 | 1 | 34 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 9.00 |
| ▷ Minimum class complexity | 9.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 8 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 8 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
There are no PNG files in this plugin