Improve Average Time on Page to Bali Event Calendar

[bstiawan]

Description

• Awareness chapter has reported an issue with website interaction in Bali Events Calendar page (https://www.bukitvista.com/bali-event-calendar) where there is a hypothetical dropoff due to events not being found due to filter limitations.

Problem

• When filter is set to month of X, events shown will only be the event that starts in the month of X.
• Event that spans between X-t and X+t are not shown in the result.
• Events entered will be showed less due to this issue.

Solutions

• Enhance the filters such that for selected filter X, events that are shown includes events X-t and X+t. issue
• Implement the partial load feature for PODS to improve page speed during search. issue
• Increasing the number of words to excerpt will increase reading time and there increase avg time on page. issue

Measurement metrics

• Source

Current measurements:

• From 2024-03-16 - 2024-04-16
  • Average time on page: 1:39m
  • Sessions: 3.2k
  • Drop off rate 66.4%

Timeline

• [x] 2024-04-19: Implementation deadline
• [x] 2024-04-26: Evaluation period end

SLA

• Upon completion of project, we will do measurement for 7 days.
  • [ ] Average time on page: 1:58m (20% increase)
    • 1:46m
  • [ ] Sessions: 896 sessions (20% increase)
    • Sessions: 65
  • [ ] Drop off rate 50% (24.5% decrease)
    • 72.7%

Updates

• 2024-04-29: There is no need to revert the feature despite the result.
• During then evaluation period, exactly coincides with the marketing team deprioritizing the article generation for events; From 5 events/day they completely stopped the release of new articles in the past 7 days. Which is concluded as the primary factor of the decrease in the number of sessions.
• This result will be returned to the marketing chapter, from Engineering there is no other requirement.

[Vidiskiu]

Overall Point: 5.1

Functional Complexity: 1

Enhancement to the filter functionality requires careful consideration of the logic that determines which events are displayed, which moderately increases functional complexity.

Technical Complexity: 1.1

The technical work needed to expand event filter ranges and implement partial page loads involves non-trivial back-end logic and possibly front-end adjustments.

UI/UX Complexity: 0.8

Changes to the filter will have a direct impact on the user interface, requiring UX consideration to ensure it remains intuitive.

Data Manipulation: 0.9

The solution involves manipulating event data to ensure correct display based on the new filter parameters, representing a considerable amount of data operation.

Testing: 0.3

Testing the new filter logic and page load performance is required, but tools and frameworks should be in place to facilitate this.

Dependencies: 0.5

The enhancement may rely on existing filtering libraries or frameworks, but also introduces some new dependencies for partial page loading.

Risk and Uncertainty: 0.3

There's some risk in modifying existing filters and page load behavior, but these are well-understood areas with predictable outcomes if managed properly.

User Impact: 0.2

While the change is aimed to improve user engagement, its impact on overall user experience is expected to be moderate given that it's a targeted optimization.