Closed clhenrick closed 4 years ago
On the individual park pages (/park/:id
) this appears to be caused by the delay in loading a selected park's GeoJSON boundary and related images. For large / complex park boundaries such as National Forests, this can take a while, 13 seconds on a fast internet connection even! However I noticed that subsequent loads after clearing my browser cache were much faster.
My suspicion is that the server side rendering is delaying the initial page load (or doing something along those lines) until data for park images and the park geometry are returned. Still wrapping my head around server side rendering so may come to a different conclusion later.
Wondering why the header images are sent to the client before anything else is? This results in a mega FOUC. Perhaps there was rationale for this that I'm not currently aware of.
@mojodna @sconnelley any insights to this?