Render blocking CSS from third party domain

Cycling-UK / cycling-uk-application

0 stars 0 forks source link

Render blocking CSS from third party domain #22

Open j4-m opened 3 months ago

j4-m commented 3 months ago

5 render blocking CSS requests are made to https://cycling-uk-d9.cycle.travel/. Because these are cross origin requests, each has to establish a connection which introduces latency.

j4-m commented 3 months ago

@alistair-martin @sachawellborn on further investigation this appears to be more involved than I first expected. On the journey planner page there are a number of requests to cycling-uk-d9.cycle.travel and cycling-uk.cycle.travel. Unfortunately, these requests are going over HTTP1 so there's a significant penalty in opening up additional connections/multiple requests.

Do either of you know if there's a reason why these resources can't be hosted on cyclinguk.org?

sachawellborn commented 1 month ago

@j4-m @alistair-martin I suppose we could host the css on our site. This would probably be rather simple. It's the more complex mapping stuff that I doubt we would take on.

sachawellborn commented 1 month ago

@j4-m What if we retrieve the css and js libraries for the journey planner in exactly the same manner as we're doing on the route content type? Would that be ok? We already get all those libraries in for the routes. I've had a go by making a template file for the journey planner that does this. Is this acceptable for google and/or performance? https://devd10.cyclinguk.org/journey-planner

sachawellborn commented 4 days ago

@j4-m Could you confirm on that I've done this correctly? Please check at https://www.cyclinguk.org/journey-planner Thanks -

j4-m commented 3 days ago

Hi @sachawellborn. I've taken a look at the page above and the only CSS coming from third-party domains are relating to Google Fonts and TypeKit. Nice job.