LGPL is not GPL 
LGPL is a privative license (quite similar to Apache 2.0) there is no problem with it can be statically linked / compiled in the same binary as the rest of a web application even if you create a privative binary.
GPL is a free license (also called copyleft) there is no problem with it can be statically linked / compiled in the same binary as the rest of a web application but this web application become free. With GPL you just have to give the source code to the users of the application (only the users not the world wide).
Note that only make the application whom linked/compiled free, not other libs used by the application, but while you must give them source code to users they must be open sourced (but it’s legally ok if some have copyright)
Mains copyrighted open source license are LGPL, MIT, BSD, Apache2
Mains free open source license are, from the less to the most restrictive) MPL, GPL, AGPL
In short:
You can include GPL libs in AGPL or GPL libs.
You can include LGPL, MIT, BSD, Apache2 libs in MPL, GPL or AGPL libs
You can include MPL libs in LGPL, MIT, BSD, Apache2 without license change
You cannot include GPL or AGPL libs in LGPL, MIT, BSD, Apache2 libs without modifying the license to the most free one 