Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.06MB] [CPU: ▼1.64ms] Passed 4 tests
Analyzing server-side resources used by Accessibility by Audioeye
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 39.06 ▲0.57 |
Dashboard /wp-admin | 3.35 ▲0.05 | 46.92 ▼2.24 |
Posts /wp-admin/edit.php | 3.47 ▲0.11 | 45.31 ▼1.32 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 88.97 ▼2.55 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 34.46 ▼0.44 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 24 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Accessibility by Audioeye: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,823 ▲88 | 13.60 ▼0.69 | 1.67 ▼0.07 | 42.95 ▼5.49 |
Dashboard /wp-admin | 2,232 ▲44 | 4.88 ▼0.04 | 97.87 ▼5.57 | 39.04 ▼6.61 |
Posts /wp-admin/edit.php | 2,112 ▲26 | 2.03 ▲0.02 | 34.91 ▼3.59 | 32.76 ▼1.36 |
Add New Post /wp-admin/post-new.php | 1,543 ▲10 | 18.29 ▼4.90 | 610.26 ▼62.20 | 56.41 ▼13.52 |
Media Library /wp-admin/upload.php | 1,411 ▲20 | 4.25 ▲0.11 | 96.36 ▼5.10 | 41.88 ▼3.39 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Good news, no errors were detected
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/accessibility-by-audioeye/public/partials/audioeye-public-display.php
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_create_nonce() in wp-content/plugins/accessibility-by-audioeye/admin/partials/audioeye-admin-display.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Donate link: Please fix this invalid url: "www.audioeye.com"
- Plugin Name: Please specify the plugin name on the first line (
=== accessibility-by-audioeye ===
)
accessibility-by-audioeye/audioeye.php 77% from 13 tests
The main PHP file in "Accessibility by Audioeye" ver. 1.0.47 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Description: The description should be shorter than 140 characters (currently 174 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("accessibility-by-audioeye.php" instead of "audioeye.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected811 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 154 | 495 | 463 |
CSS | 2 | 63 | 8 | 297 |
JavaScript | 2 | 16 | 27 | 51 |
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.16 |
Average class complexity | 2.43 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.40 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 25 | |
▷ Static methods | 2 | 8.00% |
▷ Public methods | 20 | 80.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 20.00% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected