5 ms·
Great that it's working for them, but for the end user the feel of the site nearly unusable. There's 1s+ of delay on every interaction - pressing "home" button
by petetnt 1y ago
Great that it's working for them, but for the end user the feel of the site nearly unusable. There's 1s+ of delay on every interaction - pressing "home" button from explore tab takes 1,85 seconds (on a gigabit connection) before home view comes active, without any other feedback to the end user except for "Home" icon becoming active.
You cannot just blindly trust the page speed metric but it should be impossible to miss things like this when you are actually using the site. Compare the experience to something like GoodReads that's using plain old SSR and you'll immediately notice the difference.
- yellow_lead 1y agoI don't have this delay personally. Probably the page speed metric is more accurate because it smooths out anecdotes like ours.
- petetnt 1y agoPage speed metric shows 5.2s for the first contentful paint for the mobile home page too: https://pagespeed.web.dev/analysis/https-hardcover-app-feed-all/pn7c0gal28?form_factor=mobile https://pagespeed.web.dev/analysis/https-hardcover-app-feed-...
- yellow_lead 1y agoI didn't realize you were trying mobile initially. When I tried mobile, it also seems incredibly slow. My desktop didn't have this issue (when going from explore page to home). Everything seems a lot slower on mobile.
- dyogenez 1y agoThat is one of the slower pages on the entire app. I'd like to move that one to use an InertiaRails.deferred setup, so it loads instantly with a loading spinner - like you'd see with Suspense + RSC. (Hardcover founder here)
- jakubmazanec 1y agoTrue, the 1s+ delays (both on mobile and desktop!) and no spinners is a very annoying UX. I've been saying this forever and this is a great reminder for those React-hating folks here on HN: usually it's the developer's fault his web is slow, not the framework's.