PHP in 2026 — Trends, Performance, Ecosystem, and Security

PHP in 2026 — Trends, Performance, Ecosystem, and Security

Verified Sources
Jun 24, 2026

PHP in 2026 is a language at a fascinating inflection point. Celebrating its 30th anniversary in 2025, PHP continues to power approximately 70.8% of all websites with a detectable server-side language according to W3Techs as of June 2026. Yet, paradoxically, it ranks 18th on the TIOBE Index (down from 15th in January 2025), signaling a deep disconnect between actual web infrastructure and perceived "hype" popularity. This research brief explores the full spectrum of PHP's current state: from runtime breakthroughs like JIT and therise of FrankenPHP, through the framework ecosystem dominated by Laravel, to the tooling, security posture, and enterprise deployment patterns that define PHP in 2026.

The narrative that "PHP is dead" has persisted for over a decade, yet the data tells a different story: PHP 8.5 shipped with the pipe operator and a native URI extension, PHP 8.6 is confirmed with Partial Function Application (PFA), 89% of the Packagist ecosystem has adopted PHP 8.x, and the PHP Foundation now boasts 536+ sponsors2. PHP is not dying — it is quietly modernizing from within.

Footnotes

  1. W3Techs Usage Statistics of Server-side Programming Languages - PHP at 70.8% as of June 2026, historical trend data.

  2. StatisticsTimes Top Computer Languages 2026 - TIOBE Index rank #18 for PHP at 1.23%, PYPL rank #7 at 3.35%.

  3. State of PHP 2026 — Dev Newsletter - FrankenPHP benchmarks, PHP Foundation support, PHP 8.5 features, 89% PHP 8.x adoption.

  4. PHP Foundation 2025 Thank You Blog - 536+ sponsors, Executive Director transition, Foundation milestones.

PHP in 2026 is so good — Nuno Maduro

1. Language Adoption & Market Position

PHP's web dominance remains staggering but shows a slow downward trend. W3Techs historical data shows PHP declining from 74.2% in June 2025 to 70.9% by mid-June 2026 — a drop of roughly 3.3 percentage points in 12 months. Meanwhile, JavaScript (Node.js server-side) grew from 4.5% to 6.6%, and Ruby from 6.2% to 6.9% over the same period. This erosion reflects the broader industry shift toward JavaScript-centric full-stack development and microservices architectures.

MetricValueSource
Websites using PHP (server-side)70.9%W3Techs, June 2026
PHP 8.x adoption (websites)61.0% of PHP sitesW3Techs
PHP 7.x still running30.7% of PHP sitesW3Techs
PHP 5.x still running8.2% of PHP sitesW3Techs
TIOBE Index rank#18 (1.23%)TIOBE, 2026
PYPL rank#7 (3.35%)PYPL, 2026
Packagist PHP 8.x adoption89%Dev Newsletter
PHP Foundation sponsors536+PHP Foundation

The gap between TIOBE/PYPL rankings and actual web usage is critical: TIOBE measures search engine visibility (blog posts, tutorials, discussions), while W3Techs measures deployed production systems. PHP's legacy footprint ensures its continued dominance in deployment even as new projects increasingly select alternative stacks.

Footnotes

  1. W3Techs Usage Statistics of Server-side Programming Languages - PHP at 70.8% as of June 2026, historical trend data. 2 3 4 5

  2. W3Techs Historical Trends in Server-side Languages - Monthly trend data June 2025–June 2026 showing PHP decline and JS/Ruby growth.

  3. StatisticsTimes Top Computer Languages 2026 - TIOBE Index rank #18 for PHP at 1.23%, PYPL rank #7 at 3.35%. 2

  4. State of PHP 2026 — Dev Newsletter - FrankenPHP benchmarks, PHP Foundation support, PHP 8.5 features, 89% PHP 8.x adoption.

  5. PHP Foundation 2025 Thank You Blog - 536+ sponsors, Executive Director transition, Foundation milestones.

PHP Evolution: From 7.4 to 8.6

PHP 7.4

Nov 2019

Typed properties, Arrow functions, Null coalescing assignment, FFI. The last 7.x release before the modern era."

PHP 8.0

Nov 2020

JIT compiler introduced, Union types, Match expression, Attributes, Named arguments, Nullsafe operator. The biggest leap in PHP's modern history."

PHP 8.1

