Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
You still need to fix the following installer errors
- The plugin did not install without errors
- > Warning in wp-content/plugins/jnext-timeline-blocks/jnext-timeline-blocks.php+26
require_once(wp-content/plugins/jnext-timeline-blocks/class-block-assets.php): failed to open stream: No such file or directory
Server metrics [RAM: ▼0.01MB] [CPU: ▼10.04ms] Passed 4 tests
Analyzing server-side resources used by GUTENBERG TIMELINE BLOCK
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 35.21 ▼8.88 |
| Dashboard /wp-admin | 3.31 ▼0.04 | 45.22 ▼18.58 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.94 ▼1.62 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 90.26 ▼11.09 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.34 ▼0.65 |
Server storage [IO: ▲4.07MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 56 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for GUTENBERG TIMELINE BLOCK
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,790 ▲43 | 14.37 ▲0.03 | 1.60 ▼0.34 | 37.89 ▼7.76 |
| Dashboard /wp-admin | 2,195 ▲18 | 5.61 ▼0.05 | 91.89 ▼6.11 | 37.98 ▼5.64 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.94 ▲0.01 | 40.52 ▼2.24 | 35.56 ▼2.11 |
| Add New Post /wp-admin/post-new.php | 1,529 ▼6 | 23.14 ▼0.05 | 576.56 ▼38.33 | 53.95 ▲4.09 |
| Media Library /wp-admin/upload.php | 1,394 ▼9 | 4.22 ▼0.03 | 93.89 ▼4.88 | 41.80 ▼2.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
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
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)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/jnext-timeline-blocks/src/block/jnext-post-timeline/block.php:782
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/jnext-timeline-blocks/src/fonts/GoogleFonts.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: These screenshots need descriptions #1, #2, #3, #4, #5, #6, #7, #8, #9 in jnext-timeline-blocks/assets to your readme.txt
- Tags: Please delete some tags, you are using 14 tag instead of maximum 10
jnext-timeline-blocks/plugin.php 92% from 13 tests
The main file in "GUTENBERG TIMELINE BLOCK" v. 1.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("jnext-timeline-blocks.php" instead of "plugin.php")
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
No dangerous file extensions were detected36,188 lines of code in 51 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 2 | 0 | 0 | 24,990 |
| JavaScript | 28 | 766 | 358 | 7,131 |
| PHP | 6 | 547 | 339 | 2,651 |
| Sass | 8 | 16 | 1 | 1,071 |
| CSS | 6 | 43 | 8 | 332 |
| SVG | 1 | 1 | 0 | 13 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 68.00 |
| ▷ Minimum class complexity | 68.00 |
| ▷ Maximum class complexity | 68.00 |
| Average method complexity | 4.19 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 20.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 1 | 100.00% |
| Methods | 21 | |
| ▷ Static methods | 16 | 76.19% |
| ▷ Public methods | 21 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 21 | |
| ▷ Named functions | 21 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 10 | |
| ▷ Global constants | 10 | 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 images were found in this plugin