Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼142.08ms] Passed 4 tests
A check of server-side resources used by Gridy Portfolio
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.87 ▲0.04 | 34.78 ▼3.48 |
| Dashboard /wp-admin | 3.09 ▲0.03 | 46.26 ▲2.91 |
| Posts /wp-admin/edit.php | 3.14 ▲0.03 | 43.51 ▼3.42 |
| Add New Post /wp-admin/post-new.php | 5.44 ▲0.01 | 86.04 ▼563.28 |
| Media Library /wp-admin/upload.php | 3.03 ▲0.03 | 33.88 ▲1.87 |
| Add Portfolio item /wp-admin/post-new.php?post_type=gportfolio | 3.14 | 51.81 |
| Category /wp-admin/edit-tags.php?taxonomy=gportfolio-category&post_type=gportfolio | 3.03 | 32.12 |
| G Portfolio /wp-admin/edit.php?post_type=gportfolio | 3.07 | 33.19 |
Server storage [IO: ▲0.75MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 23 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Gridy Portfolio
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,854 ▲282 | 16.79 ▲1.25 | 19.84 ▲9.51 | 68.95 ▲24.36 |
| Dashboard /wp-admin | 3,010 ▲76 | 5.95 ▲0.01 | 139.60 ▼12.22 | 106.90 ▼9.08 |
| Posts /wp-admin/edit.php | 2,779 ▲40 | 2.72 ▲0.01 | 63.22 ▼21.41 | 83.82 ▼6.47 |
| Add New Post /wp-admin/post-new.php | 1,698 ▲17 | 18.87 ▲3.63 | 402.30 ▼2.63 | 107.51 ▼3.82 |
| Media Library /wp-admin/upload.php | 1,850 ▲43 | 5.01 ▼0.03 | 150.72 ▼0.14 | 123.97 ▲18.62 |
| Add Portfolio item /wp-admin/post-new.php?post_type=gportfolio | 3,187 | 8.96 | 226.49 | 137.10 |
| Category /wp-admin/edit-tags.php?taxonomy=gportfolio-category&post_type=gportfolio | 1,779 | 2.38 | 60.86 | 81.27 |
| G Portfolio /wp-admin/edit.php?post_type=gportfolio | 1,436 | 2.64 | 63.53 | 74.58 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/gridy-portfolio/gportfolio.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
4 plugin tags: grid portfolio, portfolio, grid, expandable
gridy-portfolio/gportfolio.php 92% from 13 tests
Analyzing the main PHP file in "Gridy Portfolio" version 1.0
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("gridy-portfolio.php" instead of "gportfolio.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected1,898 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| SVG | 2 | 0 | 0 | 702 |
| CSS | 4 | 119 | 32 | 541 |
| JavaScript | 4 | 127 | 120 | 446 |
| PHP | 1 | 47 | 22 | 209 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| 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 | 7 | |
| ▷ Named functions | 7 | 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 Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
3 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/ico-delete.png | 0.70KB | 0.72KB | 0.00% |
| images/more.png | 4.22KB | 1.06KB | ▼ 74.84% |
| images/expand.png | 1.04KB | 0.19KB | ▼ 81.70% |