Http/2 Server Push for App/Common Bundles
See original GitHub issueI only found this old and seemingly outdated information about http/2 server push support in next.js.
For our production next.js app, neither _app.js
nor commons.*.js
are loaded via http/2 server push. I checked using the Chrome 71 Network tab in column “Initiator”.
Could server push of these resources bring performance improvements for the load time of a next.js app? How would it be possible to activate it, if at all?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Http/2 Server Push for App/Common Bundles #6163 - GitHub
js are loaded via http/2 server push. I checked using the Chrome 71 Network tab in column "Initiator". Could server push of these...
Read more >A Comprehensive Guide To HTTP/2 Server Push
Server push acts as a suitable alternative for a number of HTTP/1-specific optimization anti-patterns, such as inlining CSS and JavaScript ...
Read more >Utilizing HTTP2 PUSH in a Single Page Application - Bitovi
When writing client-side applications, we deal with this problem in a variety of ways such as: Pre-rendering the application on the server.
Read more >Announcing Support for HTTP/2 Server Push
In its most basic form, Server Push allows the server to “bundle” assets that the client didn't ask for. It works by sending...
Read more >How to decide which files can I push with HTTP 2 Server Push ...
I have an Angular 8 app, which by default generates 2 js files for each bundle, ES5 and ES6 versions. I would like...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@fabb +1. My “Next Preload Headers” module sometimes causes a “can’t add headers to already sent response” message which I believe is harmless could be an indication that next.js is the only place to put preload links into the header due without any side effects. I am fairly new at node so if an expert could help take that plugin to the next level it would benefit most next.js users performance I think.
Thank you. Any idea why next.js does not put preload links to the header by default?