Browser-Based Web Page Capture for Thresholded Change Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems struggle to efficiently track and analyze changes in the client-side rendering of web pages, particularly in terms of performance indicators, as they rely solely on server-side code which does not capture user experience or device-specific rendering nuances.

Innovation Solution

A computing apparatus generates client-side representations of web pages using web browser applications, calculates differences between these representations, and stores them only when changes exceed a threshold, thereby efficiently tracking performance indicators over time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If client-side representations are stored for every web page version, then complete historical performance data is available, but storage space and computational resources are wasted on redundant data

Engineering Contradiction:

Improvehistorical performance data completenessVSAvoidstorage space consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The system changes the parameter of storage frequency from constant (every version) to variable (based on difference threshold). By calculating a difference metric between consecutive client-side representations and comparing it to a threshold, the system dynamically determines whether to store data, thereby reducing storage consumption while preserving significant historical performance information.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

Instead of storing all possible client-side representations (excessive action), the system selectively stores only those that exceed a meaningful change threshold (partial action). This approach avoids the waste of storing redundant or insignificant variations while ensuring that all meaningful performance changes are captured for historical analysis.

Inventive Principle:

Principle #16Partial or excessive action

2Measurement precision

If analytics scripts run on every web page update, then all performance indicators are captured, but computational resources are wasted on unnecessary calculations

Engineering Contradiction:

Improveperformance indicator accuracyVSAvoidcomputational resource consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system changes the parameter of analytics script execution from constant (every update) to conditional (based on difference threshold). By first calculating a lightweight difference metric between client-side representations and comparing it to a threshold, the system determines whether full analytics processing is necessary, thereby reducing computational resource consumption while maintaining measurement precision for significant changes.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system performs a preliminary check by calculating the difference metric between consecutive client-side representations before executing the full analytics script. This preliminary action filters out insignificant changes, preventing unnecessary computational resource consumption while ensuring that all meaningful performance indicators are captured when changes exceed the threshold.

Inventive Principle:

Principle #10Preliminary action

3Quantity of substance

If server-side code is used to represent web pages, then code storage is efficient, but client-side rendering differences and user experience are not captured

Engineering Contradiction:

Improvecode storage efficiencyVSAvoidclient-side rendering information

Core Design Contradiction:

Quantity of substanceVSLoss of information

Solution Approach 1:

The system creates client-side representations (copies) of web pages as they actually render in the browser, rather than storing only server-side code. These copies capture the true client-side rendering including CSSOM, DOM, and visual appearance, preserving information about user experience and device-specific rendering nuances that would be lost if only server-side code were stored.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

Instead of storing server-side code and attempting to infer client-side rendering (traditional approach), the system inverts the approach by directly capturing and storing client-side representations. This inversion ensures that the stored data reflects actual user experience and rendering behavior rather than theoretical server-side output.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS20260111508A1Methods And Systems For Obtaining And Storing Web Pages

Publication Date: 2026.04.23 XERO

AI summary

A computing apparatus executes an application configured to perform a process for one or more web browser applications, each configured receive an input URL and acquire code from a web server location identified by the input URL, and generate a client-side representation of the acquired code, the process comprising: causing the web browser application to execute with a target URL as the input URL; obtaining, as a first client-side representation, a client-side representation of the acquired code as generated by the web browser application; obtaining, as a second client-side representation, a second client-side representation of code acquired from the target URL; calculating a difference metric; comparing the difference metric with a threshold, and based on the comparison: causing an analytics script to run on the target URL to obtain a set of performance indicators; and causing the first client-side representation to be stored in association with the performance indicators.