Hi borodatiyPupok,
The image you sent shows the static lib only. To see the true size of an application could you try compiling the application that will statically link to wolfssl.lib and check the resulting size of the app? The static lib will contain many portions of code that will get optimized out in an executable. Also I suspect you may be building one of the Debug builds with the size you are seeing. In MSVS go to "Build->Configuration Manager...-> set wolfssl to "Release" ".
To illustrate I'll include the build sizes I see with DEBUG and RELEASE builds and also compare the lib size to the executable size:
DEBUG BUILD for x64:
-rwx------+ 1 boz_windows None 839680 Oct 24 08:19 testsuite.exe
-rwx------+ 1 boz_windows None 608332 Oct 24 08:19 testsuite.ilk
-rwx------+ 1 boz_windows None 1338368 Oct 24 08:19 testsuite.pdb
-rwx------+ 1 boz_windows None 1940904 Oct 24 08:19 wolfssl.lib
lib = 1,940,904 (nearly 2 Mb)
testsuite.exe = 839,680 (839K)
NOTE: The .lib is much larger than testsuite.exe but testsuite.exe is compiled with the static library. You can see much of the code was optimized out for testsuite.exe
RELEASE BUILD for x64:
-rwx------+ 1 boz_windows None 390144 Nov 14 12:46 testsuite.exe
-rwx------+ 1 boz_windows None 969728 Nov 14 12:46 testsuite.pdb
-rwx------+ 1 boz_windows None 3346028 Nov 14 12:46 wolfssl.lib
lib = 3,346,028 (3.3 Mb)
testsuite.exe = 390,144 (390K)
Even though the .lib is larger in release mode you can see the executable is far more optimized (839k to 390k) so the size was reduced by more than half. I did these tests with the default configure settings of the windows project. Please try comparing the same with your configure settings and let me know the results.