Does WP Travel work with WordPress 6.0.2 and PHP 7.4.8? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 839.62 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.237 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.0.2 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 6,000+ |
WordPress.org page | https://wordpress.org/plugins/wp-travel/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-travel%2Fwp-travel.php&plugin_status=all&paged=1&s&_wpnonce=01bab35ddb |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.740 s |
Memory usage | 4.46 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.034 s |
Memory usage | 4.55 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=wp-travel-coupons |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.699 s |
Memory usage | 4.55 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-enquiries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.079 s |
Memory usage | 4.58 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=tour-extras |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.621 s |
Memory usage | 4.55 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking&page=download_upsell_page |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.750 s |
Memory usage | 4.46 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking&page=booking_chart |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.819 s |
Memory usage | 4.46 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking&page=wp_travel_custom_filters_page |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.667 s |
Memory usage | 4.46 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking&page=settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.826 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itinerary-booking&page=wp-travel-marketplace |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.868 s |
Memory usage | 4.46 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.735 s |
Memory usage | 4.58 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php?post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.163 s |
Memory usage | 4.6 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=itinerary_pricing_category&post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.653 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=itinerary_types&post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.766 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=travel_locations&post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.571 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=travel_keywords&post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.596 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit-tags.php?taxonomy=activity&post_type=itineraries |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.596 s |
Memory usage | 4.49 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.629 s |
Memory usage | 4.2 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/widgets.php |
---|---|
Aspect | new-sidebar-widgets |
HTTP status | 200 |
Load time | 2.266 s |
Memory usage | 6.66 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.358 s | 0.763 s | +0.405 s | 3.72 MiB | 4.48 MiB | + 777.09 KiB |
/wp-admin/edit.php | 0.204 s | 0.494 s | +0.290 s | 3.76 MiB | 4.53 MiB | + 794.73 KiB |
/wp-admin/post-new.php | 0.996 s | 1.200 s | +0.204 s | 5.55 MiB | 6.7 MiB | + 1.15 MiB |
/wp-admin/upload.php | 0.455 s | 0.687 s | +0.232 s | 3.69 MiB | 4.44 MiB | + 776.31 KiB |
/wp-admin/options-writing.php | 0.173 s | 0.473 s | +0.300 s | 3.62 MiB | 4.42 MiB | + 821.96 KiB |
/wp-admin/media-new.php | 0.439 s | 0.422 s | -0.017 s | 3.66 MiB | 4.42 MiB | + 777.29 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.198 s | 0.754 s | +0.556 s | 3.69 MiB | 4.45 MiB | + 776.95 KiB |
/wp-admin/post-new.php?post_type=page | 1.037 s | 1.007 s | -0.030 s | 5.54 MiB | 6.69 MiB | + 1.15 MiB |
/wp-admin/options-discussion.php | 0.219 s | 0.486 s | +0.267 s | 3.6 MiB | 4.36 MiB | + 778.54 KiB |
/wp-admin/edit-comments.php | 0.231 s | 0.459 s | +0.228 s | 3.7 MiB | 4.45 MiB | + 774.37 KiB |
/ | 0.276 s | 0.443 s | +0.167 s | 3.6 MiB | 4.2 MiB | + 606.38 KiB |
Average | 0.417 s | 0.653 s | +0.237 s | 4.01 MiB | 4.83 MiB | + 839.62 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
PHP | 41.1% | 34,197 | 8,391 | 232 | |
JavaScript | 39.7% | 32,973 | 6,709 | 61 | |
CSS | 8.4% | 7,000 | 137 | 32 | |
PO File | 5.3% | 4,412 | 2,896 | 1 | |
SVG | 5.2% | 4,311 | 3 | 11 | |
Markdown | 0.2% | 135 | 0 | 1 | |
XML | 0.1% | 89 | 0 | 2 | |
Sass | 0.0% | 6 | 0 | 1 | |
Total | 83,123 | 18,136 | 341 |
Lines of code | 31,637 |
---|---|
Total complexity | 6,334 |
Median class complexity | 15.0 |
Median method complexity | 2.0 |
Most complex class | WpTravel_Helpers_Trips |
Most complex function | wptravel_get_booking_data() |
Classes | 128 |
---|---|
Methods | 627 |
Functions | 648 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
wp_options
16ID | Name |
---|---|
itinerary-booking | Bookings |
itineraries | Trips |
wp-travel-payment | Payments |
wp-travel-coupons | Coupons |
itinerary-enquiries | Enquiries |
tour-extras | Trip Extras |
ID | Name |
---|---|
wp_travel_search | WP Travel Search (Deprecated) |
wp_travel_featured | WP Travel Featured Trip (Deprecated) |
wp_travel_location | WP Travel Trips by Location (Deprecated) |
wp_travel_trip_type | WP Travel Trips by Type (Deprecated) |
wp_travel_sale_itineraries | WP Travel Sales Widget (Deprecated) |
wp_travel_trip_enquiry_form_widget | WP Travel Enquiry Form Widget (Deprecated) |
wp_travel_filter_search_widget | WP Travel Filters Widget (Deprecated) |
{
"itinerary-enquiries": {
"wp-travel-enquiries-info": {
"title": "Enquiry Details View All enquiries",
"context": "normal"
}
},
"wp-travel-coupons": {
"wp-travel-coupons-detail": {
"title": "Coupon Options",
"context": "normal"
}
},
"itinerary-booking": {
"wp-travel-itinerary-payment-detail": {
"title": "Payment Detail",
"context": "normal"
},
"wp-travel-booking-info": {
"title": "Booking Detail View All Bookings",
"context": "normal"
},
"wp-travel-itinerary-single-payment-detail": {
"title": "Payment Info",
"context": "side"
}
},
"tour-extras": {
"tour-extras-detail": {
"title": "Trip Extras",
"context": "normal"
}
},
"itineraries": {
"wp-travel-trip-options": {
"title": "Trip Options",
"context": "advanced"
}
}
}
ID | Name |
---|---|
wp-travel-customer | WP Travel Customer |
The log file is empty.