CodePudding user response:
Try debugging code, part of the comments part of debuggingCodePudding user response:
F12 view which request takes the longest timeCodePudding user response:
Should be a js connection failure, I also tried beforeCodePudding user response:
Also met this problem before, behind screening because returns the content of image problems, image storage is binary stream, lead to the content of the return is very large, which affects page loading slowly, you can see if the problemCodePudding user response:
First, F12 debugging looking is what long timescalesSecond, see page architecture, if instead of div + CSS table too much this image can affect the speed of the whole page rendering
Third, because the requested data is too large, lead to page rendering time is too long
Fourth, because the data of the slow query result in
Because what you have said is just a single page time consuming, well check
According to the above method for screening is very simple
CodePudding user response:
5 minutes?Is the greatest possible query of SQL optimization, or the amount of data is too large, Suggestions from the aspects of the first to screening,