Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)! drupal 11.3.6 Update released for Drupal core (11.3.6)! drupal 10.6.6 Update released for Drupal core (10.6.6)! cms 2.1.0 Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 Minor update available for module menu_link_attributes (8.x-1.7). leaflet 10.4.5 Minor update available for module leaflet (10.4.5). eca 3.1.1 Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 Minor update available for module ai (1.3.3). ai 1.2.14 Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 Minor update available for module klaro (3.0.10). klaro 3.0.9 Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 Minor update available for module layout_paragraphs (2.1.2).

ara

No security coverage
View on drupal.org

Advanced Render Auditor (ARA) is a site-wide render tree profiler for Drupal. It decorates \Drupal\Core\Render\Renderer to record one entry per rendered element — including render time, database queries, cache keys/tags/contexts, and the tree of inheriting elements for each cache lineitem. While active, it renders a floating results panel at the bottom of every page with a summary bar, filter/threshold controls, color-coded rows, inline cache metadata inspection, and click-through to the originating row for any inherited tag or context. Optionally prepends a small severity-colored badge to each element on the page.

Local development only. This module swaps the core renderer service and instruments every doRender() call while it is active. Never enable it outside of local development. A runtime requirements check surfaces a warning on the Status Report whenever the profiler is enabled.

Requirements

  • Drupal core ^10 || ^11
  • No additional contrib module dependencies

Installation

Install as you would normally install a contributed Drupal module. For further information, see Installing Drupal Modules.

Configuration

  1. Navigate to Administration > People > Permissions and grant Use Advanced Render Auditor profiler to your admin role.
  2. Navigate to Administration > Configuration > Development > Advanced Render Auditor profiler.
  3. Toggle Enable profiler site-wide.
  4. Optionally enable Display annotations and set an Annotation display threshold (milliseconds) to hide fast elements.
  5. Reload any page and the results panel will appear at the bottom.

A render call is profiled only when all of the following are true:

  1. Config ara.settings.enabled is TRUE.
  2. The current user has the use ara profiler permission.

When either fails, ProfilingRenderer::doRender() short-circuits to the parent implementation on the very first line — overhead is one boolean check per render call.

Configuration fields

Field Description enabled Master switch. display_annotations Render severity-colored badges above rendered elements. annotation_threshold_ms Hide annotations below this threshold (rows still appear in the panel).

Troubleshooting

Panel does not appear. Verify the config switch is on and that the current user has the use ara profiler permission. Clear the cache with ddev drush cr after enabling.

Status Report warning. The profiler is enabled. Disable it at /admin/config/development/ara; the warning will clear automatically.

BigPipe-streamed elements missing from the panel. Lazy-builder placeholders that resolve after hook_page_bottom are not captured. Disable BigPipe temporarily to profile those elements.

FAQ

Q: Can I safely leave it enabled in production?

A: No. The decorator instruments every doRender() call and adds significant overhead. The runtime requirements check will warn you on the Status Report whenever the module is enabled.

Maintainers

Supporting this Module

Buy me a hot chocolate :)

Activity

Total releases
2
First release
Apr 2026
Latest release
1 day ago
Release cadence
0 days
Stability
50% stable

Releases

Version Type Release date
1.0.0 Stable Apr 18, 2026
1.0.x-dev Dev Apr 18, 2026