Configure Performance Settings

WP Travel Engine's Performance settings help your trip pages load faster. Right now, that comes down to one setting: Optimized Loading.

Before you start

You'll need to be logged in to your WordPress admin area with permission to change WP Travel Engine settings.

Opening the performance settings

1. Log in to your WordPress dashboard.
2. On the left-hand menu, click WP Travel Engine, then Settings.
3. Click the Performance tab, then General from the submenu.

What Optimized Loading does

On a single trip page, WP Travel Engine normally loads several separate script and style files: the date picker library, a small state-management library, the WordPress REST API helper, and the trip booking modal script, among others. Each one is a separate file your visitor's browser has to request.

Turn on Optimized Loading and WP Travel Engine swaps those separate files for pre-built bundles instead, packing several of them into one file for the trip booking modal and one for the single trip page. Fewer files means fewer requests, which is the part of a page load that tends to add up on slower connections.

Say a traveler on mobile data opens your Kilimanjaro trek page. With Optimized Loading on, their browser fetches two bundled scripts for that page's interactive pieces instead of several separate ones. That's less back-and-forth before the page is ready to use.

This setting is currently marked Beta. It only affects single trip pages, and it's worth testing on your own site before you rely on it everywhere.

Turning on Optimized Loading

1. On the Performance > General tab, toggle Optimized Loading on.
2. Click Save Changes.

Once saved, WP Travel Engine starts serving the bundled versions of these files on your single trip pages.

Best practices

• Test after enabling. Since this feature is Beta, open a few real trip pages, on both desktop and mobile, and confirm the date picker, booking modal, and any interactive elements still work as expected.
• Watch for theme or plugin conflicts. A theme or plugin that expects one of the individual scripts to be loaded on its own may behave differently once those scripts are bundled. If something looks off after enabling this setting, that's the first place to check.
• Pair it with a caching plugin. Optimized Loading reduces how many files your trip pages load; a caching plugin reduces how often your server has to build those pages from scratch. Used together, they cover different parts of the same problem.