HTTP/2 is a connection protocol between a visitor’s browser and the server or proxy serving your site. WordPress has no dashboard switch or plugin that enables it: the setting belongs on the HTTPS endpoint, which may be your web server, hosting provider, or CDN. If you administer an NGINX server, you can enable HTTP/2 in its HTTPS server block; otherwise, ask the provider that controls your public connection.
What HTTP/2 means for a WordPress site
HTTP/2 is a newer version of the protocol used to transfer website requests and responses. A browser negotiates it with the server or proxy that handles the public connection. WordPress supplies the site’s application and content, but the web server or TLS-terminating proxy determines which HTTP protocol is used for that connection.
That distinction matters because installing a WordPress plugin or changing a WordPress setting cannot, by itself, turn on HTTP/2. WordPress’s server and hosting guidance treats server configuration as part of the hosting environment.
What you need before enabling HTTP/2
- An HTTPS endpoint: Browser deployments of HTTP/2 generally use HTTPS. WordPress’s HTTPS guide says a TLS/SSL certificate must be installed and available to the web server for HTTPS.
- Support in the server or proxy: For NGINX, the HTTP/2 module must be built in. NGINX documents ALPN support for HTTP/2 over TLS in its HTTP/2 module documentation.
- Access to the component that serves HTTPS: If a CDN, load balancer, or reverse proxy handles the public connection, that service may be the place where HTTP/2 needs to be enabled—not the WordPress origin server.
A valid certificate confirms HTTPS configuration, not that HTTP/2 was negotiated. WordPress’s current requirements page recommends HTTPS but does not list HTTP/2 as a separate WordPress requirement.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Used Book in Good Condition
Enable HTTP/2 on NGINX
NGINX’s documented pattern uses a separate http2 on; directive alongside the TLS listener. The following is an abbreviated example, not a complete WordPress configuration:
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.
}Replace the example hostname and certificate paths with the values for your site, and preserve its existing WordPress routing and other server settings. NGINX’s core listen directive documentation describes the older listen ... http2 parameter as deprecated; use syntax supported by the version installed on your server.
- Confirm the NGINX version, build, and configuration process with your administrator or host. Verify that the HTTP/2 module is available.
- Identify the HTTPS server block for the exact hostname visitors use, and confirm that NGINX—not a CDN or another proxy—terminates the public TLS connection.
- In that block, configure the TLS listener and
http2 on;, while keeping the site’s existing certificate, key, and WordPress routing configuration. - Validate the NGINX configuration and reload it through your normal operational process. Do not replace a live configuration with the abbreviated example.
- Test the public HTTPS hostname after the change to confirm that the connection negotiates HTTP/2.
What to do on managed hosting, a CDN, or a proxy
If you cannot edit the server configuration, ask the provider that controls the public HTTPS endpoint: “Does the public HTTPS endpoint for my domain negotiate HTTP/2, and if not, can you enable it?” Your hosting provider or CDN may manage that setting. WordPress advises managed-hosting customers to consult the host’s documentation or support before changing server settings.
In a CDN or reverse-proxy setup, the browser may connect to the edge service while that service connects separately to your origin. HTTP/2 on one connection does not establish the protocol used on the other. Confirm which endpoint serves visitors and where its TLS configuration is managed before making changes.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Keep WordPress HTTPS settings separate
WordPress’s HTTPS guide explains how to use a TLS/SSL certificate with the web server, and documents FORCE_SSL_ADMIN for HTTPS logins and administration. It also notes that reverse-proxy setups may need WordPress to recognize the HTTP_X_FORWARDED_PROTO header. These settings help WordPress handle HTTPS correctly; they do not enable HTTP/2 on the public connection.
Verify HTTP/2 on the public site
Check the exact hostname visitors use, including both the apex domain and www if both are active. Different hostnames or routes may use different server or proxy configurations. Use a current browser’s network panel or a reliable protocol checker to inspect the negotiated protocol for an HTTPS request. A certificate, a WordPress setting, or an origin-server configuration alone is not proof that the public endpoint is serving HTTP/2.
NGINX also documents $http2 as an indicator of the negotiated protocol in its own configuration context. That can help an administrator inspect an NGINX-handled connection, but it does not replace checking the visitor-facing endpoint when a proxy or CDN sits in front.
Why there is no guaranteed speed percentage
Enabling HTTP/2 changes how the connection can carry web traffic, but it does not guarantee a particular performance improvement for every WordPress site. The official sources cited here provide no attributable, current speed figure for WordPress sites after enabling HTTP/2. Verify that the protocol is active, and assess your site’s performance separately rather than assuming a fixed gain.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
