Method and device for page loading

Abstract

The present application discloses a method and device for page loading. The method has a cache mode of structure cache and data cache, including: receiving a page load request, where the page load request includes request parameters, and the request parameters include the structure cache and the data cache. An associated identifier; according to the identifier of the request parameter, the structure data is obtained from the structure cache, and the interface data is obtained from the data cache; the page to be loaded is rendered according to the obtained structure data and interface data. This method is a double-cache scheme based on interface data and DOM structure, and a second-out scheme based on DOM structure cache, which can complete the first screen rendering at the fastest speed. At the same time, for scenarios that rely on interface data, the page visibility time and page availability time of secondary loading are greatly reduced, and the loading time of the first screen of Html pages is accelerated.

Description

technical field [0001] The present application relates to the technical field of page loading in web pages, in particular to a method for page loading. The present application also relates to a device for page loading. Background technique [0002] A hybrid development solution for various existing wireless clients, such as mobile Taobao, Alipay, Alitrip, etc., and a large number of Html5 (hereinafter referred to as H5) are used in the client as the page display container. [0003] Traditional H5 page loading and rendering needs to go through four steps: HTML loading, CSS / JS loading, data request, and page rendering. However, in the case of an unsatisfactory network environment, excessive resource loading and initialization will greatly prolong page loading and time. Rendering completion time. [0004] For user experience, the page display time after clicking and jumping is a very key indicator. For this reason, each container implements an offline solution for static reso...

AI Technical Summary

Problems solved by technology

[0003] Traditional H5 page loading and rendering needs to go through four steps: HTML loading, CSS / JS loading, data request, and page rendering. However, in the case of an unsatisfactory network environment, excessive resource loading and initialization will greatly prolong page loading and render completion time

[0004] For user experience, the page display time after clicking and jumping is a very key indicator. For this reason, each container has implemented a static resource offline solution (offline HTML / JS / CSS files to the local), reducing resource loading time, but data interface access is still subject to network conditions, such as product list pages and other scene pages are still unable to achieve seconds

Images