Am I truly using http2?
0
I have never setup http2 but I think cloudflare serve request as http2.
However, when I see dev tool water fall it looks like http1.
Because of the when I just test with http2 testing site it show I am serving http2.
As you see it kinda fetching 5 or 6 at a time.
Do I need to setup ngnix http2 instead of relying on cloudflare ?
I also added webpack optimization option to allow more requests.
optimization: {
splitChunks: {
maxAsyncRequests: 20,
maxInitialRequests: 20,
minChunks: 2,
chunks: 'all',
cacheGroups: {
styles: {
name: 'styles',
test: /.css$/,
chunks: 'all',
enforce: true
},
}
}
},
javascript webpack http2 code-splitting react-loadable
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
|
show 1 more comment
0
I have never setup http2 but I think cloudflare serve request as http2.
However, when I see dev tool water fall it looks like http1.
Because of the when I just test with http2 testing site it show I am serving http2.
As you see it kinda fetching 5 or 6 at a time.
Do I need to setup ngnix http2 instead of relying on cloudflare ?
I also added webpack optimization option to allow more requests.
optimization: {
splitChunks: {
maxAsyncRequests: 20,
maxInitialRequests: 20,
minChunks: 2,
chunks: 'all',
cacheGroups: {
styles: {
name: 'styles',
test: /.css$/,
chunks: 'all',
enforce: true
},
}
}
},
javascript webpack http2 code-splitting react-loadable
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30
|
show 1 more comment
0
0
0
I have never setup http2 but I think cloudflare serve request as http2.
However, when I see dev tool water fall it looks like http1.
Because of the when I just test with http2 testing site it show I am serving http2.
As you see it kinda fetching 5 or 6 at a time.
Do I need to setup ngnix http2 instead of relying on cloudflare ?
I also added webpack optimization option to allow more requests.
optimization: {
splitChunks: {
maxAsyncRequests: 20,
maxInitialRequests: 20,
minChunks: 2,
chunks: 'all',
cacheGroups: {
styles: {
name: 'styles',
test: /.css$/,
chunks: 'all',
enforce: true
},
}
}
},
javascript webpack http2 code-splitting react-loadable
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
I have never setup http2 but I think cloudflare serve request as http2.
However, when I see dev tool water fall it looks like http1.
Because of the when I just test with http2 testing site it show I am serving http2.
As you see it kinda fetching 5 or 6 at a time.
Do I need to setup ngnix http2 instead of relying on cloudflare ?
I also added webpack optimization option to allow more requests.
optimization: {
splitChunks: {
maxAsyncRequests: 20,
maxInitialRequests: 20,
minChunks: 2,
chunks: 'all',
cacheGroups: {
styles: {
name: 'styles',
test: /.css$/,
chunks: 'all',
enforce: true
},
}
}
},
javascript webpack http2 code-splitting react-loadable
javascript webpack http2 code-splitting react-loadable
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
asked Nov 23 '18 at 17:29
Seongjun Kim
366522
366522
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30
|
show 1 more comment
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30
|
show 1 more comment
1 Answer
1
active
oldest
votes
0
Looks like the main... is calling the later scripts, so presumably the browser doesn’t think it needs to load more than the 5 or 6 resources at a time.
HTTP/2 doesn’t magically fix all performance issues with a site - often there are other limitations on a site, and these may be bigger than the issues with HTTP/1 that HTTP/2 is designed to address.
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450852%2fam-i-truly-using-http2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Looks like the main... is calling the later scripts, so presumably the browser doesn’t think it needs to load more than the 5 or 6 resources at a time.
HTTP/2 doesn’t magically fix all performance issues with a site - often there are other limitations on a site, and these may be bigger than the issues with HTTP/1 that HTTP/2 is designed to address.
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
add a comment |
0
Looks like the main... is calling the later scripts, so presumably the browser doesn’t think it needs to load more than the 5 or 6 resources at a time.
HTTP/2 doesn’t magically fix all performance issues with a site - often there are other limitations on a site, and these may be bigger than the issues with HTTP/1 that HTTP/2 is designed to address.
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
add a comment |
0
0
0
Looks like the main... is calling the later scripts, so presumably the browser doesn’t think it needs to load more than the 5 or 6 resources at a time.
HTTP/2 doesn’t magically fix all performance issues with a site - often there are other limitations on a site, and these may be bigger than the issues with HTTP/1 that HTTP/2 is designed to address.
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
Looks like the main... is calling the later scripts, so presumably the browser doesn’t think it needs to load more than the 5 or 6 resources at a time.
HTTP/2 doesn’t magically fix all performance issues with a site - often there are other limitations on a site, and these may be bigger than the issues with HTTP/1 that HTTP/2 is designed to address.
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
edited Nov 26 '18 at 18:23
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
answered Nov 23 '18 at 20:45
Barry Pollard
15.9k22547
15.9k22547
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
add a comment |
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
is there anyway I can remove number of max load ?
– Seongjun Kim
Nov 26 '18 at 14:39
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
What do you mean by fixing number of max load? I don’t think you have hit a maximum limit. I think you only need those initial 5-6 resources and by the time it has spotted it needs other resources those initial ones are dealt with. I think you are limited by your JavaScript deciding it needs to load resources rather than by 12 being requested at once and only 6 being fetched at a time.
– Barry Pollard
Nov 26 '18 at 18:25
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
do you have experience using react-loadable ?
– Seongjun Kim
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
Nope. Suggest you run webpagetest.org on the app (if deployed) and then link to that.
– Barry Pollard
Nov 26 '18 at 20:07
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450852%2fam-i-truly-using-http2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
According to the protocol column, your local resources are being delivered over HTTP/2. If you are going through Cloudflare then resources will be delivered over HTTP/2 from it's caching servers, however if it has to communicate with your origin server and that does not support HTTP/2, then page load will be limited by the slowest connection.
– luc122c
Nov 26 '18 at 9:10
shouldn't waterfall column should be all in one line ? It seems it fetches 5 and then fetch more
– Seongjun Kim
Nov 26 '18 at 14:41
No, as it appears that the scripts are being initiated from different sources. Resource 1 is initiated by the page itself. Resources 2, 3, 4 and 5 are initiated by a script 'rock...'. Scripts 6, 7, 8 and 9 are initiated by 'main...'. This means the index is parsed, then rock... (which loads some more scripts) then main... (which loads more scripts). This doesn't look like a problem with HTTP, the gap is probably caused by the time it takes to parse the JavaScript.
– luc122c
Nov 26 '18 at 21:09
so only way to fix this problem is make main.js small
– Seongjun Kim
Nov 27 '18 at 15:25
Consider why rock... and main.js are pulling in other (blocking) scripts. Can they not all be pulled in by the index document? Take a look here: developers.google.com/web/tools/lighthouse/audits/…
– luc122c
Nov 27 '18 at 20:30