Website Statistics for 2027: Speed, PHP and SEO Data Every Site Owner Needs

PHP 8.2 end of life, Core Web Vitals pass rates and AI-summary click data, every number sourced, plus what to fix in 2027.

On 1 January 2027, PHP 8.2 stops getting security fixes. Based on W3Techs data, that will leave roughly 6 in 10 PHP websites on a version of PHP that no longer gets patched.

That is one of three shifts site owners should plan for next year. Fewer than half of mobile sites pass Google's Core Web Vitals, and AI summaries are changing how many people click through from Google at all.

The short answer: in 2027, upgrade PHP to 8.4 or newer, fix loading speed on mobile first, and write pages that answer questions clearly enough to be quoted. Each number below links to its source, and you are welcome to reuse the charts with a link back.

Still on PHP 8.2 or older?

We upgrade PHP on a staging copy first, fix what breaks, then switch live. Fixed price agreed before any work starts.

Get a fixed-price quote WhatsApp us

1. PHP: most sites will be out of support on 1 January 2027

PHP versions in use (% of all PHP websites)
PHP 5.x7.3%PHP 7.x24.6%PHP 8.03.4%PHP 8.18.8%PHP 8.217.4%PHP 8.324.3%PHP 8.49.0%PHP 8.55.1%
Red: no security fixes today. Orange: PHP 8.2, security support ends 31 Dec 2026. Purple: supported in 2027. PHP 8.x splits calculated from W3Techs' PHP 8 breakdown. Source: W3Techs, 19 Nov 2026, W3Techs PHP 8 versions, php.net supported versions.

PHP runs 68.1% of websites whose server-side language is known, according to W3Techs. That includes most WordPress, WooCommerce, Magento and Laravel sites.

PHP gives each version two years of active support and two more years of security fixes, then it is end of life. Here is where the dates fall:

VersionSecurity fixes untilStatus on 1 Jan 2027
PHP 7.4 and olderEnded (7.4: Nov 2022)Unsupported
PHP 8.0Nov 2023Unsupported
PHP 8.131 Dec 2025Unsupported
PHP 8.231 Dec 2026Unsupported
PHP 8.331 Dec 2027Security fixes only
PHP 8.431 Dec 2028Security fixes only
PHP 8.531 Dec 2029Fully supported

Put the two together. Today about 44% of PHP sites run a version with no security fixes: all of PHP 5 and 7, plus 8.0 and 8.1. PHP 8.2 is the single biggest group still on a supported version, at around 17% of all PHP sites. When it drops out, the unsupported share jumps to about 62%.

