First, let's look at the definition:
Google AMP (Accelerated Mobile Pages) is a type of web page built for static content launched by Google, providing reliable and fast rendering, and speeding up page load times, especially when viewing content on the mobile web side.
Baidu MIP (Mobile Instant Pages) is a set of open technology standards for mobile web pages. Mobile web page acceleration is achieved by providing the MIP-HTML specification, MIP-JS running environment, and MIP-Cache page caching system.
It seems that the definitions of the two are very similar, one is called accelerating mobile pages, the other is called mobile web acceleration, and the purpose is the same - optimizing mobile web pages. WTF, it won't be a thing. Of course it's not the same thing, but it's just the difference between Laotan sauerkraut noodles and Master Kong's beef noodles. Both are instant noodles, the main raw materials are the same, the recipe is a little different, the way of making is a little different, and the most important thing is that the spokesperson is different.
Mobile web acceleration was first proposed by Google, by formulating open source standards, formulating page specifications, optimizing rendering speed to improve user experience, and Google will increase the weight of pages that meet AMP standards in search engines. Baidu adheres to the principle that Google has me, fully borrows from AMP, and also puts forward its own web acceleration open source standard, so MIP was born.
Baidu MIP is the same as Google AMP, even the page layout, menu arrangement, and technical description of the official website are almost the same, whether it is the purpose (returning extremely fast moving pages in search results), the principle (simplifying HTML, CSS, disabling most JS, resource control, caching, etc.), or the launch steps (news first, then general pages), and the mutual referencing method (adding tags) between the original page and the MIP page. Even the logos displayed on the corresponding search engines are almost identical:
Here I have to admire the Chinese people's ability to learn from it.
On-page optimization principles
Both AMP and MIP are essentially page acceleration by optimizing page rendering or lazy loading to reduce blocking. Just like some specifications within our business, we may also have a set of standards to improve our code quality and page performance. It's just that these two can bring us SEO optimization. Below, let's take a MIP as an example to understand the principle of her acceleration.
MIP is organized into three main parts:
MIP HTML
MIP JS
MIP Cache
MIP HTML formulates a new specification based on the basic tags in HTML, allowing HTML to display richer content by restricting the use of some basic tags or expanding functions. MIP JS can ensure fast rendering of MIP HTML pages; MIP Cache is used to implement caching of MIP pages, which further improves page performance.
The following describes the acceleration principle of MIP pages:
Well-designed JavaScript
MIP does not allow users to customize JavaScript and needs to be introduced in the form of MIP components to ensure security and performance
All static resources need to be dimensioned
MIP requires all assets (ads, images, audio, and video) to be dimensioned. When the resource is actually loaded, all resource sizes can be immediately inferred and quickly used to calculate the page layout, and the loading resource will be presented seamlessly without affecting the user's reading experience due to frequent page layout updates.
No mechanism is allowed to prevent page rendering
Any custom scripts by developers need to use MIP tags to feed back to MIP, such as mip-ad, mip-iframe, etc., which will not block the layout and rendering of the page.
Control external resource loading
The MIP runtime controls the loading of external resources to ensure their efficiency, so that what users want to read appears on the screen as quickly as possible.
Encapsulation of interactive functions
MIP advocates that web pages can give users a direct and simple experience, but this does not mean that MIP limits the vividness and fun of the page. The MIP runtime provides highly optimized encapsulated JavaScript that eliminates the need for developers to invest too much effort in implementing complex interactive functions.
It is recommended to use inline's CSS
CSS loading will prevent page rendering, and CSS inline can reduce the client's overhead.
Only GPU-accelerated animations are allowed
MIP only allows animations to be done with transforms and opacity, and only triggers render layer merging when animations can be executed on the GPU.
MIP cache
Another important significance of MIP is that it can help webmasters speed up web pages, and Baidu will cache MIP web pages to Baidu CDN. MIP caching can be used as long as it meets the MIP standard.
These are just the means we often use in optimizing web projects, but now Baidu has passed the open source standard and given SEO sweetness and unified specifications.
Google AMP and Baidu MIP's views
The mobile web optimization solutions provided by AMP and MIP can improve the user experience to a certain extent. At the same time, the combination with SEO has also increased the interest of many developers to join. However, due to the relatively closed environment, this set of standards cannot be applied to large-scale projects, but can only be applied to relatively simple page displays, of course, this is consistent with their original intention.
AMP and MIP are two different sets of standards, and in order to support the optimization of Google and Baidu's search engines, two sets of pages must be written, which will increase the development cost of developers.
In the future, I personally believe that the standards of the two companies will tend to be unified, and Baidu is estimated to support the AMP standard, after all, Google is from a global perspective, and Baidu only has more users in China.
MIP Tutorial:https://www.mipengine.org/doc/00-mip-101.html
Tutorial:https://www.ampproject.org/zh_cn/
|
Posted on 7/7/2018 9:47:36 AM
|
|
|
|
