New to Pressable? Get up to 6 months of free hosting on Premium plans this holiday season. Ends Nov 30. Get the offer

Using APM Insights to Troubleshoot Performance Issues

Last modified: November 20, 2026

Ask Your Favorite AI

Copy the link to a markdown format of this article for ChatGPT, Claude, Gemini, or your favorite AI.

APM Insights (Application Performance Monitoring) is a powerful diagnostic tool in the Pressable control panel. It records how your site handles PHP requests, so you can find the slow plugins, database queries, or theme functions behind a performance problem.

APM comes in two versions. Standard is the default for every site. New adds a more detailed trace viewer and keeps traces for 30 days, and requires PHP 8.3 or later. You can switch a site between them at any time while APM isn’t recording.

Where to find APM Insights

  1. Log in to the MyPressable control panel and go to Sites.
  2. Select your site, then select Performance in the left menu.
  3. Under Tools & Monitoring, find the Application Performance Monitoring (APM) row.

The row shows whether APM is Active or Inactive. It also has two buttons:

  • Dashboard opens the trace viewer for traces you’ve already captured. It only appears once the viewer is available for your site.
  • Manage opens the APM window, where you start and stop recording, choose the APM version, and copy a shareable link.

If the site uses the new version, the row shows a New (Beta) badge next to its title.

Choosing an APM version

Every site starts on Standard. The New version records the same kind of traces, but its viewer goes deeper: you can open a request as a flame graph or waterfall, see its database queries and external requests, and download the trace.

Before you switch, keep these in mind:

  • PHP 8.3 or later is required for the new version. On older PHP versions, New is grayed out, with a link to change your PHP version. Switching back to Standard works on any PHP version.
  • You can’t switch while APM is recording. Stop the recording first.
  • Each version keeps its own traces. Traces captured on one version don’t appear in the other version’s viewer.
  • If you lower PHP below 8.3 later, the new version stops working, and the APM row tells you to switch back to Standard in Manage.

To switch versions:

  1. On the Performance page, click Manage in the APM row.
  2. Under APM version, select Standard or New.
  3. Click Update APM Version. A message confirms the change, for example “APM version set to Standard.”
Screenshot showing a close up of the APM version section of the settings overlay, with the "New" version selected

Every switch is recorded in your site’s Activity Logs, as “APM version set to New (Beta)” or “APM version set to Standard.”

Screenshot showing activity log entries for APM version updates.

You can also check and change the version through the Pressable API (see Get APM Version and Set APM Version) or with the get_site_apm_version and set_site_apm_version tools in the Pressable MCP server.

Activating APM monitoring

APM records traces only for a set period, then stops on its own. To start recording:

  1. On the Performance page, click Manage in the APM row.
  2. Choose a duration: 5 minutes, 10 minutes, or 30 minutes (not recommended).
  3. Click Activate Monitoring.

While APM is recording, the row shows Active and the time recording stops, for example “Stops recording at 2:15 PM UTC on Nov 20.”

Screenshot showing APM section of Performance page in MyPressable, with monitoring active and a "Stops recording at..." date visible.

To stop early, click Manage, then Deactivate.

For useful results, keep sessions short (5 minutes is usually enough, and under 10 minutes is best) and reproduce the problem while APM records. For example, load the slow page or complete a test checkout.

Bulk Activate APM on sites

With Bulk Operations, you can turn APM recording on or off for several sites at once. Turning it on records for 30 minutes on each site; turning it off stops recording right away. Each site records with the APM version it’s already set to (Bulk Operations doesn’t change versions). Inactive sites, and sites already in the selected state, are skipped. Site content and backups aren’t affected.

Viewing and sharing traces

Click Dashboard in the APM row to open the trace viewer in a new tab. You don’t need to be recording to open it, so you can review traces after a session ends.

The dashboard lists each captured request with its timestamp and duration. Click a trace to open its details.

To share traces with a developer or collaborator, click Manage, then Copy APM Link at the bottom of the APM window. The link is temporary, so share it soon after you copy it.

Dashboard and Copy APM Link always open the viewer for the version your site is set to. After switching versions, traces from the other version won’t show there.

Screenshot of the APM trace list when using the Standard option
Standard APM traces
Screenshot of the APM trace list when using the New option
New APM traces

Understanding APM traces

Each trace represents one PHP request and breaks down how WordPress handled it. Look for long spans: they show where the time went.

In the Standard viewer, each trace includes:

  • Summary: the request path, duration, timestamp, and status (such as SUCCESS or ERROR).
  • Latency chart: time spent in WordPress core (WP), the database (DB), and Memcache. Memcache is Pressable’s built-in object caching layer, separate from page or edge caching.
  • Spans tab: every function, query, or action in the request. Use the filters to narrow results by span type or duration.

In the new version’s viewer, you can also:

  • Open a request as a flame graph or waterfall, to see which calls ran inside which and in what order.
  • See the request’s database queries and external requests (calls your site made to other services).
  • Download the trace to keep it or share it.

Whatever the viewer, these patterns are worth checking first:

  • Long database spans may point to slow or repeated queries.
  • Long WordPress (wp) spans may point to inefficient PHP code or plugin hooks.
  • Memcache spans should generally be short. Long ones are worth a closer look.

Saving traces

How long traces last depends on the APM version.

  • Standard: trace data is short-lived. Don’t expect it to last beyond the recording session; it may become unavailable once the session ends or after you close the dashboard. When you find something worth investigating, copy the details right away or download using JSONL link on the main trace list page.
  • New: traces are kept for 30 days. To keep a trace longer, or to share it outside the viewer, download it.

Best practices and next steps

  • Keep recording windows short, ideally under 10 minutes.
  • Reproduce the slow action while APM records.
  • On PHP 8.3 or later, consider the new version for its deeper trace detail and 30-day retention.
  • Review the results with your developer, and share traces using Copy APM Link or a downloaded trace.

Related articles: