Server push is an important performance feature that you may want to try . However, one important thing to note is not to aggressively push files on every request. The browser may already have a cached copy of the resource for you, and the browser must have space to use that cache. Aggressively pushing too many resources that are not needed can waste bandwidth that the user may be on a metered connection.
If you want to try this, this post explains in detail how to set up server push for NGINX . This post on CSS-Tricks helps with setting up a cache-aware server push setup . This blog post has a lot of advice and algeria mobile database insights on using server push . For WordPress sites, the same Easy Speedup plugin provides this server push functionality.
<img data-original="s:static.semrush.combloguploadsmediad23dd23d676bb8dc4c7405cb3056b541b043original.png" alt="Preload your hosting chart" class="zooming lazyloaded" data-src="s:static.semrush.comcdn-cgiimagewidth=1010bloguploadsmediad23dd23d676bb8dc4c7405cb3056b541b043hsts%281%29.png" src="s:static.semrush.comcdn-cgiimagewidth=1010bloguploadsmediad23dd23d676…hsts%281%29.png">
HSTS, or Strict Transport Security, is a way to enforce S to ensure that if a user requests a page using plain old , an intruder doesn't have a chance to alter the request or response.
HSTS Preload is a list maintained by the Google Chrome team to create a catalog of such sites that endorse S for the entire domain and its subdomains. This domain list is used by most major browser vendors, including Chrome, Firefox, Opera, Safari, Edge, and IE. If a website is in this HSTS preload site list, the browser will always establish a secure connection with it. Even if the user tries to open such a site over unencrypted , the browser will look for the site in the list and change the request to S.