Third-party Tag Acceleration via Nanovisor Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Third-party tags on webpages, such as advertisement and analytics tags, introduce latency and impact the loading speed of first-party content, affecting revenue and user experience.
Innovation Solution
Implementing a system that accelerates the delivery of performance-sensitive third-party tags while deferring non-performance-sensitive ones, using a Nanovisor to intercept and modify resource requests and DOM operations, and employing HTML streaming and content transformation techniques to optimize tag delivery without compromising first-party content performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If third-party tags are loaded to deliver advertisements and collect analytics, then revenue and marketing insights are improved, but page loading speed deteriorates
Solution Approach 1:
The patent segments third-party tags into different categories (e.g., ads vs. analytics) and applies different loading strategies to each segment. Performance-sensitive tags like ads are loaded eagerly to maximize revenue, while non-performance-sensitive tags like analytics are loaded lazily to preserve page load speed. This segmentation allows the system to optimize for revenue without uniformly sacrificing performance.
Solution Approach 2:
The patent implements dynamic loading decisions based on runtime conditions. The system adjusts tag loading behavior according to factors such as user interactions, network conditions, and page state. For example, tags may be loaded immediately when certain user actions occur (like clicking a link) rather than waiting for initial page load, enabling the system to adapt loading timing to maximize revenue while maintaining perceived performance.
2Productivity
If third-party tags are loaded immediately, then tag performance is improved, but first-party content performance deteriorates
Solution Approach 1:
The patent divides third-party tags into performance-sensitive and non-performance-sensitive segments. Performance-sensitive tags (ads) are loaded immediately to maximize revenue opportunity, while non-performance-sensitive tags (analytics) are deferred until appropriate moments. This segmentation enables the system to improve tag delivery performance for critical tags without compromising first-party content loading speed.
Solution Approach 2:
The system incorporates feedback mechanisms that monitor page load progress and user interactions. Based on this feedback, the system dynamically adjusts tag loading timing. For example, if the user interacts with the page before analytics tags are loaded, the system may prioritize loading those tags immediately. This feedback-driven approach ensures that tag performance is optimized without consistently sacrificing first-party content performance.
3Productivity
If all third-party tags are loaded simultaneously, then revenue optimization is improved, but page load time increases
Solution Approach 1:
The patent segments third-party tags by performance sensitivity and applies differentiated loading strategies. Performance-sensitive tags are loaded immediately to maximize revenue, while non-performance-sensitive tags are loaded lazily. This segmentation enables the system to optimize revenue from critical tags without incurring the full penalty of loading all tags simultaneously, thereby reducing overall page load time.
Solution Approach 2:
The system performs preliminary actions by pre-loading or pre-positioning performance-sensitive tags in a ready state before they are actually needed. This allows the browser to prepare ad tags in advance without blocking the initial page load, as the tags are already prepared to execute immediately when triggered. This preliminary preparation optimizes revenue potential while minimizing the impact on perceived page load time.
Data Source
AI summary
A method of delivering a webpage is disclosed. It is determined that delivery of at least a portion of third-party content associated with a webpage is to be accelerated. One or more pre-conditions to be met prior to the delivery of the accelerated third-party content are determined. A loading order configuration for the webpage is determined based at least in part on the one or more pre-conditions. At least a portion of the webpage that modifies a loading order of content portions of the webpage is determined based on the loading order configuration.