Benchmarks
Plugin footprint Passed 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.07MB] [CPU: ▼139.65ms] Passed 4 tests
This is a short check of server-side resources used by Bijbel Plugin voor Wordpress
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.92 ▲0.19 | 44.02 ▲21.86 |
Dashboard /wp-admin | 3.14 ▲0.08 | 49.33 ▼11.41 |
Posts /wp-admin/edit.php | 3.19 ▲0.08 | 50.93 ▲2.21 |
Add New Post /wp-admin/post-new.php | 5.50 ▲0.07 | 104.45 ▼547.15 |
Media Library /wp-admin/upload.php | 3.08 ▲0.07 | 41.14 ▼2.23 |
Server storage [IO: ▲3.35MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 57 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Bijbel Plugin voor Wordpress: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 4,050 ▲454 | 16.87 ▲1.35 | 37.39 ▲27.55 | 51.75 ▼2.62 |
Dashboard /wp-admin | 2,993 ▲62 | 5.94 ▼0.04 | 147.83 ▼24.57 | 125.42 ▲9.07 |
Posts /wp-admin/edit.php | 2,788 ▲49 | 2.70 ▼0.01 | 67.45 ▲3.29 | 97.57 ▼6.52 |
Add New Post /wp-admin/post-new.php | 1,514 ▲14 | 16.68 ▼1.89 | 303.48 ▼92.02 | 120.67 ▼4.32 |
Media Library /wp-admin/upload.php | 1,855 ▲48 | 5.03 ▲0.00 | 154.69 ▼8.39 | 107.22 ▼33.45 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 50% 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 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 4× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/bijbelteksten/bible-versions/bg.php
- > /wp-content/plugins/bijbelteksten/bverse-convert.php
- > /wp-content/plugins/bijbelteksten/bible-versions/biblia.php
- > /wp-content/plugins/bijbelteksten/bible-versions/bibles.php
- 3× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/bijbelteksten/includes/shortcodes/shortcode-bibles.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/bijbelteksten/includes/shortcodes/shortcode-bg.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/bijbelteksten/includes/shortcodes/shortcode-biblia.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
2 plugin tags: bijbelteksten, bijbel
bijbelteksten/bverse-convert.php 92% from 13 tests
The principal PHP file in "Bijbel Plugin voor Wordpress" v. 1.0 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("bijbelteksten.php" instead of "bverse-convert.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 detected19,358 lines of code in 27 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 8 | 77 | 279 | 11,436 |
JavaScript | 11 | 324 | 70 | 4,813 |
SVG | 1 | 0 | 0 | 2,671 |
PHP | 7 | 138 | 152 | 438 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
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 | 21 | |
▷ Named functions | 21 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
15 PNG files occupy 1.37MB with 0.81MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/fancybox_sprite@2x.png | 5.76KB | 5.76KB | 0.02% |
Lightbox.png | 481.41KB | 152.88KB | ▼ 68.24% |
img/TopSprites.png | 2.86KB | 0.25KB | ▼ 91.09% |
Instellingen.png | 179.07KB | 55.14KB | ▼ 69.21% |
screenshot-2.png | 481.41KB | 152.88KB | ▼ 68.24% |