Dev Stack Source

Answer : To directly answer the question, no it's not impossible to get a fast FCP label. There's more to the question so I'll try to elaborate. Another way to phrase the "fast" criteria is: "Do at least 90% of user experiences have an FCP less than 1 second ?" Why 90%? Because it's inclusive of a huge proportion of user experiences. As the PSI docs say: Our goal is to make sure that pages work well for the majority of users. By focusing on 90th and 95th percentile values for our metrics, this ensures that pages meet a minimum standard of performance under the most difficult device and network conditions. Why 1 second? It's a subjective value for how quickly users expect the page to start showing meaningful progress. After 1 second, users may become distracted or even frustrated. Of course the holy grail is to have instant loading, but this is chosen as a realistic benchmark to strive towards. So at worst 10% of the FCP experien...

Answer : Socket/Connect and Read/Response timeouts can be set from Http Request Defaults section at jmeter GUI. See sample: Connect timeout: 3 seconds Response timeout: 20 seconds. For your need, an assertion is not the right solution as it will only mark the request as failed but it will wait. The right option is a response timeout. Regarding the 3rd point os_sampler.poll_for_timeout=x => not for http, see: https://github.com/apache/jmeter/blob/master/bin/jmeter.properties http.socket.timeout=x => applies to all requests using HttpClient4 or 3, see: https://github.com/apache/jmeter/blob/master/bin/hc.parameters httpclient.timeout=x => Same, see: https://github.com/apache/jmeter/blob/master/bin/jmeter.properties I think the best option is to use 1. , if you want those values to apply to all requests, just use Http Request Defaults element: https://jmeter.apache.org/usermanual/component_reference.html#HTTP_Request_Defaults If you're looking to learn jmeter correctly, t...