"LIMIT 10" hides part of the issue. Remove that, and you will probably find that "futbol" occurs a lot more than "baloncesto". Since the query has to do at least one "filesort" (I think it is doing two), it has to collect more rows for "futbol", hence takes longer.
You have a lot of indexes; this probably slows down INSERTs, but perhaps not enough to matter. Even so, the one that I think is useful is missing:
INDEX (SITE, SECCION, TIMESLOT), or
INDEX (SECCION, SITE, TIMESLOT)
What is the value of innodb_file_per_table? I suspect it is 0. (If it is 1, then I need to bring up another topic.)
If you have not increased innodb_buffer_pool_size from the default, then please read this; it may improve performance significantly:
http://mysql.rjweb.org/doc.php/memory
(That's why I asked for SHOW VARIABLES LIKE '%buffer%';)
With only 155MB of data, I would not expect such long query times unless it is unnecessarily hitting the disk.
When you run timings, I suggest you run each test twice in a row. The first time _may_ be hitting the disk to get blocks that are not cached (in the buffer_pool); the second time should be more useful as an indicator of efficiency. (Thanks for doing RESET QUERY CACHE; that eliminates it from the equation.)