Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.47ms] Passed 4 tests
Server-side resources used by Cryptum NFT
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 35.32 ▼3.76 |
Dashboard /wp-admin | 3.31 ▲0.01 | 43.20 ▼10.83 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 44.38 ▼0.92 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 83.18 ▼12.70 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 32.20 ▼2.59 |
Server storage [IO: ▲3.30MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 81 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
Cryptum NFT: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,831 ▲85 | 14.74 ▼0.04 | 1.99 ▼0.30 | 40.52 ▼2.27 |
Dashboard /wp-admin | 2,215 ▲23 | 5.86 ▲0.98 | 96.25 ▼20.60 | 39.36 ▼6.18 |
Posts /wp-admin/edit.php | 2,094 ▲5 | 2.01 ▼0.04 | 37.64 ▲1.83 | 32.29 ▼4.21 |
Add New Post /wp-admin/post-new.php | 1,539 ▲25 | 23.12 ▲5.62 | 659.89 ▼14.19 | 62.10 ▲14.12 |
Media Library /wp-admin/upload.php | 1,394 ▲6 | 4.17 ▼0.04 | 96.51 ▼6.49 | 42.34 ▼4.82 |
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 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% 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 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
Please fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Parse error
syntax error, unexpected '|', expecting variable (T_VARIABLE) in wp-content/plugins/cryptum-nft/lib/symfony/polyfill-mbstring/bootstrap80.php on line 15
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/cryptum-nft/uninstall.php:3
- > PHP Parse error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
8 plugin tags: nft, e-commerce, store, crypto, blockchain...
cryptum-nft/cryptum-nft.php 92% from 13 tests
"Cryptum NFT" version 1.1.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Success! There were no dangerous files found in this plugin7,370 lines of code in 62 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 33 | 521 | 555 | 6,212 |
JavaScript | 8 | 33 | 225 | 312 |
CSS | 6 | 17 | 7 | 243 |
JSON | 4 | 0 | 0 | 234 |
PO File | 1 | 71 | 106 | 148 |
YAML | 5 | 26 | 0 | 143 |
Markdown | 3 | 18 | 0 | 38 |
XML | 1 | 4 | 0 | 29 |
SVG | 1 | 0 | 1 | 11 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.58 |
Average class complexity | 28.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 166.00 |
Average method complexity | 4.23 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 7 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 18 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 18 | 100.00% |
▷ Final classes | 2 | 11.11% |
Methods | 149 | |
▷ Static methods | 98 | 65.77% |
▷ Public methods | 127 | 85.23% |
▷ Protected methods | 1 | 0.67% |
▷ Private methods | 21 | 14.09% |
Functions | 90 | |
▷ Named functions | 78 | 86.67% |
▷ Anonymous functions | 12 | 13.33% |
Constants | 20 | |
▷ Global constants | 9 | 45.00% |
▷ Class constants | 11 | 55.00% |
▷ Public constants | 7 | 63.64% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin