The webpage cannot be opened because the div element lacks a closing tag

At first I thought it was a speed issue, so I later connected all image link requests to the site instead of cross-site connections, but the problem still persisted.

But what is puzzling is that with the same set of codes, other pages can open normally, why is there a problem with this page?

Finally, the only way to troubleshoot is to check the code. Code checking is a very difficult task because the code is not written in a standard way and is densely packed.

Start checking from top to bottom, deleting each piece one by one, and checking each time to see if the webpage can be opened normally. . .

Later, a div tag gave me inspiration, as shown below:

A warning wave appears at a certain div. Move the mouse over it and a text prompt appears: Validation (XHTML 1.0 Transitional): Element "div" is missing a closing tag .

This is where the undisplayable part starts!

I then added the closing tag </div> at the appropriate location.

Check the webpage opening status again, it is finally normal!

postscript

From my case, I thought of many similar web pages, where the upper part of the web page opens very quickly, but the lower part, especially the main text, takes a few seconds to open. In most cases, I won't wait any longer, because I can use the waiting time to click on another record in the search results to open another web page. What's more, I don't know what the result of waiting will be.

Although there are many factors that affect the speed of web page opening, I think the most critical and important one is the web page code itself. If improving bandwidth and hardware is not practical, why not optimize it in the web page code?

<<: Detailed explanation of fetch network request encapsulation example

>>: CSS to achieve the small sharp corner effect of bubbles