Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼6.95ms] Passed 4 tests
Analyzing server-side resources used by Block for Apple Maps
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 37.31 ▼7.11 |
Dashboard /wp-admin | 3.34 ▼0.00 | 46.94 ▼13.88 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 48.57 ▲3.27 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 82.60 ▼10.08 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 51.78 ▲19.48 |
Block for Apple Maps /wp-admin/options-general.php?page=block-for-apple-maps | 3.24 | 35.65 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 19 new files
Database: no new tables, 9 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
maps_block_apple_team_id |
widget_recent-comments |
theysaidso_admin_options |
maps_block_apple_key_id |
maps_block_apple_private_key |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Block for Apple Maps
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,794 ▲58 | 14.14 ▼0.26 | 1.72 ▲0.08 | 39.51 ▼4.19 |
Dashboard /wp-admin | 2,193 ▲13 | 5.51 ▼0.14 | 98.35 ▼1.75 | 43.76 ▲0.29 |
Posts /wp-admin/edit.php | 2,101 ▲1 | 1.97 ▲0.02 | 38.87 ▼0.64 | 35.53 ▼1.06 |
Add New Post /wp-admin/post-new.php | 6,375 ▲4,849 | 29.69 ▲6.54 | 877.06 ▲157.97 | 37.10 ▼20.60 |
Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.21 ▲0.07 | 106.91 ▲3.48 | 68.88 ▲21.33 |
Block for Apple Maps /wp-admin/options-general.php?page=block-for-apple-maps | 979 | 3.16 | 65.83 | 39.34 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options were found after uninstall: 9 options
- widget_recent-comments
- maps_block_apple_key_id
- maps_block_apple_team_id
- maps_block_apple_private_key
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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 fix the following
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function tenup\\Maps_Block_Apple\\add_action() in wp-content/plugins/maps-block-apple/includes/block-assets.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function tenup\\Maps_Block_Apple\\add_action() in wp-content/plugins/maps-block-apple/includes/rest-routes.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function tenup\\Maps_Block_Apple\\plugin_dir_url() in wp-content/plugins/maps-block-apple/maps-block-apple.php:22
- > 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)
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
3 plugin tags: apple maps, block, map block
maps-block-apple/maps-block-apple.php Passed 13 tests
"Block for Apple Maps" version 1.1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
63 characters long description:
An Apple Maps block for the WordPress block editor (Gutenberg).
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 detected655 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 10 | 97 | 211 | 482 |
JSON | 1 | 1 | 0 | 94 |
CSS | 2 | 15 | 0 | 62 |
Bourne Shell | 1 | 5 | 4 | 13 |
JavaScript | 3 | 0 | 0 | 3 |
SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
Average class complexity | 14.00 |
▷ Minimum class complexity | 14.00 |
▷ Maximum class complexity | 14.00 |
Average method complexity | 2.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 22 | |
▷ Named functions | 21 | 95.45% |
▷ Anonymous functions | 1 | 4.55% |
Constants | 6 | |
▷ Global constants | 6 | 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
There were not PNG files found in your plugin