Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲1.25MB] [CPU: ▼1.42ms] Passed 4 tests
A check of server-side resources used by Digital Publishing Tools for WordPress
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.74 ▲1.28 | 49.38 ▲8.26 |
| Dashboard /wp-admin | 4.60 ▲1.25 | 57.97 ▼0.04 |
| Posts /wp-admin/edit.php | 4.65 ▲1.29 | 66.86 ▲19.13 |
| Add New Post /wp-admin/post-new.php | 7.12 ▲1.23 | 87.36 ▼18.47 |
| Media Library /wp-admin/upload.php | 4.46 ▲1.23 | 42.12 ▲4.56 |
Server storage [IO: ▲8.69MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 352 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| dpsfa_defaultTemplate |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Digital Publishing Tools for WordPress: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,818 ▲72 | 13.33 ▼1.10 | 1.91 ▲0.02 | 42.07 ▼1.59 |
| Dashboard /wp-admin | 2,221 ▲36 | 4.80 ▼0.09 | 97.53 ▼5.35 | 37.95 ▼8.49 |
| Posts /wp-admin/edit.php | 2,134 ▲38 | 2.05 ▲0.03 | 43.65 ▲2.26 | 37.97 ▲3.89 |
| Add New Post /wp-admin/post-new.php | 1,546 ▲32 | 23.37 ▲5.78 | 665.93 ▼22.70 | 62.72 ▲17.65 |
| Media Library /wp-admin/upload.php | 1,400 ▲15 | 4.23 ▲0.05 | 96.95 ▼10.22 | 45.99 ▼1.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- dpsfa_defaultTemplate
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not 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
The following issues need your attention
- 18× GET requests to PHP files return non-empty strings (only 10 are shown):
- > /wp-content/plugins/digital-publishing/classes/cms-modules/wordpress/dpsfa-cms-wordpress-ajax.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-bundlr.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-templates.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-content.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-error-logging.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-publication.php
- > /wp-content/plugins/digital-publishing/classes/cms-modules/wordpress/dpsfa-cms-wordpress.php
- > /wp-content/plugins/digital-publishing/classes/cms-modules/wordpress/dpsfa-cms-wordpress-cpt-article.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-curl.php
- > /wp-content/plugins/digital-publishing/classes/dpsfa-entity.php
- 17× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Mustache_Logger_AbstractLogger' not found in wp-content/plugins/digital-publishing/libs/Mustache/Logger/StreamLogger.php:21
- > PHP Fatal error
Uncaught Error: Call to undefined function DPSFolioAuthor\\get_bloginfo() in wp-content/plugins/digital-publishing/classes/cms-modules/wordpress/dpsfa-cms-wordpress.php:37
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Exception' not found in wp-content/plugins/digital-publishing/libs/Mustache/Exception/UnknownHelperException.php:15
- > PHP Warning
Use of undefined constant DPSFA_DIR_NAME - assumed 'DPSFA_DIR_NAME' (this will throw an Error in a future version of PHP) in wp-content/plugins/digital-publishing/publish-templates/article.php on line 15
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Loader' not found in wp-content/plugins/digital-publishing/libs/Mustache/Loader/StringLoader.php:26
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Logger' not found in wp-content/plugins/digital-publishing/libs/Mustache/Logger/AbstractLogger.php:21
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Exception' not found in wp-content/plugins/digital-publishing/libs/Mustache/Exception/UnknownFilterException.php:15
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Loader' not found in wp-content/plugins/digital-publishing/libs/Mustache/Loader/InlineLoader.php:51
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Loader' not found in wp-content/plugins/digital-publishing/libs/Mustache/Loader/FilesystemLoader.php:27
- > PHP Fatal error
Uncaught Error: Interface 'Mustache_Exception' not found in wp-content/plugins/digital-publishing/libs/Mustache/Exception/InvalidArgumentException.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
7 plugin tags: digital publishing, dps, digital publishing solution, aem mobile, adobe...
digital-publishing/digital-publishing-tools-for-wordpress.php 85% from 13 tests
The principal PHP file in "Digital Publishing Tools for WordPress" v. 2.1.0 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 153 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("digital-publishing.php" instead of "digital-publishing-tools-for-wordpress.php")
Code Analysis 95% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin62,489 lines of code in 307 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 63 | 6,676 | 26,429 | 32,727 |
| PHP | 51 | 1,447 | 2,837 | 9,173 |
| CSS | 12 | 28 | 53 | 7,689 |
| LESS | 71 | 1,351 | 1,576 | 5,906 |
| HTML | 46 | 799 | 252 | 4,466 |
| Markdown | 15 | 391 | 0 | 1,006 |
| JSON | 42 | 1 | 0 | 897 |
| SVG | 1 | 0 | 0 | 288 |
| CoffeeScript | 2 | 45 | 50 | 168 |
| TypeScript | 1 | 14 | 18 | 94 |
| Mustache | 2 | 0 | 0 | 69 |
| make | 1 | 3 | 0 | 6 |
PHP code 0% from 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
It is recommended to fix the following
- Cyclomatic complexity of classes should be reduced to less than 1000 (currently 1,053)
- Method cyclomatic complexity has to be reduced to less than 100 (currently 1,003)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 39.74 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 1,053.00 |
| Average method complexity | 5.15 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 1,003.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 4 | |
| Traits | 0 | |
| Classes | 46 | |
| ▷ Abstract classes | 2 | 4.35% |
| ▷ Concrete classes | 44 | 95.65% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 480 | |
| ▷ Static methods | 11 | 2.29% |
| ▷ Public methods | 367 | 76.46% |
| ▷ Protected methods | 26 | 5.42% |
| ▷ Private methods | 87 | 18.12% |
| Functions | 7 | |
| ▷ Named functions | 6 | 85.71% |
| ▷ Anonymous functions | 1 | 14.29% |
| Constants | 135 | |
| ▷ Global constants | 75 | 55.56% |
| ▷ Class constants | 60 | 44.44% |
| ▷ Public constants | 60 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
10 PNG files occupy 3.34MB with 2.38MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-1024x1024.png | 661.78KB | 177.75KB | ▼ 73.14% |
| assets/screenshot-3.png | 1,178.08KB | 385.58KB | ▼ 67.27% |
| assets/icon-256x256.png | 78.96KB | 21.30KB | ▼ 73.02% |
| assets/screenshot-2.png | 432.21KB | 125.07KB | ▼ 71.06% |
| assets/icon.png | 229.09KB | 63.25KB | ▼ 72.39% |