Looking into host names, at least some of the failing embedded resources, to wit:
appear to be
external, i.e. they are not an integral part of your application. You should not be even executing requests to these endpoints as they are not something you can efficiently control. Even if you find out that the slowest part of your application is request to some font there is not much you can do about it. Moreover conducting a load to resources you don't own may be considered as an attempt of a
DDoS attack which is illegal in the majority of countries.
So make sure to filter out calls to embedded resources to limit them only to the domain(s) where your application is deployed via "URLs must match" input of the "Advanced" tab of the HTTP2 Request Sampler

You can put Perl-5 style regular expressions there.
Check out Web Testing with JMeter: How To Properly Handle Embedded Resources in HTML Responses article for more information on the topic.
Just in case, be aware that you can suppress HTTP2 Request sampler failures on failing embedded resources by adding the next line to user.properties file:
httpsampler.ignore_failed_embedded_resources=true