Hey everyone, has anyone else been hitting a wall with painfully slow load times in Hyperproof's evidence repository lately? 😅
I'm running our compliance workflows through it, and when my team needs to upload or review evidence, the lag is becoming a real bottleneck. We're talking 10-15 seconds sometimes just to open a folder or preview a PDF. It's especially noticeable compared to other modules, which seem snappy.
A few things I've noted:
* It happens across different file types (images, PDFs, spreadsheets).
* Our instance isn't huge—maybe a few thousand evidence items total.
* We've tried different browsers and cleared caches, so it doesn't seem client-side.
I'm passionate about smooth automation, and this kind of delay really interrupts the flow for our auditors. Before I dive deeper with support, I wanted to check if this is a common experience or if it's just us. Any workarounds or config tweaks you've found helpful?
Keep automating!
Keep automating!
I ran some informal timings on our instance last month because I thought the same thing. My results were weird. The slowness wasn't universal. Opening a folder with 50 PDFs? Fast. Opening a single image in a folder with a mix of file types? Consistently slow.
That tells me it's not about raw data volume. Something is happening with their file indexing or preview generation when you have heterogeneous content. It feels like a lazy loading problem where they're scanning something on each individual file open.
Before you go to support, check if the lag is worse on files uploaded in a certain date range. Ours was terrible for anything uploaded before their Q3 platform update.
-- bb
We had the same issue. Your note about it being isolated to the repository is key - it points to a backend indexing or storage problem, not general platform load.
Our workaround was to batch download anything needed for an active audit review to a secure local folder. It defeats the purpose of a live repository, but it kept the auditors moving.
Hyperproof support will likely blame your network or ask for HAR files. Push them to check their object storage latency metrics and evidence table indexing for your tenant. Ours improved after they rebuilt our index, but it crept back over a few months.
Where is your SOC 2?