Website Zone Performance Comparison System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for webpage optimization lack scalability and automation in collecting and comparing performance data across different website versions, making it difficult for website owners to assess the impact of changes and organize large volumes of data effectively.

Innovation Solution

A system and method for comparing zones of different website versions based on performance metrics, involving the collection, identification, and analysis of comparison zone metrics, which includes receiving comparison requests, collecting and analyzing user interaction metrics, and returning analysis results, utilizing a network system with an analytic server and database to automate the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual collection of performance data is used, then data can be gathered, but scalability is limited and administrative time and effort increase significantly

Engineering Contradiction:
Improvedata collection efficiencyVSAvoidadministrative time and effort
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables automated self-service data collection by implementing tracking code that automatically gathers performance metrics from website interactions without requiring manual administrative effort. The system serves itself by autonomously collecting, storing, and analyzing performance data across multiple website versions.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical data collection processes with an automated computational system. Tracking code embedded in website versions automatically captures user interaction metrics and performance data, substituting human administrative work with automated software-based data gathering and analysis mechanisms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If manual solutions are used to gather performance data, then some data can be collected, but the capacity to present different versions of a site side-by-side is lost

Engineering Contradiction:
Improvecomparison capabilityVSAvoidsystem capability
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments website performance data by discrete versions and zones, allowing individual comparison of different website versions side-by-side. Each website version is treated as a separate segment with its own performance metrics, enabling granular comparison across multiple versions simultaneously through the automated system.

Inventive Principle:
Principle #1Segmentation

3Extent of automation

If manual solutions are used, then limited data analysis can be performed, but automatic gathering of website version histories and performance metric data is lacking

Engineering Contradiction:
Improvedata gathering automationVSAvoidsystem infrastructure
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system performs preliminary automated actions by pre-collecting and storing website version histories and performance metric data before comparison is needed. Tracking code automatically gathers data in real-time and stores it in structured formats, preparing the data infrastructure in advance for automated analysis and comparison operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11593451B2System and method for comparing zones for different versions of a website based on performance metrics
Publication Date: 2023.02.28 CONTENT SQUARE SAS
  • US11593451B2 patent drawing
  • US11593451B2 patent drawing
  • US11593451B2 patent drawing

AI summary

A system and method for comparing zones for different versions of a website based on performance metrics are provided. The method includes collecting comparison versions of at least one website specified in a received comparison request; identifying at least one comparison zone in the collected comparison versions, wherein a comparison zone is a zone included in the at least one specified website; collecting at least one comparison zone metric for each of the at least one comparison zones for the collected comparison versions, wherein the at least one comparison zone metric is a numerical value related to a user interaction metric with the at least one comparison zone; analyzing the collected comparison zone metrics to determine zone performance; and returning the analysis results.