i think it’s an inherent limitation of pagespeed, since wefwef is not serving 1st-party content. the first contentfull load will be after the backend wefwef queries responds, which in this case took several seconds. there’s nothing the client can do about that, except for changing backends