Nov 2021

Enums, Fibers, Readonly properties, First-class callables, Intersection types. Fibers enable cooperative multitasking."

PHP 8.2

Nov 2022

Readonly classes, Disjunctive normal form types, Random extension. EOL scheduled for December 31, 2026."

PHP 8.3

Nov 2023

Typed class constants, Dynamic class constant fetch, #[Override] attribute, Deep cloning of readonly properties. 64% Packagist adoption by 2025."

PHP 8.4

Nov 2024

Property hooks, Asymmetric visibility, HTML5 parsing, new array_find/array_all/array_none. Recommended production version in 2026."

PHP 8.5

Nov 2025

Pipe operator (|>), Clone with modifications, native URI extension, array_first/array_last, Fatal error backtraces, closures in attributes."

PHP 8.6 (Expected)

Nov 2026

Partial function application (PFA) confirmed, ? placeholder syntax, variadic ... placeholder. Enabling proper functional composition with pipe operator."

2. Runtime & Performance: JIT, OPCache, and FrankenPHP

The PHP runtime has undergone a transformative shift since PHP 8.0 introduced the JIT compiler. However, real-world JIT gains vary dramatically by workload type. PHPBenchLab's 2026 benchmarks reveal a stark pattern:

Workload TypeJIT Gain (PHP 8.5)Notes
Symfony apps~95%Dramatic improvement in framework-heavy code
Laravel apps~82%Significant but slightly less than Symfony
WordPress<1%I/O-bound, minimal CPU-heavy paths
CPU micro-benchmarks~61%Pure computation sees major gains

OPCache Deep Dive

OPCache remains the single most impactful performance optimization for PHP applications. Key tuning parameters in 2026 include:

  • opcache.memory_consumption: Must exceed total compiled script size. Undersizing causes cache evictions and performance degradation.
  • opcache.max_accelerated_files: Should accommodate all project + vendor files. Laravel projects commonly exceed 10,000 files.
  • opcache.validate_timestamps: Set to 0 in production with manual cache clearing on deploy to eliminate stat calls.
  • opcache.jit_buffer_size: Allocate sufficient JIT buffer (typically 64M–256M depending on codebase size).
  • opcache.jit: Enable with 1255 (tracing JIT, all functions) or 1235 for selective optimization.

FrankenPHP: The Game-Changing Runtime

FrankenPHP gained official PHP Foundation support in 2025 and has emerged as the most significant PHP runtime innovation in years. Its worker mode eliminates the traditional PHP-FPM bootstrapping cost by keeping the application kernel in memory:

RuntimeRequests/secRelative Performance
FrankenPHP (worker mode)~15,000 req/s3.5× baseline
PHP-FPM~4,000 req/s1× baseline
FrankenPHP (classic mode)~6,900–18,400 req/sComparable to FPM

FrankenPHP benchmarks show 80% response time reduction in worker mode, native HTTP/2 and HTTP/3 support, automatic HTTPS via Caddy, and the ability to compile PHP applications into standalone static binaries for simplified deployment. However, classic (non-worker) mode shows parity with PHP-FPM — the gains are architecture-specific.

Footnotes

  1. PHPBenchLab — PHP Performance Benchmarks - JIT benchmark data: 95% gains Symfony, 82% Laravel, <1% WordPress; PHP 8.5 vs Node.js vs Go vs Python.

  2. State of PHP 2026 — Dev Newsletter - FrankenPHP benchmarks, PHP Foundation support, PHP 8.5 features, 89% PHP 8.x adoption. 2

