Optimized browser rendering service

• US 10,284,623 B2
• Filed: 08/09/2017
• Issued: 05/07/2019
• Est. Priority Date: 06/26/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Eastham, Michael, Xu, Hui, Meng, Biping, Zhou, Xiaobo
• Primary Examiner(s): Gilles, Jude Jean
• Application Number:
  US15/672,895
• Publication Number:
  US 20170359402A1
• Time in Patent Office: 636 Days
• Field of Search: 709203
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: H04L 41/0293 for accessing web services by means of a binding identification of the management service or element
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Implementations optimize a browser render process by identifying content neutral embedded items and rendering a web page without fetching the content neutral items. An example method includes identifying a URL pattern common to a plurality of URLs stored in fetch records and selecting a sample of URLs from the plurality. The method also includes, for each URL in the sample, determining whether the URL is optional by generating a first rendering result using content for the URL and a second rendering result without using the content for the URL and calculating a similarity score for the URL by comparing the first rendering result and the second rendering result, the URL being optional when the similarity score is greater than a similarity threshold. The method may also include storing the URL pattern in a data store of optional resource patterns when a majority of the URLs in the sample are optional.

Claims

1. A computer system comprising:

at least one processor; and

memory storing instructions that, when executed by the at least one processor, cause the system to;

receive a URL for an embedded resource in a web-page from a requestor,

determine whether the embedded resource is an optional resource by determining that the URL for the embedded resource matches a pattern in a data store identifying optional resources,

responsive to determining that the embedded resource is an optional resource, provide an indication that the embedded resource is not found, and

responsive to determining that the embedded resource is not an optional resource, fetch content for the embedded resource and provide the content to the requestor.

2. The system of claim 1, wherein the embedded resource is included in the data store identifying optional resources responsive to determining a rendering result of the web page rendered with the embedded resource is similar to a rendering result of the web page rendered without the embedded resource.

3. The system of claim 1, wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to:

rewrite the URL by removing a query string from the URL; and

match the rewritten URL to the pattern in the data store identifying optional resources, wherein the embedded resource is determined to be optional when the rewritten URL matches the pattern.

4. The system of claim 1, wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to:

rewrite the URL for the embedded resource by removing at least a portion of a query string from the URL; and

match the rewritten URL to the pattern in the data store identifying optional resources,

wherein the embedded resource is determined to be optional when the rewritten URL matches the pattern.

5. The system of claim 1, wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to:

generate a first rendering result for an embedder of the embedded resource using content fetched from the URL;

generate a second rendering result for the embedder of the embedded resource without using the content;

calculate a similarity score for the URL by comparing the first rendering result to the second rendering result,

determine that the embedded resource is optional when the similarity score is greater than a similarity threshold; and

responsive to determining that the embedded resource is optional, store the URL pattern in the data store.

6. The system of claim 5, wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to:

generate a third rendering result for the embedder of the embedded resource using the the content fetched from the URL; and

disregard any differences between the third rendering result and the first rendering during calculation of the similarity score.

7. The system of claim 5, wherein the memory further stores instructions that, when executed by the at least one processor, cause the system to:

generate a third rendering result for the embedder of the embedded resource using the the content fetched from the URL;

determine DOM nodes that are different between the first rendering result and the third rendering result; and

ignore the DOM nodes that are different when calculating the similarity score.

8. The system of claim 1, wherein the URL is received as part of a fetch request for the embedded resource.

9. The system of claim 1, wherein the requestor is an indexing engine.

10. The system of claim 1, wherein the requestor is a browser.

11. A computer-implemented method comprising:

receiving, using a hardware processor, a URL for an embedded resource in a web-page from a requesting process;

determining, using the hardware processor, whether the embedded resource is an optional resource by determining whether the URL for the embedded resource matches a pattern in a data store, stored in a memory, identifying optional resources;

responsive to determining that the embedded resource is an optional resource, providing a response indicating no fetch of the embedded resource is required to render the web page; and

responsive to determining that the embedded resource is not an optional resource, providing a response indicating a fetch of the embedded resource is required.

12. The method of claim 11, wherein the requesting process is a browser and the method is performed by a service local to a computing device running the browser.

13. The method of claim 11, wherein the requesting process is a browser and the method is performed by a service remote from a computing device running the browser.

14. The method of claim 11, further comprising:

rewriting the URL by removing a query string from the URL; and

matching the rewritten URL to the pattern in the data store identifying optional resources, wherein the embedded resource is determined to be optional when the rewritten URL matches the pattern.

15. The method of claim 11, further comprising:

rewriting the URL for the embedded resource by removing at least a portion of a query string from the URL; and

matching the rewritten URL to the pattern in the data store identifying optional resources,

wherein the embedded resource is determined to be optional when the rewritten URL matches the pattern.

16. The method of claim 11, further comprising:

generating a first rendering result for an embedder of the embedded resource using content fetched from the URL;

generating a second rendering result for the embedder of the embedded resource without using the content;

calculate a similarity score for the URL by comparing the first rendering result to the second rendering result;

determining that the embedded resource is optional when the similarity score is greater than a similarity threshold; and

responsive to determining that the embedded resource is optional, storing the URL in the data store as the pattern.

17. The method of claim 16, further comprising:

generating a third rendering result for the embedder of the embedded resource using the the content fetched from the URL; and

disregarding any differences between the third rendering result and the first rendering during calculation of the similarity score.

18. The method of claim 16, further comprising:

generating a third rendering result for the embedder of the embedded resource using the the content fetched from the URL;

determining DOM nodes that are different between the first rendering result and the third rendering result; and

ignoring the DOM nodes that are different when calculating the similarity score.

19. The method of claim 11, further comprising:

identifying a URL pattern common to a plurality of URLs stored in fetch records, the URL being one of the plurality of URLs;

selecting a sample of URLs from the plurality of URLs, the URL being one of the sample of URLs;

for each of the sample of URLs;

generating a first rendering result for an embedder of the embedded resource using content fetched from the URL,

generating a second rendering result for the embedder of the embedded resource without using the content;

calculating a respective similarity score for the URL by comparing the first rendering result to the second rendering result, and

determining that the embedded resource is optional when the similarity score is greater than a similarity threshold; and

responsive to a predetermined number of the respective similarity scores being greater than a similarity threshold, storing the URL pattern common to the plurality of URLs in the data store.

20. The method of claim 11, wherein the pattern is the entire URL.