Skip to main content

Recording Details Page

Once you create a recording, you can view its details to get a comprehensive overview of the captured data. This screen provides insights into the number of dependencies found, the static content version recorded, and a history of all optimizations created from this recording. For manual recordings, you can also initiate new optimizations directly from this view.

To view a recording's details, navigate to System > Tools > mageproxy.io and click View next to the recording you want to inspect.

Timeline​

The Timeline provides a graphical log of all captured dependencies during the recording's run. It helps you understand how and when new dependencies were captured over time.

This view is useful for tracking the history of the recording and seeing how it evolved, which can help you plan your recording schedule for the future.

Dependencies​

The Dependencies tab shows a complete list of every JavaScript file that was recorded from your website's traffic. This raw data, including the page handle where each dependency was recorded, is what MageProxy uses to build its optimized bundles.

In this section, you can:

  • Review all captured files: See the name and path of every JavaScript dependency.
  • See where files are used: Identify the page handles where each dependency was loaded.
  • Identify potential issues: Spot any unexpected or unnecessary JavaScript files that are being loaded on your site.
  • Prepare for optimization: Use this list to decide if you need to exclude or remove certain files when you create your next optimization.

Optimizations​

This section lists all optimizations created from the recording. For each optimization, you can see its requested date, deployment date (if applicable), the total number of JavaScript files included (dependency count), and a unique checksum, which MageProxy uses to avoid creating redundant optimizations. You can also see whether an optimization is ready for deployment.

By clicking View on any optimization, you can inspect the exact configuration that was used to create it and save those settings as an Auto Run Template.