Browser Pre-Caching for Web Page Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web browsing experiences are hindered by latency due to the numerous requests made by browsers to render pages, leading to increased user wait times as websites incorporate more complex functionalities.

Innovation Solution

Implementing a pre-caching system where a browser component asynchronously loads and caches pages likely to be selected by the user, allowing seamless transitions by replacing portions of the host page with cached content without navigating away from the original page, thus reducing the need for duplicate content downloads.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a browser makes numerous requests to render web pages with complex functionality, then the page functionality and content completeness are improved, but the user wait time and latency increase

Engineering Contradiction:
Improvepage functionalityVSAvoiduser wait time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-loading and caching web resources (images, scripts, stylesheets) into a resource cache before they are actually needed. When a user navigates to a page, the browser checks the resource cache first and uses cached resources if available, avoiding the need to make numerous HTTP requests during page rendering. This preliminary caching action resolves the contradiction by preparing resources in advance, thus maintaining complete page functionality while significantly reducing user wait time.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If a browser loads complete web pages for each navigation, then the content accuracy and completeness are improved, but the bandwidth usage and load time increase

Engineering Contradiction:
Improvecontent accuracyVSAvoidbandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies segmentation by dividing web resources into two categories: static resources (images, scripts, stylesheets) and dynamic content (HTML page content). Static resources are pre-loaded and cached independently from dynamic content. When navigating between pages, the browser reuses cached static resources and only requests dynamic content specific to the current page. This segmentation resolves the contradiction by maintaining content accuracy through proper caching while reducing bandwidth usage by avoiding redundant downloads of static resources.

Inventive Principle:
Principle #1Segmentation

3Speed

If a browser caches web resources, then the page load speed is improved, but the memory usage and cache management complexity increase

Engineering Contradiction:
Improvepage load speedVSAvoidcache management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent applies copying by creating a separate resource cache that stores copies of static web resources independently from the main page content. The resource cache contains copies of images, scripts, and stylesheets that can be reused across multiple pages. This copying approach resolves the contradiction by improving page load speed through efficient resource reuse while managing complexity through a dedicated, simplified caching layer that handles only static resources with straightforward cache-invalidation rules.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9065793B2Rendering web content using pre-caching
Publication Date: 2015.06.23 CBS INTERACTIVE INC
  • US9065793B2 patent drawing
  • US9065793B2 patent drawing
  • US9065793B2 patent drawing

AI summary

A first resource is provided on a user device, the first resource including a plurality of links to other resources. At least one, but not all of the plurality of links are selected for pre-caching, and at least a portion of a second resource located by the first link is automatically cached. At least the portion of the second resource is provided in response to a designated triggering event.