Designer Load Monitor
Server response time of the designer and key pages, measured every 15 minutes with plain HTTP requests from an always-on server. A robot has no slow wifi: whatever shows here is the site, not the visitor. Running since 31 Aug 2026.
Server response time (seconds, lower is better)
Designer editor page Product page Category page Homepage
Hourly medians
What a real visitor experiences on top of this (measured in a real browser, 31 Aug 2026)
- Designer editor HTML answered after 3.7 s server time; the page finished loading at 9.7 s on a fast connection.
- The editor pulls 10.4 MB across 138 requests (fonts via /CF/DynamicProduct/LoadFontFile, MegaEdit assets from resources.public.infigosoftware.rocks) before it is usable. On a typical phone connection this alone explains a 30–60 s wait.
- Hotjar session review (JC, Aug 2026): average click-to-designer wait 62–75 s; the share of visitors clicking the button multiple times doubled year over year, 10.5% → 20–27%.
- Each extra click starts another designer order in the backend. The button has no click guard, so frustrated double-clicks multiply the load.
Method: GET requests against the designer editor URL (with a session cookie since 6 Sep 2026; until then the probe was redirected to the login page and timed that instead), a product page, a category page, and the homepage; time-to-first-byte recorded per run. Raw data: designer-timings.jsonl