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 successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.15MB] [CPU: ▼308.04ms] Passed 4 tests
Analyzing server-side resources used by Timeline Blocks for Gutenberg
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.77 ▲0.26 | 54.90 ▲4.59 |
Dashboard /wp-admin | 3.60 ▲0.19 | 35.61 ▲1.31 |
Posts /wp-admin/edit.php | 3.82 ▲0.18 | 38.40 ▲0.78 |
Add New Post /wp-admin/post-new.php | 5.82 ▼1.15 | 54.30 ▼1,238.84 |
Media Library /wp-admin/upload.php | 3.47 ▲0.18 | 28.39 ▲5.22 |
Server storage [IO: ▲3.16MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 57 new files
Database: no new tables, 1 new option
New WordPress options |
---|
tb_timeline_gutenberg_do_activation_redirect |
Browser metrics Passed 4 tests
Checking browser requirements for Timeline Blocks for Gutenberg
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,801 ▲47 | 16.19 ▲0.52 | 6.21 ▼0.24 | 2.27 ▲0.09 |
Dashboard /wp-admin | 2,895 ▲44 | 6.17 ▲0.10 | 118.20 ▼15.89 | 154.23 ▼6.11 |
Posts /wp-admin/edit.php | 2,691 ▲3 | 3.23 ▼0.02 | 62.99 ▲0.33 | 138.32 ▼4.32 |
Add New Post /wp-admin/post-new.php | 1,766 ▲106 | 22.30 ▲6.62 | 481.64 ▲83.86 | 175.64 ▲21.25 |
Media Library /wp-admin/upload.php | 1,698 ▼0 | 5.46 ▼0.07 | 140.23 ▲3.06 | 180.80 ▲1.96 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Zombie WordPress options were found after uninstall: 1 option
- tb_timeline_gutenberg_do_activation_redirect
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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
Please fix the following items
- 7× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
require(): Failed opening required 'TB_DIRsrc/tb-helper/class-tb-config.php' (include_path='.:/usr/share/php') in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-helper.php on line 70
- > PHP Warning
Use of undefined constant TB_DIR - assumed 'TB_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-helper.php on line 70
- > PHP Warning
require(TB_DIRsrc/tb-helper/class-tb-config.php): failed to open stream: No such file or directory in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-helper.php on line 70
- > PHP Warning
require(TB_DIRsrc/tb-helper/class-tb-helper.php): failed to open stream: No such file or directory in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-loader.php on line 50
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/timeline-blocks/src/blocks/index.php:654
- > PHP Fatal error
require(): Failed opening required 'TB_DIRsrc/tb-helper/class-tb-helper.php' (include_path='.:/usr/share/php') in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-loader.php on line 50
- > PHP Warning
Use of undefined constant TB_DIR - assumed 'TB_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/timeline-blocks/src/tb-helper/class-tb-loader.php on line 50
- > PHP Fatal error
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 Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
5 plugin tags: post timeline blocks, timeline templates, timeline layouts, timeline blocks, gutenberg block
timeline-blocks/timeline-blocks.php Passed 13 tests
Analyzing the main PHP file in "Timeline Blocks for Gutenberg" version 1.1.3
112 characters long description:
A beautiful timeline block to showcase your posts in timeline presentation with multiple templates availability.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin11,451 lines of code in 43 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 14 | 1,850 | 50 | 4,360 |
SVG | 3 | 0 | 0 | 3,927 |
JavaScript | 12 | 142 | 61 | 1,248 |
PHP | 10 | 251 | 455 | 1,128 |
Sass | 4 | 106 | 14 | 788 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 6.57 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 36.00 |
Average method complexity | 2.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 3 | 42.86% |
Methods | 25 | |
▷ Static methods | 12 | 48.00% |
▷ Public methods | 24 | 96.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 4.00% |
Functions | 28 | |
▷ Named functions | 27 | 96.43% |
▷ Anonymous functions | 1 | 3.57% |
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
There were not PNG files found in your plugin