Gatsbygram Case Study
11–17 of 17 posts
These are pretty amazing performance numbers. Did you account for all the bloat instagram has in the form of tracking and the likes? (I assume you didn't implement tracking in their magnitude)
Re: Gatsbygram Case Study
#12These are pretty amazing performance numbers. Did you account for all the bloat instagram has in the form of tracking and the likes? (I assume you didn't implement tracking in their magnitude)
Tracking shouldn't affect performance numbers much. The main problems Instagram seems to have is a) they don't server rendered HTML (so nothing shows until the client JavaScript is ready) and b) they don't use a service worker so the repeat visit scores aren't as good.
Re: Gatsbygram Case Study
#13I have used Gatsby for several projects at work and at home. The current version is great, and the features coming in 1.0 are even better.
At work we switched to Gatsby after trying to use another popular react starter. Our page load dropped from several seconds on slow devices to a few hundred miliseconds.
Re: Gatsbygram Case Study
#14Is it possible to add some dynamic behaviour? like update 'Likes' in gatsbygram photo.
Re: Gatsbygram Case Study
#15just chiming in to say I'm a fan of what you're doing with Gatsby - I think this is the first this-generation SSG to be good enough to replace Jekyll as the defacto :)
Re: Gatsbygram Case Study
#16just chiming in to say I'm a fan of what you're doing with Gatsby - I think this is the first this-generation SSG to be good enough to replace Jekyll as the defacto :)
thanks Jon!
Re: Gatsbygram Case Study
#17Is it possible to add some dynamic behaviour? like update 'Likes' in gatsbygram photo.
Absolutely. Gatsby sites are built with React which means it's very easy to add interactive behavior in the client that communicate with a backend API.