Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼4.57ms] Passed 4 tests
A check of server-side resources used by Frontend Developer
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.71 ▼0.12 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 49.94 ▼11.21 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 51.78 ▲1.40 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 87.02 ▼8.35 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 39.31 ▲5.86 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
Frontend Developer: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,969 ▲223 | 13.64 ▼0.79 | 6.74 ▲4.91 | 41.48 ▼1.11 |
| Dashboard /wp-admin | 2,221 ▲24 | 5.88 ▲0.02 | 102.89 ▼5.02 | 39.84 ▼4.84 |
| Posts /wp-admin/edit.php | 2,103 ▲6 | 2.03 ▲0.02 | 35.53 ▼3.79 | 32.24 ▼3.95 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲10 | 23.16 ▲5.40 | 648.97 ▲15.67 | 48.94 ▼1.53 |
| Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.20 ▲0.02 | 93.85 ▼11.99 | 44.86 ▼0.43 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-front-end-developer/functions.php:48
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
4 plugin tags: themer, front end, wordpress, developer
wp-front-end-developer/functions.php 92% from 13 tests
The main PHP script in "Frontend Developer" version 2.1 is automatically included on every request by WordPress
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 ("wp-front-end-developer.php" instead of "functions.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin96 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 1 | 17 | 17 | 61 |
| PHP | 1 | 6 | 42 | 23 |
| JavaScript | 1 | 6 | 5 | 12 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.10 |
| 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 | 3 | |
| ▷ Named functions | 3 | 100.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
3 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/mobile.png | 1.07KB | 0.21KB | ▼ 79.87% |
| img/tablet.png | 1.03KB | 0.18KB | ▼ 82.70% |
| img/screen.png | 0.97KB | 0.12KB | ▼ 87.65% |