Optimizing PHP 8.5 Performance: A Production Playbook

  1. 1
    Step 1

    Define clear SLOs (e.g., p95 latency < 150ms). Use tools like PHPBench or wrk to measure current request throughput and response times. Record PHP-FPM pool stats, OPCache hit rates, and memory usage. Version your benchmarks.

  2. 2
    Step 2

    Set opcache.enable=1, opcache.memory_consumption=512 (or higher based on codebase), opcache.max_accelerated_files=20000, opcache.validate_timestamps=0 in production, opcache.jit_buffer_size=128M, and opcache.jit=1255. Verify hit rate > 99% via opcache_get_status().

  3. 3
    Step 3

    Enable JIT with opcache.jit=1255 (tracing JIT for all functions) for Laravel/Symfony applications. For I/O-bound WordPress deployments, opcache.jit=1235 (selective) or even off may be preferred, as JIT adds overhead without meaningful gains in I/O-bound workloads.

  4. 4
    Step 4

    Pilot FrankenPHP in staging. Benchmark against existing PHP-FPM setup with realistic traffic patterns (not just hello-world). Confirm compatibility with your framework — Laravel and Symfony have official integrations. Test state leaks across requests (static variables, service containers). Plan for zero-downtime worker restarts.

  5. 5
    Step 5

    Run composer dump-autoload --optimize in production (class map generation). Use --classmap-authoritative if no classes are generated at runtime. Remove unused dependencies with composer unused. Profile autoloading overhead with Xdebug or Blackfire.

  6. 6
    Step 6

    Implement APCu for in-memory object caching. Use Redis for session clustering and distributed caching. Consider varnish for full-page caching on high-traffic content sites. Database query caching with proper TTL management.

PHP Framework Adoption in 2026

Usage share among professional PHP developers (JetBrains State of PHP 2025)

3. The Framework Ecosystem: Laravel, Symfony, Yii, and Beyond

The PHP framework landscape in 2026 shows Laravel's undisputed dominance at 64% adoption among professional PHP developers, followed by WordPress (25%, reflecting legacy CMS usage) and Symfony at 23%. No major shifts in framework adoption occurred between 2024–2026, indicating ecosystem maturity.

Laravel: The De Facto Standard

Laravel 12 is the current stable release, with Laravel 13 expected in early 2026 bringing enhanced cloud support and performance improvements. Laravel's ecosystem expansion in 2025–2026 includes:

  • Laravel Cloud: A first-party hosting/deployment platform reducing infrastructure complexity.
  • Laravel Boost and MCP: AI-powered integrations for code generation and the Model Context Protocol.
  • First-party packages: Forge, Vapor (serverless), Nova, Livewire, Inertia.js integrations.

Taylor Otwell, Laravel's creator, emphasized: "Laravel remains focused on providing a comprehensive, modern full-stack solution that makes PHP development more productive and accessible than ever."

Symfony: The Enterprise Foundation

Symfony occupies a distinct niche: enterprise-grade, component-driven architecture. Its reusable components form the backbone of Laravel and countless other projects. In 2026, Symfony remains the choice for complex, long-lived enterprise systems requiring:

  • Strict coding standards and backwards-compatibility guarantees
  • Reusable bundles for modular functionality
  • Twig templating for clean separation of concerns
  • Deep integration with the PHP Foundation's AI SDK initiative (MCP collaboration with Anthropic)

Yii 3: The Performance Contender

Yii 3 has officially replaced Yii 2, targeting high-performance applications like e-commerce and real-time data processing2. Key improvements include modern PHP 8.x feature usage, improved security tooling, and a continued focus on the Gii code generator for rapid scaffolding. Yii 3's performance optimization and security features keep it relevant for domains where raw throughput matters.

Footnotes

  1. JetBrains State of PHP 2025 - Laravel 64%, WordPress 25%, Symfony 23% adoption among PHP developers. 2

  2. Cloudways Best PHP Frameworks 2026 - Laravel 12/13, Yii 3 replacing Yii 2, framework comparison. 2

  3. team.blue Becomes PHP Foundation Gold Sponsor - PHP Foundation milestones: security audit, PIE, FrankenPHP integration, MCP SDK with Anthropic. 2

  4. Devabit PHP Framework Popularity 2025–2026 - Yii 3 high-performance positioning, framework market share analysis. 2

Best for: Rapid application development, SaaS products, APIs, content platforms.

Strengths: Developer experience, massive ecosystem (40K+ packages), built-in auth/ORM/queue/broadcasting, active community, Laravel Cloud.

Weaknesses: Opinionated architecture, heavier footprint than microframeworks, vendor lock-in to first-party ecosystem.

2026 Version: Laravel 12 (stable), Laravel 13 (upcoming)

4. Tooling: Composer, Packagist, and the Dependency Ecosystem

PHP's dependency management architecture centers on Composer and Packagist, the package repository. As of 2026, Packagist hosts over 422,860 packages, with 20,109 new projects added since January 2025. The ecosystem is mature, but dependency management remains the third-largest challenge for PHP development teams according to the 2025 PHP Landscape Report.

Composer 2.9: Security Hardening

