erichartline
commented
3 years ago Our LCP element (largest image or text block visible within the viewport) is
The Dicty Stock Center is a rapidly growing central repository for Dictyosteliu…
<p data-key="1">LCP is primarily affected by four factors:
- Slow server response times
- Render-blocking JavaScript and CSS
- Resource load times
- Client-side rendering
Slow server response times
- We have one slow response time for the homepage, and that is for retrieving the number of strains and plasmids. This needs to be taken care of in
modware-stockas reflected in this issue. - We can set up a custom service worker with a cache-first policy.
- We can establish our connection to the GraphQL server early by using
rel="preconnect".
Resource load times
- Optimize images (slideshow and dicty logo). We already use ImageBot to compress images, but our report suggests we could do even more.
- Look into Brotli instead of using gzip?
- Also suggests the service worker
Client-side rendering
- Bundle size. Our biggest culprit in our bundle is the page editor. This is even more incentive to upgrade to the latest version of Slate. Our version,
0.4x, is 187.3kb, whereas the newest version is at 72kb. This would drastically lower our bundle size alone.
Our desktop report shows LCP of 1.2s, which is good according to Google's criteria (under 2.5s). However, it can likely be improved. This issue will be used to track progress.