Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▼1.95MB] [CPU: ▼57.01ms] Passed 4 tests
An overview of server-side resources used by Frame to Folio
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.05 ▼1.41 | 4.62 ▼40.62 |
| Dashboard /wp-admin | 2.07 ▼1.28 | 5.95 ▼59.13 |
| Posts /wp-admin/edit.php | 2.07 ▼1.28 | 5.38 ▼41.53 |
| Add New Post /wp-admin/post-new.php | 2.07 ▼3.82 | 5.34 ▼86.75 |
| Media Library /wp-admin/upload.php | 2.07 ▼1.16 | 8.41 ▼28.53 |
Server storage [IO: ▲0.01MB] [DB: ▲0.31MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Frame to Folio
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,821 ▲75 | 13.67 ▼0.49 | 2.06 ▲0.01 | 44.33 ▼0.55 |
| Dashboard /wp-admin | 2,223 ▲20 | 5.85 ▼0.05 | 114.47 ▼1.37 | 43.29 ▼0.45 |
| Posts /wp-admin/edit.php | 2,099 ▼1 | 2.02 ▲0.04 | 36.99 ▼2.84 | 34.81 ▲2.66 |
| Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 17.52 ▼0.15 | 670.19 ▲17.92 | 56.59 ▲2.85 |
| Media Library /wp-admin/upload.php | 1,396 ▲2 | 4.22 ▼0.09 | 114.21 ▲11.60 | 47.15 ▲3.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.31MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- Uninstall procedure had uncaught errors
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the frame-to-folio-css-main handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
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 | 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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/frame-to-folio/frame-to-folio.php:17
- > 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 97% from 29 tests
readme.txt 94% from 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
These attributes need your attention:
- Plugin Name: Please specify the plugin name on the first line (
=== frame-to-folio ===)
frame-to-folio/frame-to-folio.php Passed 13 tests
The primary PHP file in "Frame to Folio" version 1.0.0 is used by WordPress to initiate all plugin functionality
42 characters long description:
Insert iframe tag linked on portfolio item
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin98 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 3 | 3 | 42 |
| PHP | 1 | 10 | 7 | 39 |
| CSS | 1 | 0 | 0 | 17 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.05 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 1.14 |
| ▷ 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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 85.71% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 14.29% |
| 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 |
| mce/images/frame.png | 0.64KB | 0.66KB | 0.00% |