Composer 2.9 (released 2025) introduced significant security features funded by Private Packagist subscriptions, including supply chain security improvements. Critically, Composer 2.9.6 (April 2026) patched two command injection vulnerabilities in the Perforce driver (CVE-2026-40261 and CVE-2026-40176) — teams must update immediately.

Packagist Transparency Log

A major 2025 initiative introduced a transparency log for Packagist.org, enabling audit of package publication events. This mirrors the broader industry trend toward SBOM tracking and supply chain integrity, particularly relevant after the xz/liblzma backdoor incident of 2024.

PHP Version Adoption in the Packagist Ecosystem

The Packagist ecosystem shows strong modern version adoption. The top 1,000 most popular packages increasingly require PHP 8.1+ as their minimum version, steadily pushing the ecosystem forward. The Zend 2025 Landscape Report found 71.18% of survey participants deploying PHP 8.x, with PHP 8.3 leading at 63.99% adoption. Notably, EOL PHP deployments dropped from over 50% in 2024 to approximately 38% in 2025.

Footnotes

  1. Reddit: Comprehensive Packagist.org Analysis - 422,860 packages on Packagist, 20,109 new since Jan 2025.

  2. Zend PHP Dependency Management Guide - Dependency management is the 3rd largest challenge for PHP developers (2025 Landscape Report).

  3. Packagist.org News - Composer 2.9.6 security fixes (CVE-2026-40261, CVE-2026-40176), Transparency Log initiative. 2 3

  4. Stitcher.io PHP Version Stats June 2025 - Packagist ecosystem PHP version adoption, top 1000 packages minimum version analysis.

  5. Zend 2026 PHP Migration Trends - 71.18% PHP 8.x, 63.99% on PHP 8.3, EOL deployments dropping from 50% to 38%. 2

EOL PHP Versions Remain a Major Risk

PHP 8.2 reaches end-of-life on December 31, 2026. PHP 8.1 already reached EOL on December 31, 2025. PHP 7.4 has been EOL since November 2022 and is vulnerable to actively exploited CVEs including CVE-2024-4577 (CVSS 9.8). Running EOL PHP violates compliance requirements for SOC 2, PCI DSS, HIPAA, ISO 27001, and the EU Cyber Resilience Act. Approximately 30.7% of PHP websites still run PHP 7.x — that's millions of vulnerable endpoints.

Footnotes

  1. HeroDevs PHP End-of-Life Dates - EOL timelines, compliance implications, CVE-2024-4577 details.

Pro Tip: Authoritative Autoloader in Production

Always run composer dump-autoload --classmap-authoritative in production. This tells Composer that the class map is the sole source of truth, eliminating filesystem lookups entirely. Combined with opcache.validate_timestamps=0, this eliminates all file stat calls on each request. For projects that generate classes at runtime (e.g., Doctrine proxies), use --optimize instead and warm your proxy cache during deployment.

5. Security Posture in 2026

PHP's security landscape is improving but remains a critical concern. Year-over-year data shows a significant decline in average CVE severity, from 8.28 in 2022 to 7.03 in 2024, 4.98 in 2025, and 4.75 (projected) in 2026.

YearCVEs PublishedAverage CVSS Score
2019307.61
2020156.13
202166.05
202298.28
202377.09
2024187.03
2025154.98
202614 (YTD)4.75

Key 2026 CVE Examples:

  • CVE-2026-7568: Integer overflow in metaphone() causing DoS (PHP 8.x before 8.2.31/8.3.31/8.4.21/8.5.6)
  • PDO Firebird SQL Injection: NUL byte handling in PDO Firebird driver allows SQL injection via PDO::quote() (PHP < 8.2.31/8.3.31/8.4.21/8.5.6)
  • Composer CVE-2026-40261/40176: Command injection in Perforce driver affecting Composer 2.9.5 and earlier

The PHP Foundation's first security audit of PHP core in over a decade (completed 2025) is a landmark investment in proactive security.

Footnotes

  1. Stack.watch PHP Security Vulnerabilities in 2026 - CVE count and severity data 2019–2026, specific 2026 CVE details. 2 3

  2. Packagist.org News - Composer 2.9.6 security fixes (CVE-2026-40261, CVE-2026-40176), Transparency Log initiative.

  3. team.blue Becomes PHP Foundation Gold Sponsor - PHP Foundation milestones: security audit, PIE, FrankenPHP integration, MCP SDK with Anthropic.

