5 ms·
At Tock we had been obsessed with page load performance since the beginning and I agree with the author. We avoided PWA mostly due to it's broken behavior. Oft
by robinanil 8y ago
At Tock we had been obsessed with page load performance since the beginning and I agree with the author. We avoided PWA mostly due to it's broken behavior. Often times we are faster than loading the same restaurant page on Google search.
Out challenge has been that we have to load a lot of images, so we spent a lot of time optimizing everything around it and optimizing everything around it. From TLS1.3 to the CDN, to every part of our stack.
Try it out
https://www.exploretock.com https://www.exploretock.com
https://www.exploretock.com/tfl https://www.exploretock.com/tfl
- robinanil 8y agoAlso ours is not a static page, it has dynamic content, and ga + fb tracking for our restaurants and we make it work by correctly prioritizing important rendering elements over other
- robinanil 8y agoWe have also spent time reducing the initial JS parsing size by chunking out our ever growing JS bundle and we constantly test on slow devices on 2g/3g profiles to emulate bad internet conditions. We have learned a lot in the process probably good for a blog post
- 43920 8y agoSort of off-topic, but there seems to be a bug with the way search results work. If I click on "search", it shows me an option for "<my city name> nearby", but if I click on that, I get results for a city that has the same name, but is in a completely different area. edit: this also applies to the "near you" cards on the home page.
- robinanil 8y agoThanks, could be a geocoder issue for a specific city - we will investigate.
- mychael 8y agoVery fast indeed. Hard work paid off!
- bill_mon 8y agoNo images without javascript? Imo js should be for functionality only, basic content should always load.
- robinanil 8y agoTrue critique, but progressive loading is not supported by html5 alone. I have been following up with srcset to support proper lazy loading behavior and the day it gets supported you will see it on our site.
- bill_mon 8y agoI understand the problem and I don't have a good solution -- does srcset really help here? How about a browser setting where the user can decide whether to load images only when they are seen?
- robinanil 8y agoHow about it is made the default behavior in any browser, I see no reason why image downloading should ever be not lazy and viewport dependent
- Uw7yTcf36gTc 8y agoits in the pipeline for chrome. should be in testing or dev soon enough.
- ec109685 8y agoScroll a little, click a link and then swipe back. Back button doesn’t work.