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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.44ms] Passed 4 tests
Analyzing server-side resources used by FAQ Block
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 34.98 ▼1.35 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 44.53 ▼13.75 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.84 ▼4.26 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.49 ▼10.41 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.50 ▲1.87 |
Server storage [IO: ▲0.20MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 15 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for FAQ Block
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,793 ▲32 | 14.72 ▲0.37 | 1.57 ▲0.01 | 39.37 ▲0.65 |
| Dashboard /wp-admin | 2,195 ▲17 | 5.62 ▼0.05 | 90.86 ▼16.05 | 40.02 ▼4.18 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 2.02 ▲0.03 | 38.32 ▼6.78 | 38.31 ▲0.98 |
| Add New Post /wp-admin/post-new.php | 6,376 ▲4,850 | 22.35 ▼1.07 | 845.67 ▲184.10 | 52.22 ▼3.10 |
| Media Library /wp-admin/upload.php | 1,394 ▼3 | 4.15 ▲0.00 | 94.77 ▼3.44 | 40.73 ▼3.88 |
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
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/faq-block/faq-block.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% 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 require attention:
- Screenshots: Add descriptions for screenshots #1, #2 in faq-block/assets to your readme.txt
faq-block/faq-block.php Passed 13 tests
The entry point to "FAQ Block" version 1.0.8 is a PHP file that has certain tags in its header comment area
75 characters long description:
Very simple and clean Gutenberg Block for FAQ (Frequently Asked Questions).
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
No dangerous file extensions were detected5,085 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 2 | 0 | 0 | 4,781 |
| JavaScript | 3 | 11 | 4 | 123 |
| CSS | 4 | 14 | 0 | 76 |
| Sass | 2 | 14 | 6 | 63 |
| PHP | 1 | 12 | 19 | 42 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/meowapps.png | 3.54KB | 3.59KB | 0.00% |