If you have spent any time in developer forums lately, you have heard it: PHP is dead. The reality is very different. PHP still runs about 69% of the websites whose server-side language we can identify, and WordPress alone — which is written entirely in PHP — powers more than 43% of all websites. For Kenyan business owners choosing a stack, the "PHP is dead" conversation is mostly noise. The useful question is not whether PHP is alive; it is whether PHP is the right tool for your specific project.
What the data actually says
W3Techs tracks server-side language usage across millions of websites. As of October 2026, PHP sits at roughly 69.3%. JavaScript is around 8%, Java and Python are each in single digits. PHP runs more of the web than every competing server-side language combined. That gap has been stable for over a decade. It survived Node.js, Ruby on Rails, and the latest wave of full-stack JavaScript frameworks.
Why PHP feels dead but is everywhere
PHP is invisible. It runs on the server, renders HTML, and sends it to the browser. Users never see it. Developers talk about what they build new projects in — Next.js, Go, Rust — but most of the web they actually visit runs on PHP underneath, usually through WordPress. Popularity in developer forums and usage in production are two different metrics.
What PHP looks like in 2026
Modern PHP is not the PHP of 2010. PHP 8.x runs on about 62% of PHP sites and brought real performance gains, stronger type safety, and better tooling. Laravel is the most popular framework, with over 1.5 million live websites and a large ecosystem. Symfony powers large enterprise systems. Composer handles dependencies. PHPStan and Rector support static analysis and automated refactoring. The language is actively maintained.
The real risk: skills and versions
The Zend 2026 PHP Landscape Report flags two issues. First, hiring: fewer new developers are entering the PHP ecosystem, so experienced PHP talent is harder to replace. Second, versions: about 40% of PHP teams still run end-of-life versions, which carry security risk. PHP 7.4, 8.0 and 8.1 no longer receive security fixes. If you inherit a PHP site, version and maintenance matter more than language choice.
What this means for Kenyan businesses
For most Kenyan SMEs, PHP is still the practical default. A WordPress site on affordable hosting gets you online quickly and cheaply. A Laravel application gives you a custom web application with room to grow. Next.js or another JavaScript stack fits interactive dashboards and web apps, but usually costs more to build and host. The right choice depends on what you are building, not on whether PHP is "trendy."
Where Next.js and PHP overlap
Lumyn builds in Next.js because it gives us speed, SEO control, and a modern developer experience. But we do not pretend every client needs a JavaScript stack. A Nairobi salon needs a WordPress site, not a React application. A logistics company needs a Laravel backend, not a static site. Match the stack to the problem.
What to ask before choosing
Who will maintain this after launch? Do you need a content team that can edit pages without a developer? Is the project a brochure site, an application, or an e-commerce store? What is your hosting budget? PHP wins on the first three for most small businesses; JavaScript stacks win on interactive applications.
Build what comes next
Want to explore what these ideas could mean for your business? Start a conversation with our team.