PHP Security Hardening Checklist for 2026

  1. 1
    Step 1

    Audit all PHP installations. Upgrade PHP 7.x and 8.1+ to 8.4+ immediately. For PHP 8.2, plan migration before December 31, 2026 EOL. Use commercial extended support (e.g., Zend, HeroDevs) if immediate upgrade is infeasible.

    Footnotes

    1. HeroDevs PHP End-of-Life Dates - EOL timelines, compliance implications, CVE-2024-4577 details.

  2. 2
    Step 2

    Use CIS-benchmarked, pre-hardened PHP container images (e.g., Zend's hardened images). Nearly 30% of PHP teams still don't use containers — this must change.

    Footnotes

    1. Zend PHP Security Best Practices - Containerization stats (~30% not using containers), security best practices.

  3. 3
    Step 3

    Integrate static analysis (PHPStan, Psalm, Snyk) and dynamic analysis (DAST) tools into your pipeline. Automate security testing on every code change. Use pre-commit hooks for early detection.

  4. 4
    Step 4

    Update to Composer 2.9.6+ immediately (CVE-2026-40261). Run composer audit regularly. Use the Packagist transparency log. Generate SBOMs for your application.

  5. 5
    Step 5

    Deploy FrankenPHP or Caddy for automatic HTTPS with HTTP/3. Enforce HSTS headers. Disable TLS 1.0/1.1. Use certificate pinning for internal service communication.

  6. 6
    Step 6

    For critical enterprise applications, deploy RASP agents that monitor application behavior at runtime to detect and block attacks in real-time, including zero-day exploits.

PHP CVE Count and Average Severity (2019–2026)

Yearly vulnerability count and average CVSS score trend

6. Deployment Practices and Enterprise Adoption

PHP deployment practices in 2026 reflect the broader industry shift toward containerization and cloud-native architectures. The 2025 PHP Landscape Report found that ~70% of PHP teams now use container technologies, while nearly 30% still operate without containers.

Current Deployment Patterns

The dominant PHP deployment architectures in 2026 include:

  1. Docker + Kubernetes (enterprise): Containerized PHP-FPM with Nginx sidecars, orchestrated by Kubernetes. Docker adoption reached 92% among IT professionals in 2025.
  2. FrankenPHP Static Binaries (emerging): Compile PHP applications into single self-contained binaries — eliminating the need for a PHP runtime on the target system. Ideal for edge deployment and simplified distribution.
  3. Serverless / Laravel Vapor (Laravel-specific): AWS Lambda-based PHP execution with auto-scaling, used primarily by Laravel teams for variable workloads.
  4. Traditional LAMP/LEMP (legacy): Still widespread for smaller deployments and WordPress hosting.

The Zend 2026 PHP Landscape Report notes that Services/APIs remain the top application type at 80%, followed by Internal Business Applications (70%) and Content Management (56%). Crucially, teams are moving away from out-of-the-box CMS solutions toward custom-built applications.

Enterprise Adoption Scenarios

ScenarioTypical StackPHP VersionFramework
High-traffic SaaS APIK8s + PHP-FPM/FrankenPHP8.4+Laravel or Symfony
Legacy CMS migrationDocker + PHP-FPM8.2→8.4WordPress → custom
Financial services backendHardened containers + RASP8.4 (LTS)Symfony
E-commerce platformFrankenPHP worker mode8.5Yii 3 / Laravel
Internal business toolsDocker Compose8.3+Laravel
AI-integrated web appsFrankenPHP + MCP SDK8.5+Laravel + MCP

Footnotes

  1. Zend PHP Security Best Practices - Containerization stats (~30% not using containers), security best practices.

  2. Docker 2026: 92% Adoption — Programming Helper - Docker 92% IT professional adoption, 71.1% professional developer adoption.

  3. State of PHP 2026 — Dev Newsletter - FrankenPHP benchmarks, PHP Foundation support, PHP 8.5 features, 89% PHP 8.x adoption.

  4. Zend 2026 PHP Usage Statistics - 80% Services/APIs, 70% Internal Business Apps, shift to custom solutions.

Deep Dive: Key PHP 2026 Topics

PHP Application Types in 2026

Distribution of PHP application categories (Zend 2026 Landscape Report)

7. PHP 8.5 and 8.6: New Language Features

PHP 8.5 (released November 2025) and PHP 8.6 (expected November 2026) represent PHP's continued embrace of functional programming paradigms alongside incremental improvements2.

PHP 8.5 Highlights

The Pipe Operator (|>): The most impactful feature, enabling left-to-right functional composition:

1// Before: nested, right-to-left 2$result = count(array_filter(array_map('strtoupper', $data), 'isValid')); 3 4// After: readable, left-to-right with pipe operator 5$result = $data 6 |> array_map(strtoupper(...), ?) 7 |> array_filter(?, 'isValid') 8 |> count(...);

Other PHP 8.5 features include:

  • array_first() and array_last(): Built-in functions for array edge access
  • Fatal error backtraces: Stack traces on fatal errors for production debugging
  • Closures in attributes: Static closures and first-class callables as attribute parameters
  • #[NoDiscard] attribute: Warnings when return values are ignored
  • Asymmetric visibility for static properties: Granular access control
  • Clone with modifications: clone $obj with {property: value}

PHP 8.6: Partial Function Application

The unanimously accepted PFA RFC introduces ? argument placeholders and ... variadic placeholders:

1// Partial application with ? placeholder 2$addFive = add(?, 5); 3$result = $addFive(3); // returns 8 4 5// With pipe operator 6$numberOfAdmins = getUsers() 7 |> array_filter(?, isAdmin(...)) 8 |> count(...); 9 10// Variadic placeholder 11$sum = array_sum(...);

PFA is the key to making the pipe operator truly useful — without it, multi-argument functions require verbose closure wrappers. The next frontier after PFA is function composition (creating new functions by combining existing ones without immediate execution).

Footnotes

  1. Zend PHP 8.5 Features Guide - Pipe operator details, PFA preview, other PHP 8.5 features. 2

  2. PHP Foundation: PFA in PHP 8.6 - PFA unanimously accepted, ? and ... placeholder syntax, functional composition roadmap. 2

PHP in 2026: Key Concepts

1 / 6
17%
Question · Term

What percentage of websites use PHP as their server-side language?

Click to reveal
Answer · Definition

~70.9% as of June 2026 (W3Techs). Down from 74.2% a year earlier — a slow erosion but still dominant.

8. The PHP Foundation and the Road Ahead

The PHP Foundation, now in its fourth year, has become the institutional backbone ensuring PHP's long-term health. Key developments:

  • 536+ sponsors including major sponsors like team.blue (Gold, starting January 2026), Automattic, Laravel, JetBrains, Zend, and Private Packagist2
  • $183,500+ in total contributions via Open Collective
  • First security audit of PHP core in over a decade (2025)
  • PIE (PHP Installer for Extensions) released — standardizing extension installation
  • FrankenPHP integrated into the official PHP organization (2025)
  • Strategic Anthropic/Symfony collaboration on the MCP SDK, positioning PHP as a first-class language for AI development
  • Dedicated Executive Director position created to manage the Foundation's growing scope

Looking beyond 2026, the PHP ecosystem is tracking several emerging themes:

  1. Functional programming trilogy: First-class callables → Pipe operator → PFA → Function composition (the final piece)
  2. AI-native PHP: The MCP SDK enables PHP applications to act as AI tool servers
  3. Alternative runtimes: FrankenPHP, Swoole, and RoadRunner challenge PHP-FPM's decades-long dominance
  4. Supply chain security: Transparency logs, SBOMs, and audit tools hardening the dependency chain
  5. Serverless PHP: Laravel Vapor and FrankenPHP static binaries making PHP viable in serverless environments

Footnotes

  1. PHP Foundation 2025 Thank You Blog - 536+ sponsors, Executive Director transition, Foundation milestones. 2 3

  2. team.blue Becomes PHP Foundation Gold Sponsor - PHP Foundation milestones: security audit, PIE, FrankenPHP integration, MCP SDK with Anthropic. 2 3 4

  3. PHP Foundation Open Collective - $183,500+ total contributions, sponsorship tiers.

  4. State of PHP 2026 — Dev Newsletter - FrankenPHP benchmarks, PHP Foundation support, PHP 8.5 features, 89% PHP 8.x adoption.

Knowledge Check

Question 1 of 5
Q1Single choice

As of mid-2026, approximately what percentage of websites with a known server-side language use PHP?