The HITS/s KPI reported by the report depends on your script configuration. BlazeMeter counts unique requests that appear in the JTL file generated during the test. This means that if only high level requests are present in the JTL file, the HITS/s figure relates only to the high level requests. If while configuring the test, you select to include sub-samples in your runs, thenHITS/s represents all high level requests and sub-samples (e.g. images, CSSs, JSs etc).
The way to identify how your test is configure is by the presence of the label “OTHERS”. the label “OTHERS” includes all of the samples that do not have a unique label (e.g. sub-samples).
If the test is run using a single console (no engines) – The sub-sample reporting is turned on automatically. If you use more than a single console, you need to turn this property on in order to count the sub-samples as well as the high-level requests.