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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.14ms] Passed 4 tests
Server-side resources used by PDF Invoicing for WooCommerce
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.29 ▼7.47 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 45.16 ▼5.76 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.23 ▲0.53 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.55 ▼3.85 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.81 ▲2.56 |
Server storage [IO: ▲4.33MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 127 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for PDF Invoicing for WooCommerce
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.29 ▼1.14 | 1.80 ▼0.20 | 42.05 ▼1.72 |
| Dashboard /wp-admin | 2,206 ▲20 | 5.85 ▲0.88 | 110.73 ▼9.42 | 36.35 ▼11.00 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.10 ▲0.11 | 40.44 ▲4.05 | 35.42 ▲2.91 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.55 ▲0.43 | 589.01 ▼75.05 | 50.16 ▼7.98 |
| Media Library /wp-admin/upload.php | 1,391 ▼0 | 4.18 ▼0.09 | 94.21 ▼13.38 | 41.04 ▼7.71 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
Smoke tests 50% 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 everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/tcpdf/tools/tcpdf_addfont.php
- 33× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'setasign\\Fpdi\\PdfParser\\Filter\\FilterInterface' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Filter/AsciiHex.php:16
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\FpdiException' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfReader/PdfReaderException.php:18
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Type\\PdfType' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Type/PdfDictionary.php:20
- > PHP Fatal error
Uncaught Error: Class 'tFPDF' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/Tfpdf/FpdfTpl.php:20
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\PdfParserException' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/CrossReference/CrossReferenceException.php:18
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\FpdfTpl' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/Fpdi.php:23
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Type\\PdfType' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Type/PdfStream.php:27
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Type\\PdfType' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Type/PdfArray.php:21
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Filter\\FilterException' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Filter/LzwException.php:16
- > PHP Fatal error
Uncaught Error: Class 'setasign\\Fpdi\\PdfParser\\Filter\\FilterException' not found in wp-content/plugins/pdf-invoicing-for-woocommerce/assets/lib/fpdi/src/PdfParser/Filter/Ascii85Exception.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 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
6 plugin tags: pdf, woocommerce, credit note, packing list, woo commerce...
pdf-invoicing-for-woocommerce/pdf-invoicing-for-woocommerce.php Passed 13 tests
The main file in "PDF Invoicing for WooCommerce" v. 2.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
32 characters long description:
Add PDF invoices to WooCommerce.
Code Analysis 95% from 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
No dangerous file extensions were detected52,635 lines of code in 109 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 104 | 2,637 | 15,014 | 52,366 |
| Markdown | 3 | 49 | 0 | 171 |
| JSON | 2 | 0 | 0 | 98 |
PHP code 0% from 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
It is recommended to fix the following
- Cyclomatic complexity of classes should be reduced to less than 1000 (currently 4,413)
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 502)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.45 |
| Average class complexity | 100.60 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 4,413.00 |
| Average method complexity | 8.51 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 502.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 9 | |
| Interfaces | 2 | |
| Traits | 2 | |
| Classes | 69 | |
| ▷ Abstract classes | 2 | 2.90% |
| ▷ Concrete classes | 67 | 97.10% |
| ▷ Final classes | 1 | 1.49% |
| Methods | 972 | |
| ▷ Static methods | 150 | 15.43% |
| ▷ Public methods | 656 | 67.49% |
| ▷ Protected methods | 315 | 32.41% |
| ▷ Private methods | 1 | 0.10% |
| Functions | 12 | |
| ▷ Named functions | 7 | 58.33% |
| ▷ Anonymous functions | 5 | 41.67% |
| Constants | 176 | |
| ▷ Global constants | 139 | 78.98% |
| ▷ Class constants | 37 | 21.02% |
| ▷ Public constants | 37 | 100.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
No PNG images were found in this plugin