Added fake AJAX to the blog, and finally removed it

text

A week ago, I added a piece of pseudo Ajax to my blog, and finally removed it.

In terms of code, the asynchronous loading method used by most WordPress themes is "fake Ajax". Although they have the effect of not refreshing and jumping, they cannot save traffic. The principle of these codes is much the same: first obtain the complete page asynchronously, then select the main elements, and finally fill the main contents to the current page. In this process, the browser still needs to get the full page, without saving traffic.

An ideal situation is to obtain the Json asynchronously, then parse it and populate it to the current page. In this way, it can not only save traffic and speed up, but also achieve the effect of not refreshing the jump. To implement this function on WordPress, you need to add a lot of content. It is better to write a blog program if you have time to add it. I don't understand the front and back ends, so I'm too lazy to do it.

At present, Google Adsense does not support Ajax: block ads are OK, and you can manually call the Push method to brush them. However, if you place automatic ads, the second time you call Push, you will report an enable_page_level_ads conflict and cannot refresh.

If you want to build a whole station music player or something similar, you'd better add pseudo Ajax. If you use Adsense, Ajax needs to be considered as appropriate.

About loading speed: My blog is using the Wp Super Cache plug-in. The article is static. Even if there is no asynchronous loading, the speed should not be too slow. The small water pipe of Tencent Cloud student machine occasionally gets stuck, but it doesn't hurt.