Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼305.18ms] Passed 4 tests
This is a short check of server-side resources used by Logaster Logo Generator
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.65 ▲0.13 | 63.77 ▲14.94 |
Dashboard /wp-admin | 3.49 ▲0.08 | 34.58 ▼1.79 |
Posts /wp-admin/edit.php | 3.72 ▲0.07 | 41.78 ▲2.97 |
Add New Post /wp-admin/post-new.php | 6.96 ▼0.02 | 93.68 ▼1,222.06 |
Media Library /wp-admin/upload.php | 3.37 ▲0.07 | 27.66 ▲0.18 |
Logo details /wp-admin/admin.php?page=logotype-details | 3.35 | 22.24 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 8 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Logaster Logo Generator
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,830 ▲85 | 15.28 ▼0.75 | 6.10 ▲0.74 | 2.11 ▼1.24 |
Dashboard /wp-admin | 2,937 ▲76 | 6.18 ▼0.01 | 119.22 ▼23.23 | 161.69 ▼4.51 |
Posts /wp-admin/edit.php | 2,736 ▲42 | 3.25 ▲0.01 | 65.06 ▲1.26 | 142.96 ▼2.33 |
Add New Post /wp-admin/post-new.php | 1,765 ▲75 | 21.03 ▲0.38 | 454.48 ▼4.38 | 161.37 ▼4.57 |
Media Library /wp-admin/upload.php | 1,746 ▲48 | 5.48 ▼0.00 | 143.82 ▼20.89 | 187.34 ▼13.64 |
Logo details /wp-admin/admin.php?page=logotype-details | 1,028 | 2.62 | 54.84 | 89.03 |
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
The following items require your attention
- The plugin did not uninstall gracefully
- > Warning in wp-content/plugins/logaster-logo-generator/class.logaster.php+69
rmdir(wp-content/uploads/logos): Directory not empty
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/admin.php?page=logotype-details
- > Notice in wp-content/plugins/logaster-logo-generator/views/logo_details.php+20
Trying to access array offset on value of type null
SRP 50% 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 fix the following items
- 3× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/logaster-logo-generator/views/logo_details.php
- > /wp-content/plugins/logaster-logo-generator/logaster-logo-generator.php
- > /wp-content/plugins/logaster-logo-generator/views/create_logo.php
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
These are user-side errors you should fix
- > GET request to /wp-admin/admin.php?page=logotype-details
- > Javascript (severe) in unknown
/wp-admin/admin.php?page=logotype-details 156:37 Uncaught SyntaxError: Unexpected token '}'
Optimizations
Plugin configuration 96% 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: logo plugin, logo, logotype, free logo, create logo...
logaster-logo-generator/logaster-logo-generator.php 92% from 13 tests
This is the main PHP file of "Logaster Logo Generator" version 1.3, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin554 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 100 | 92 | 442 |
PO File | 1 | 21 | 21 | 73 |
CSS | 1 | 5 | 0 | 39 |
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.23 |
Average class complexity | 34.00 |
▷ Minimum class complexity | 34.00 |
▷ Maximum class complexity | 34.00 |
Average method complexity | 2.78 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.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 | 19 | |
▷ Static methods | 9 | 47.37% |
▷ Public methods | 11 | 57.89% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 42.11% |
Functions | 2 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 2 | 100.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
No PNG images were found in this plugin