Drupal 11.2.0: Faster Installs, OOP Hooks, AVIF Support, JSON Schema, and PHPUnit 11

Staff Reporter

Priyanka Phukan authored the Specbee blog post discussing Drupal 11.2.0’s backend and frontend performance boosts. The release streamlines module installations with a three to four times speed improvement. Developers can replace legacy module files with object-oriented hook classes. JSON schema support simplifies headless and third-party integrations.

Native AVIF image handling reduces file sizes while preserving image quality. A WebP fallback ensures server compatibility when AVIF is unsupported. Refined render caching reduces backend queries and boosts page rendering. The modern navigation module enhances the admin UI with intuitive controls. PHPUnit 11 support enables updated testing workflows for PHP 8.4.

The post highlights key upgrades but relies on promotional language rather than benchmarks. Actionable guidance, such as enabling AVIF and JSON schema, helps with planning. However, detailed migration steps and performance metrics are missing. Readers should trial these features on a staging environment before upgrading live sites.

Reference: Drupal 11.2.0 is here – here’s why you should take the next step! by Priyanka Phukan, Specbee (15 July 2025)

Drupal 11

Specbee

Performance

Drupal

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.