Performance Requirements

The Performance requirements describe the desired performance characteristics of the RapidRetail system.

Definitions

Page render
Page render is defined as all layout, visual, and text elements displayed fully, including placeholders, but not necessarily item image assets.

Goals

  1. To ensure customer satisfaction and high SEO ranking with fast performance.
  2. To allow store owners to maxnage their store expediently.

Exclusions

Requirements

Page Display
AmbitionTo ensure that pages are displayed promptly when requested by a customer so that they can complete their shopping quickly.
ScaleTime from click to page render.
MeterBrowser performance inspector when browsing to one of each type of page.
Must2000ms
1500ms
Plan1500ms
1000ms
Wish1000ms
500ms
PlatformiPhone 6s, Safari 15, LTE connection
iPhone 12, Safari 18, 5G connection

Order Confirmation Email
AmbitionTo ensure that the customer's order is confirmed to them in a reasonable time.
ScaleTime from check out button click to email reaching Postfix queue.
MeterComparison of timestamps in log from Order#create to Postfix delivery.
Must60 seconds
Plan30 seconds
Wish10 seconds
PlatformFinland

Creating an Item
AmbitionTo ensure that the store owner is able to add items to their store in a reasonable time.
ScaleTime from Create Item button click to success/confirmation page render.
MeterBrowser performance inspector for the Admin/Item#create action.
Must5 seconds
Plan4 seconds
Wish3 seconds
PlatformSafari 18 on Mac OS, Cox 150mbit line, two unedited photos from an iPhone 14 (4 MB)

Signing In (Customer)
AmbitionTo ensure that the customer can sign in quickly and return to browsing.
ScaleTime from sign in button click to home page render.
MeterBrowser performance inspector for the sign in action.
Must1500ms
Plan1000ms
Wish500ms
PlatformiPhone 6s, Safari 15, LTE connection. Cache is allowed for home assets.