48% of mobile sites pass Core Web Vitals, and that is the good news
In 2026, web development has stable foundations and uneven results: JavaScript, TypeScript, Node.js and React dominate, AI is part of daily coding, yet most sites still fall short on speed or accessibility. Only 48% of mobile websites had good Core Web Vitals in 2025, according to the HTTP Archive Web Almanac, and 95.9% of the top million home pages had detectable WCAG failures in early 2026, according to WebAIM. Here is what the data says, and what it means for teams building web products.
What are teams building the web with in 2026?
The stack is consolidated. JavaScript is the most used language for the 12th year in a row, at 62.0%, with TypeScript at 43.8%, in the Stack Overflow Developer Survey 2026. Among 10,281 respondents to the web frameworks question, Node.js (46.4%) and React (41.5%) lead, followed by Next.js (20.6%), ASP.NET Core (19.9%) and jQuery (19.7%), according to the same survey. FastAPI (18.5%), Vue.js (17.2%) and Angular (16.0%) complete the top eight, so Python back ends sit alongside JavaScript ones. Node.js and React were also the top two in 2025.
Typed code is winning. In August 2025, TypeScript overtook Python and JavaScript to become the most used language on GitHub by contributor count, according to GitHub Octoverse 2025. GitHub links the shift to AI: typed languages make agent-assisted coding more reliable, and nearly every major frontend framework now scaffolds with TypeScript by default.
For most products, the framework choice is no longer the risky decision. Architecture, performance budgets, accessibility and test coverage are.
How fast is the web in 2026?
Faster than before, still not fast enough on phones. The Web Almanac 2025, based on Chrome user data from July 2025, found that 48% of mobile websites and 56% of desktop websites had good Core Web Vitals, with mobile up from 36% in 2023 and 44% in 2024.
Websites with good Core Web Vitals
- Mobile, 2023
- 36%
- Mobile, 2024
- 44%
- Mobile, 2025
- 48%
- Desktop, 2025
- 56%
Source: HTTP Archive, Web Almanac 2025, Performance (Chrome UX Report, July 2025)
Responsiveness is the metric to watch. Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital in March 2024, and it measures how quickly a page reacts to clicks and taps. On mobile, 77% of websites have good INP, up from 74% in 2024, against 97% on desktop, per the Web Almanac.
Popular sites are not automatically fast. Only 51% of the 1,000 most visited mobile sites have good Core Web Vitals, according to the Web Almanac. Responsiveness is weakest deeper in the site: 69% of mobile secondary pages have good INP against 80% of mobile home pages, in the same chapter, which points to filters, carousels, form validation and third-party scripts that load there.
How accessible is the web in 2026?
It got worse this year. In the WebAIM Million 2026, 95.9% of the top 1,000,000 home pages had detected WCAG 2 failures, up from 94.8% in 2025, and the average page had 56.1 detected errors, up 10.1%. Automated tools catch only part of the problem, so the real share of inaccessible pages is higher.
Most common detected WCAG failures, share of home pages
- Low contrast text
- 83.9%
- Missing image alt text
- 53.1%
- Missing form input labels
- 51%
- Empty links
- 46.3%
- Empty buttons
- 30.6%
- Missing document language
- 13.5%
Source: WebAIM Million 2026 (top 1,000,000 home pages, February 2026)
The failures are basic and repetitive. Low contrast text appears on 83.9% of home pages and missing image alt text on 53.1%, and 96% of all detected errors fall into just six categories, according to WebAIM. That is good news: a design system and automated checks in the pipeline remove most of them.
Accessibility is also a legal requirement in the EU. Under the European Accessibility Act (Directive 2019/882), the accessibility requirements cover e-commerce services provided to consumers after 28 June 2025, along with consumer banking, e-books, transport ticketing and other listed services. Microenterprises providing services, meaning fewer than 10 staff and no more than EUR 2 million in annual turnover or balance sheet, are exempt.
How is AI changing web development?
AI is now part of daily coding. In the Stack Overflow Developer Survey 2026, 73% of people who use AI coding assistants or agents use them daily, 69.3% use AI to generate code in a familiar area and 58.1% use it to write or improve tests. On GitHub, nearly 80% of new developers use Copilot in their first week, according to GitHub's own data.
More code is not the same as better pages. WebAIM attributes this year's accessibility decline to larger, more complex pages and to reliance on frameworks, libraries and AI-assisted coding, which it calls "vibe coding". That is WebAIM's interpretation rather than a measured cause, but the risk is real: a generated component can look right and still fail keyboard, contrast or labeling checks.
What are the main challenges for web development teams?
1. Mobile performance. More than half of mobile sites still miss good Core Web Vitals, per the Web Almanac, and the gap between desktop and mobile hardware keeps that hard. Median Total Blocking Time is 92 ms on desktop and 1,916 ms on mobile in the same report.
2. Accessibility debt. Errors grew faster than fixes in the WebAIM Million 2026, and every new component built without checks adds to the backlog.
3. JavaScript weight on interactive pages. Third-party widgets, analytics and client-side logic land on the pages where users act, which is where INP drops.
4. Reviewing AI-generated code. Generation is fast. Verifying that a page is fast, accessible and correct still takes engineers and tests.
5. Regulation. Teams whose services fall under the European Accessibility Act now need accessibility evidence, not just good intentions.
What does good web development look like, and how do you start?
- Measure real users. Track Core Web Vitals from field data, per page type, not only the home page.
- Set budgets in CI. Fail the build when bundle size, Lighthouse scores or accessibility checks regress.
- Build accessibility into components. Contrast, labels, alt text and focus states belong in the design system, so every page inherits them.
- Test what users do. End-to-end tests for key journeys catch the regressions that unit tests miss, including in AI-written code.
- Start with an audit. Take your five most visited pages, check field vitals and run an automated accessibility scan. Fix the shared components first, because one fix repairs many pages.
Want a web app that is fast, accessible and tested?
SDCLabs builds web applications and SaaS products with time-proven frameworks. AI agents draft code and tests, senior engineers review every change and decide what ships, and test automation from the founders of Codeception and CodeceptJS runs on every release. Engagements start in 1 to 2 weeks.
Tell us about your product. Related: QA and test automation and our guide to the cost of web app development.
Sources checked on 2026-11-17.
Frequently asked questions
What share of websites pass Core Web Vitals?
In the HTTP Archive Web Almanac 2025, based on Chrome user data from July 2025, 48% of mobile websites and 56% of desktop websites had good Core Web Vitals.
What are the most used web frameworks in 2026?
In the Stack Overflow Developer Survey 2026, Node.js (46.4%) and React (41.5%) led, followed by Next.js (20.6%), ASP.NET Core (19.9%) and jQuery (19.7%).
How accessible are websites in 2026?
The WebAIM Million 2026 found detectable WCAG 2 failures on 95.9% of the top 1,000,000 home pages, with an average of 56.1 errors per page.
Does the European Accessibility Act apply to online shops?
Directive (EU) 2019/882 covers e-commerce services provided to consumers after 28 June 2025. Microenterprises providing services (fewer than 10 staff and no more than EUR 2 million turnover or balance sheet) are exempt.
