I think that you are right & you need to ask the development team for advice.
It could be that what is delivered is all the team is capable of - but I guess that is not what you think. So for some reason you think the team velocity is too low & you could be right but before anyone blow's a fuse I'll put a quote at the end to demonstrate why velocity can be wrong.
To solve the problem, firstly, you could have the next sprint(s) solely focused on this question. You will need to speak to the product owner but I'm sure they will be keen to get more work delivered so this approach may quickly pay for itself. So have the next sprint focused on improving velocity & ask the developers how this can be achieved. Don't try to tell the developers what to do, ask them what can be done. You may be surprised at the outcome.
It could be that the continuous integration/deployment processes take too long or that QA has a backlog or the team were once told that velocity when it settles down should always be the same - any number of reasons.
From Mike Cohn's book on 'Agile Estimating & Planning' he makes the following point to illustrate why if you plan too far in advance & use ideal days you could be measuring velocity wrongly in the chapter 'Choosing between story points & ideal days' (don't know your setup so this is for information):
"An estimate in ideal days can change based on the team's experience
with the technology, the domain, and themselves, among other factors.
To see why, suppose a programmer is learning a new language and is
asked how long it will take to program a small application. His answer
may be five days. Now jump forward a few months and ask the same
programmer how long it will take to develop an application that is
exactly the same size and complexity. His answer may be one day
because he has become more skilled in the language. We have a
[relative] problem now ... we would like to think that measuring velocity over time would correct or account for this problem. It won't. "
Ask the developers they will have the answer.