Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼4.67ms] Passed 4 tests
Analyzing server-side resources used by Accessibility Assistant
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 39.34 ▲0.67 |
Dashboard /wp-admin | 3.34 ▲0.03 | 46.39 ▲0.45 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 42.98 ▼3.39 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 79.66 ▼14.38 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.50 ▼1.35 |
Server storage [IO: ▲1.03MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 17 new files
Database: no new tables, 10 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
accessibility_install |
can_compress_scripts |
accessibility_tokken |
accessibility_shopid |
accessibility_url |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Accessibility Assistant: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,171 ▲425 | 13.43 ▼1.13 | 5.10 ▲3.33 | 37.25 ▼5.39 |
Dashboard /wp-admin | 2,228 ▲37 | 5.19 ▲0.28 | 115.35 ▲11.37 | 52.83 ▲10.01 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.33 ▲0.30 | 38.99 ▲0.36 | 43.81 ▲10.04 |
Add New Post /wp-admin/post-new.php | 1,686 ▲167 | 22.82 ▼0.42 | 652.19 ▼32.05 | 49.17 ▼1.95 |
Media Library /wp-admin/upload.php | 1,413 ▲28 | 4.32 ▲0.12 | 97.35 ▼5.23 | 48.31 ▲4.14 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 9 options in the database
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- accessibility_shopid
- widget_recent-comments
- accessibility_url
- accessibility_tokken
- widget_theysaidso_widget
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
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/accessibility-assistant/admin/accessibility_dashboard.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 90% from 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
10 plugin tags: accessibility, blind, access, desaturation, visually...
accessibility-assistant/accessibility_assistant.php 77% from 13 tests
The main file in "Accessibility Assistant" v. 1.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.0" instead of "5.0")
- Description: Please keep the plugin description shorter than 140 characters (currently 190 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("accessibility-assistant.php" instead of "accessibility_assistant.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected14,395 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 3 | 1,230 | 21 | 9,195 |
JavaScript | 3 | 1,173 | 1,387 | 4,588 |
PHP | 5 | 78 | 20 | 612 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
5 PNG files occupy 0.27MB with 0.14MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-3.png | 66.96KB | 26.54KB | ▼ 60.37% |
assets/screenshot-1.png | 99.33KB | 38.50KB | ▼ 61.24% |
assets/header_logo.png | 7.02KB | 4.75KB | ▼ 32.35% |
assets/screenshot-2.png | 28.91KB | 14.86KB | ▼ 48.62% |
assets/screenshot-4.png | 75.63KB | 29.94KB | ▼ 60.42% |