(How we got there: W3Techs gives the PHP 8 sub-version split as a share of PHP 8 sites. We multiplied it by PHP 8's share of all PHP sites. The chart caption has the links.)

Why this matters: unsupported PHP still runs. Nothing breaks on 1 January. But the next security hole in PHP itself will not be patched for your version, and many hosts start forcing upgrades on their own timetable. We saw this in October 2026 with two critical PHP CVEs: PHP shipped fixes for 8.2 to 8.5, while 8.1 and older got no official fix.

What to do: check your PHP version in your hosting panel, test the upgrade on a staging copy, and fix what breaks. Our guide to common PHP 8 upgrade errors covers the usual ones, and memory limit errors often show up after the switch.

2. Speed: fewer than half of mobile sites pass Core Web Vitals

Websites passing all three Core Web Vitals
32%41%202131%44%202236%48%202344%55%202448%56%2025MobileDesktop
Share of sites with good LCP, INP and CLS for real Chrome users. Source: HTTP Archive Web Almanac 2025, Performance chapter.

Core Web Vitals are Google's three measures of how a page feels to real users: how fast the main content loads (LCP), how quickly the page responds to a tap (INP), and whether things jump around while loading (CLS).

The 2025 Web Almanac from HTTP Archive found that 48% of sites pass all three on mobile and 56% on desktop. That is real progress: mobile was 32% in 2021. But it still means more than half of sites give mobile visitors a slow or jumpy experience.

Share of sites with a good score, per metric (2025)
62%74%LCP (loading)77%97%INP (response)81%72%CLS (stability)MobileDesktop
Loading speed (LCP) on mobile is the metric most sites fail. Source: HTTP Archive Web Almanac 2025.

Splitting by metric shows where the problem is. On mobile, only 62% of sites have good loading speed (LCP), while 77% respond well to taps and 81% stay stable. Desktop shows the opposite weakness: CLS is the worst there, at 72%.

Does speed affect money? A Deloitte study for Google of 37 brands found that a 0.1-second faster mobile site went with 8.4% more conversions on retail sites and 9.2% higher order value. That is a correlation across many sessions, not a guarantee, but it points the same way as every other speed study.

What to do: look at your site's real-user data in Search Console's Core Web Vitals report or PageSpeed Insights, start with LCP on mobile, and fix the biggest image or the slowest server response first. If Search Console also shows redirect problems, our redirect errors guide helps.

Failing Core Web Vitals?

We find what slows your site down for real users and fix it, usually starting with LCP on mobile.

Get a fixed-price quote WhatsApp us

3. Search: AI summaries mean fewer clicks for weak pages

8% vs 15%
of Google visits ended in a click on a normal result with vs without an AI summary on the page
1%
of visits with an AI summary led to a click on a link inside the summary
18%
of Google searches in the study (March 2025) showed an AI summary
+8.4%
retail conversions when mobile sites got 0.1s faster (and +9.2% order value)

In March 2025, Pew Research tracked the Google searches of 900 US adults. When an AI summary appeared, people clicked a normal result in 8% of visits, against 15% when there was none. Clicks on the links inside the summary itself were rare, at 1%.

Google disputes how much this matters for publishers. But the direction is clear for small business sites: a page that only repeats general information now competes with an answer at the top of the page.

The pages that still earn clicks are the ones a summary cannot replace: specific prices, local details, real case studies, tools and calculators, and step-by-step fixes for a precise problem. That is also what AI summaries tend to cite.

What to do: for each important page, ask "what does this page know that a summary doesn't?" Add the specifics: numbers, examples, your own photos and process. Keep the page fast, so when someone does click, they stay.

What to do in 2027: the checklist

  1. Upgrade PHP before 31 December 2026. Move to 8.4 if your plugins support it (8.3 is only patched until December 2027). Test on staging first.
  2. Check real-user Core Web Vitals monthly. Lab scores are useful for debugging, but real-user data is what counts in Google's report.
  3. Fix mobile LCP first. Usually that means compressing the hero image, preloading it, and speeding up server response.
  4. Remove what you don't use. Old plugins, tracking scripts and sliders slow pages and add security risk.
  5. Make every key page specific. Prices, local details, case studies and clear steps are what still earn the click.
  6. Keep an update routine. Monthly plugin and theme updates, quarterly PHP and server review.
  7. Measure enquiries, not just traffic. Track form submissions and calls per page.

Skills you need (or need to hire)

SkillWhy it matters in 2027Who usually owns it
PHP upgrades and compatibility fixes8.2 support ends 31 Dec 2026Developer
Reading Core Web Vitals reportsShows what real visitors experienceDeveloper / SEO
Image and front-end optimisationLCP is the most-failed metric on mobileDeveloper
Server and caching setupSlow server response hurts every pageDeveloper / host
Writing specific, useful contentAI summaries absorb generic answersMarketing / owner
Technical SEO basicsRedirects, sitemaps and canonicals keep pages indexedSEO

2025 habits vs 2027 habits

2025 habit2027 habit
PHP version"If it works, don't touch it"Planned upgrade before end of life
SpeedCheck PageSpeed once at launchWatch real-user data every month
ContentLong general articlesSpecific answers, data and examples
PluginsInstall and forgetAudit and remove quarterly
Success metricTrafficEnquiries and sales per page

Common mistakes

  • Switching PHP version on the live site. Always test on a staging copy.
  • Chasing a 100 lab score. Real-user data matters more than a perfect Lighthouse number.
  • Fixing desktop first. Most failing sites fail on mobile LCP.
  • Ignoring old plugins. An abandoned plugin can block a PHP upgrade or become the security hole.
  • Publishing generic content. If a summary can answer it in two lines, few people will click.

An example of how it usually goes

Take a small WooCommerce shop on PHP 7.4 with a slow mobile homepage. The upgrade path is a staging copy, a compatibility scan, plugin updates or replacements, then PHP 8.4. In the same pass you compress and preload the hero image and turn on page caching. For a site like this it is usually days of work, not weeks, and the shop leaves the unsupported group before the deadline instead of after a hack.

FAQ

When does PHP 8.2 reach end of life? Security support ends on 31 December 2026, according to php.net.

What share of websites use PHP? 68.1% of websites whose server-side language is known, per W3Techs on 19 November 2026.

How many websites pass Core Web Vitals? 48% on mobile and 56% on desktop, according to the HTTP Archive Web Almanac 2025.

Do AI summaries reduce clicks from Google? Pew Research found people clicked a normal result in 8% of visits with an AI summary, against 15% without one.

Can I use these charts? Yes. Use them in your article or deck and link to this page as the source.

Get help before the deadline

Hitori Tech upgrades PHP, fixes Core Web Vitals and builds fast websites for businesses in the UK and India. See our PHP security fix service and CRO audit, or send the form below for a fixed-price quote.

Get a fixed-price quote

Tell us what's broken or what you need. We reply within one working day with a price and timeline. No obligation.

Protected by reCAPTCHA. We only use your details to reply to this request.

Sources

Written by

Jyotirmay Gaur