Frontend App Load Time Optimization via Dynamic Page Tree Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based software platforms face challenges in reducing apparent load times for frontend applications due to the transmission of infrequently used elements, styles, and scripts, which consume bandwidth and client-side resources.

Innovation Solution

A backend application uses a page request response conditioning service to determine the optimal order for transmitting elements of a page tree, prioritizing frequently used elements and deferring less frequently used ones, thereby optimizing apparent load times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all elements, styles, and scripts are transmitted to the frontend application, then functionality and completeness are ensured, but bandwidth consumption and client-side resource utilization increase

Engineering Contradiction:
Improvefunctionality completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the page elements into frequently used and infrequently used categories. The backend application analyzes usage patterns and transmits only the essential elements first, separating critical content from optional features. This segmentation allows the system to reduce bandwidth consumption while maintaining core functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by transmitting only the necessary subset of elements, styles, and scripts based on usage analysis. Instead of sending the complete set of resources, the system sends a curated partial set that satisfies user needs, thereby reducing bandwidth consumption and client-side processing requirements.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If all elements, styles, and scripts are transmitted to the frontend application, then functionality and completeness are ensured, but page load time increases

Engineering Contradiction:
Improvefunctionality completenessVSAvoidpage load time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments page loading into phases: first transmitting frequently used elements, styles, and scripts to achieve rapid initial load, then loading infrequently used elements on demand. This segmentation dramatically reduces perceived page load time while maintaining complete functionality through lazy loading of optional features.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by pre-transmitting and pre-processing frequently used elements before the user needs them. The backend analysis identifies and prepares essential resources in advance, so they are ready for immediate execution, reducing the time to first meaningful display and improving overall perceived performance.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If infrequently used elements are transmitted to the frontend application, then bandwidth and resources are consumed, but user experience is improved

Engineering Contradiction:
Improveuser experienceVSAvoidbandwidth consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent implements dynamic resource transmission based on real-time usage patterns. The system continuously monitors which elements are actually used and adjusts subsequent transmissions accordingly. This dynamic approach ensures that bandwidth is allocated to elements that provide user value, improving ease of operation while minimizing wasted resources on unused features.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs feedback mechanisms where the frontend application reports actual usage of transmitted elements back to the backend. This feedback loop enables the system to refine its element selection algorithms, transmitting more relevant resources in future sessions and reducing bandwidth consumption on infrequently used elements while maintaining excellent user experience.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12321757B2Decreasing apparent load time for a frontend application when requesting a page from a backend application of a multiuser collaboration tool
Publication Date: 2025.06.03 ATLASSIAN PTY LTD
  • US12321757B2 patent drawing
  • US12321757B2 patent drawing
  • US12321757B2 patent drawing

AI summary

Systems and methods for servicing page requests from a cloud-based software service. In particular, page tree elements defining a page requested from a backend of a cloud-based software service can be can be transmitted to a client device that originated the page request and loaded, client-side, in an order that prioritizes, in one example, features and functionality used most frequently by a particular user of the cloud-based software service.