Windows services don't start in a specified order outside of their dependencies. Each service maintains a list of which other services must be started first (this list can be seen on the service's properties window). For example, a large number of services depend on Remote Procedure Call being started first.
If necessary, you can change the dependencies for services either through the sc command:
sc config <service name> depend= <slash-separated list> or by manually editing the registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<service name> Name: DependOnService Value: A list describing each service this service depends on. If you go about changing these dependencies trying to speed up your boot process, there's a large likelihood of causing more problems, such as accidentally making two services depend on each other. Additionally, unless the services all try to do heavy disk access upon starting (which is unlikely), adding dependencies is unlikely to help your boot speed. The kernel's process scheduler is probably going to do a better job allocating CPU time to the services than you are.
If you are trying to troubleshoot if one of these services is causing the slowdown, then I recommend using a tool such as Autoruns or msconfig to selectively disable services until you find the one causing the problem. You are less likely to cause huge problems this way, and in the worst case you should still be able to boot into safe mode and re-enable all services if everything hits the fan.