whatwg/html

Performance Issue: Main single-page specification loads whole spec at root URL

Open

#12,782 opened on Aug 13, 2026

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)HTML (2,520 forks)batch import
good first issuemetaspec tooling

Repository metrics

Stars
 (7,654 stars)
PR merge metrics
 (Avg merge 42d 18h) (22 merged PRs in 30d)

Description

What is the issue with the HTML Standard?

⚠️ Performance Issue: Main single-page specification loads whole spec at root URL

Description

Navigating to the root URL (https://html.spec.whatwg.org/) loads the entire HTML Living Standard as a single, monolithic document. This creates severe browser performance issues, especially on lower-spec hardware or mobile devices.

Impact / Symptoms

  • High Memory Consumption: Loads over 15 MB of raw HTML and hundreds of thousands of DOM nodes in a single frame.
  • Browser Freezing/Crashing: Tabs often hang, become unresponsive during rendering, or crash due to memory limits.
  • Sluggish Native Search: Using Ctrl+F causes massive layout recalculation and severe input lag.

Suggested Solutions

  • Consider making the /multipage/ version the default landing view, or prominent default redirect.
  • Add an explicit, high-visibility banner at the top of the single-page view suggesting visitors switch to the /multipage/ or /dev/ edition if they experience page lag.

Contributor guide

Research direction
Investigate how the HTML Standard website serves the single page edition at the root URL. Explore the build and serving configuration to understand how to redirect to /multipage/ or add a banner. Look for existing performance considerations in the repository.
Tech stack
html
Domain
frontendperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHTML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70