End User Timing Accuracy Across Browsers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Monitoring end user timing across multiple platforms and network browsers is challenging due to differences in device specifications and browser compatibility, making it difficult to compare and report accurate user experience metrics.
Innovation Solution
The technology captures end user timing data using navigation timing standards and handler callback functionality, analyzing and reporting the most accurate data by comparing metrics from handler objects and browser interfaces, and utilizing timestamps from callback calls to determine periods of user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple metrics collection techniques are used across different browsers and platforms, then coverage and data availability are improved, but data accuracy and consistency deteriorate due to platform-specific variations
Solution Approach 1:
The system implements multiple metrics collection techniques (excessive action) including handler callbacks, navigation timing API, and performance timing API simultaneously. By collecting more data than strictly necessary from multiple sources, the system ensures compatibility across different browsers and platforms while maintaining the ability to select the most accurate timing data for each specific context
Solution Approach 2:
The system dynamically changes the measurement parameters and data sources based on the specific browser and platform environment. It selects which metrics collection technique to use or prioritize based on platform capabilities, thereby adapting the measurement approach to maintain accuracy across diverse environments
2Measurement precision
If handler callback functionality is implemented to capture timing data, then timing measurement capability is improved, but system complexity increases due to multiple event handlers and callback mechanisms
Solution Approach 1:
The system implements a universal monitoring framework that can handle multiple timing measurement techniques through a common architecture. The handler callback mechanism is designed to work alongside navigation timing and performance timing APIs, providing a multi-functional solution that reduces overall system complexity by unifying the approach to timing measurement across different browser capabilities
3Loss of information
If metrics are captured from both handler objects and browser interface, then data availability is improved, but data processing complexity increases due to comparison and validation requirements
Solution Approach 1:
The system implements feedback mechanisms where metrics from handler objects and browser interface are continuously compared and validated against each other. This feedback loop allows the system to identify and correct discrepancies, ensuring data quality while providing comprehensive timing information from multiple sources
Data Source
AI summary
A system automatically determines end user timing across multiple platforms and network browsers. End user timing data may be captured using one or more techniques. The techniques may include utilizing a navigation timing standard and handler call back functionality. The end user timing data may be analyzed to identify which technique's data is most accurate, and the most accurate end user timing data is then reported.