Assuming your load balancer (wherever it is placed) and servers are all 1 Gbit then the maximum throughput can only ever be 1 Gbit, since everything is served through the load balancer.
The load balancer, if separate from both servers, is providing failover and dividing the processing load between the servers (which for serving static files would be minimal).
In order to increase the bandwidth outbound (note, not to a single client), one would need to use something like a DNS based solution that resolved the one host name for the static assets to the two different servers. This would not provide more than 1 Gbit bandwidth to a single client, however would allow saturation of both 1 Gbit servers at full load when at least one client was connected to each. If you're doing it yourself it's more complicated to have failover since you need to remove a DNS entry if a server is down.
This is how Content Delivery Networks (CDNs) like Akamai / AWS CloudFront / many others work and what they excel at, especially when serving static content as in this use case. Dynamic and transactional content is another conversation.
If you did want to implement the DNS solution with failover yourself then you're basically building your own tiny CDN. You could roll your own or there are also DNS hosting providers who can do this as part of their service.