HTTP/2 is a connection protocol configured on the web server or the proxy that handles your site’s public HTTPS traffic—not in WordPress itself. To use it, the public endpoint must support HTTP/2 and have it enabled; on NGINX, that means an HTTP/2-capable build, HTTPS configuration, and the current http2 on; directive. If your host or CDN controls that endpoint, ask its support team to enable or confirm HTTP/2.
What HTTP/2 means for a WordPress site
HTTP/2 is a version of the protocol used to transfer requests and responses between a browser and the server-side endpoint handling the connection. WordPress runs on that web infrastructure, but it does not provide a dashboard switch or plugin that turns HTTP/2 on. The protocol is negotiated at the server or TLS-terminating proxy, so the right configuration depends on who operates that endpoint.
WordPress’s current requirements page recommends HTTPS but does not list HTTP/2 as a separate WordPress requirement: WordPress requirements. Enabling HTTP/2 should therefore be treated as a server or hosting configuration task, not a WordPress installation step.
What you need before enabling it
- An HTTPS endpoint: Browser deployments of HTTP/2 use HTTPS in practice. WordPress’s HTTPS guidance says the site needs a TLS/SSL certificate installed and available to the web server: WordPress HTTPS documentation.
- Control of the endpoint: If a CDN, reverse proxy, or load balancer terminates public TLS, HTTP/2 may need to be enabled there rather than on the origin server. Confirm the architecture with your host before editing server configuration.
- A capable server build and configuration: For NGINX, the HTTP/2 module must be built in. Consult the documentation for the installed software and your host’s change process before applying configuration.
Enable HTTP/2 on NGINX
NGINX’s documented pattern for an HTTPS server block uses listen 443 ssl; together with http2 on;. The HTTP/2 module documentation also describes ALPN support for HTTP/2 over TLS. See the NGINX HTTP/2 module documentation and the NGINX core directive documentation; the older listen ... http2 parameter is deprecated in the latter.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Used Book in Good Condition
server {
listen 443 ssl;
http2 on;
server_name example.com;
ssl_certificate /path/to/certificate.pem;
ssl_certificate_key /path/to/private-key.pem;
# Keep the site's existing WordPress location and routing configuration here.
}This is a configuration pattern, not a complete WordPress server configuration or a tested file for your site. Replace the example hostname and certificate paths with the real values, and preserve the existing WordPress routing and location rules. Use syntax supported by the installed NGINX version. Validate the configuration and reload it through your normal, documented operational process; do not paste this abbreviated block over a live configuration.
If your host or CDN manages the server
Many WordPress site owners cannot edit NGINX or proxy settings directly. WordPress’s server guidance recommends consulting the hosting provider about server configuration: WordPress server environment guidance. Ask support: “Does the public HTTPS endpoint for my domain negotiate HTTP/2, and if not, can you enable it?”
For a CDN, reverse proxy, or load balancer, ask which service terminates TLS for visitors and whether that public-facing service serves HTTP/2. The origin may have a different protocol configuration from the endpoint visitors actually reach. Do not change origin settings until you know where the public connection is handled.
HTTPS settings in WordPress are not HTTP/2 settings
WordPress’s HTTPS documentation also covers forcing HTTPS for logins and administration with FORCE_SSL_ADMIN, and handling reverse-proxy awareness where necessary, including the HTTP_X_FORWARDED_PROTO header. Those settings help WordPress recognize or use HTTPS; they do not enable HTTP/2 on the server. Follow the WordPress HTTPS guidance for those separate concerns, especially in a proxy setup.
How to check whether HTTP/2 is active
- Open the public HTTPS version of the exact hostname you use, including
wwwor the apex domain as applicable. - Use your browser’s developer tools and inspect the network request’s negotiated protocol, or use a reliable protocol-checking tool.
- Check each public hostname and relevant route separately if they may be handled by different server or proxy configurations.
A valid certificate proves that HTTPS is available; it does not prove HTTP/2 is being negotiated. Likewise, a WordPress setting or a successful NGINX configuration reload is not enough to establish what a visitor’s browser receives. NGINX documents $http2 as an indicator of the negotiated protocol in its own configuration context, but checking the public endpoint verifies what matters to visitors.
Choosing the right route
| Route | Best fit | What to confirm |
|---|---|---|
| Ask the managed host or CDN | You do not administer the server or the service terminating public TLS. | Which endpoint handles public HTTPS, whether it negotiates HTTP/2 for each hostname, and whether the provider can enable it. |
| Configure the web server | You administer the server and know which software and version serves the public connection. | That the build includes the required HTTP/2 module, HTTPS is configured, the syntax matches the installed version, and the change can be validated and rolled back. |
What enabling HTTP/2 does—and does not—promise
HTTP/2 support changes the protocol available for browser-server communication; it does not guarantee a fixed speed improvement for every WordPress site. The official WordPress and NGINX sources cited here do not establish a current, attributable performance percentage for WordPress sites after enabling HTTP/2. Verify protocol negotiation rather than assuming that the change made pages faster.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
