Preloading resources of a web page

• US 9,756,108 B2
• Filed: 04/23/2013
• Issued: 09/05/2017
• Est. Priority Date: 05/29/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Jain, Arvind, Gentilcore, Anthony Charles, Souders, Steven K., Agrawal, Shishir Kumar, Lamm, Stephen E., Kleber, Michael, Simonsen, James
• Primary Examiner(s): Survillo, Oleg
• Assistant Examiner(s): CADORNA, CHRISTOPHER PALACA
• Application Number:
  US13/868,920
• Publication Number:
  US 20150200994A1
• Time in Patent Office: 1,596 Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

A computer-implemented method for preloading resources of a web page is provided. The method includes receiving a user request to navigate to a web page and issuing a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources requested for loading the requested web page. The method also includes determining, based on a prior history of loading the requested web page, anticipated resources that are likely to be requested when loading the requested web page, and requesting the anticipated resources from a server associated with the anticipated resources at least until a time that the root page corresponding to the requested web page is received to determine the actual resources requested for loading the requested web page. Systems and machine-readable media are also provided.

Claims

1. A computer-implemented method for preloading resources of a web page, the method comprising:

receiving, by a web browser, a user request to navigate to a web page;

issuing, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page;

determining, essentially concurrently with the issued root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page;

requesting, by the web browser, the anticipated resources from a server;

concurrently receiving the requested root page and the requested anticipated resources; and

ceasing to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received.

2. The method of claim 1, further comprising:

determining actual resources requested for loading the web page by parsing the received requested root page; and

comparing the anticipated resources to the actual resources, wherein, if one of the determined actual resources corresponds to one of the received anticipated resources, using the received anticipated resource when loading the requested web page.

3. The method of claim 1, wherein the anticipated resources are received until a time that the entire requested root page corresponding to the requested web page is received and parsed to determine the actual resources requested for loading the requested web page.

4. The method of claim 1, wherein the prior history of loading the requested web page comprises information on an order in which the actual resources were requested in a previous loading of the requested web page, wherein the requested anticipated resources are requested in the order in which the actual resources were requested in the previous loading.

5. The method of claim 1, wherein the prior history of loading the requested web page comprises at least one of a number of times that an anticipated resource has corresponded to an actual resource requested for loading the requested web page for a threshold number of consecutive web page loads, a number of times that the anticipated resource has not corresponded to an actual resource requested for loading the requested web page, or a number of times the anticipated resource has not corresponded to an actual resource requested for loading the requested web page consecutively.

6. The method of claim 1, wherein the prior history of loading the requested web page comprises a cache header for the anticipated resource.

7. The method of claim 1, wherein the anticipated resources are requested if the anticipated resources are at least one of marked as cacheable or do not have a cache header.

8. The method of claim 1, wherein the predetermined amount of data is 256 bytes.

9. The method of claim 1, wherein the step of determining the anticipated resources comprises determining that the prior history of loading the web page is available for more than a predetermined number of previous loads of the web page.

10. The method of claim 1, wherein the step of determining the anticipated resources further comprises determining the anticipated resources based on a resource cache, wherein the resource cache comprises a plurality of cached resources that have been previously requested for loading the requested web page.

11. The method of claim 10, further comprising updating the plurality of cached resources before receiving the user request to navigate to the web page.

21. The method of claim 1, further comprising:

determining a priority for each anticipated resource based on the number of dependent resources associated with the anticipated resource; and

receiving the anticipated resources in the order of the determined priorities.

12. A system for preloading resources of a web page, the system comprising:

a memory storing executable instructions; and

a processor coupled to the memory configured to execute the stored executable instructions to;

receive, by a web browser, a user request to navigate to a web page;

issue, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page;

determine, essentially concurrently with the issued root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page;

request, by the web browser, the anticipated resources from a server;

concurrently receive the requested root page and the requested anticipated resources;

cease to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received;

determine actual resources requested for loading the web page by parsing the received requested root page; and

compare the anticipated resources to the actual resources, wherein if one of the determined actual resources corresponds to one of the received anticipated resources, use the received anticipated resource when loading the web page.

13. The system of claim 12, wherein the anticipated resources are received until a time that the entire requested root page corresponding to the requested web page is received and parsed to determine the actual resources requested for loading the requested web page.

14. The system of claim 12, wherein the prior history of loading the requested web page comprises information on an order in which the actual resources were requested in a previous loading of the requested web page.

15. The system of claim 12, wherein the prior history of loading the requested web page comprises at least one of a number of times an anticipated resource has corresponded to an actual resource associated with loading the requested web page, a number of times the anticipated resource has not corresponded to an actual resource associated with loading the requested web page, or a number of times the anticipated resource has not corresponded to an actual resource requested for loading the requested web page consecutively.

16. The system of claim 12, wherein the prior history of loading the requested web page comprises a cache header for the anticipated resource.

17. The system of claim 12, wherein the anticipated resources are requested if the anticipated resources are at least one of marked as cacheable or do not have a cache header.

18. The system of claim 12, wherein the step of determining the anticipated resources further comprises determining the anticipated resources based on a resource cache, wherein the resource cache comprises a plurality of cached resources that have been previously requested for loading the requested web page.

19. A non-transitory machine-readable storage medium comprising machine-readable instructions for causing a processor to execute a method for preloading resources of a web page, the method comprising:

receiving, by a web browser, a user request to navigate to a web page;

issuing, by the web browser, a request for a root page corresponding to the requested web page, wherein the root page identifies actual resources required for loading the requested web page;

determining, essentially concurrently with issuing the root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page;

determining whether the anticipated resources are at least marked as cacheable or do not have a cache header;

requesting the anticipated resources from a server when the predicted resources are determined to be marked as cacheable or not having a cache header;

concurrently receiving the requested root page and the requested anticipated resources; and

ceasing to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received.

20. A computer-implemented method for preloading resources of a web page, the method comprising:

using a daemon to crawl a cache associated with the web page;

issuing, by a web browser, a request for a root page corresponding to the web page, wherein the root page identifies actual resources required for loading the web page;

determining, essentially concurrently with the issued root page request and based on a history of prior loading sessions for the same requested web page, anticipated resources that are likely to be requested as part of loading the requested web page;

requesting, by the web browser, the anticipated resources from a server;

concurrently receiving the requested root page and the requested anticipated resources; and

ceasing to receive the requested anticipated resources when a predetermined amount of data for the requested root page has been received.