When HTTPS is enabled, all your assets have to be requested over HTTPS as well, otherwise you get mixed-content warnings as both secured and unsecured elements are being served up on a page that should be completely encrypted. Switch to HTTPS:
<script src="https://code.jquery.com/jquery-2.1.3.min.js"></script>
You can also use protocol-relative URLs, i.e. instead of:
<!-- this.. -->
<script src="http://code.jquery.com/jquery-2.1.3.min.js"></script>
<!-- ..or this -->
<script src="https://code.jquery.com/jquery-2.1.3.min.js"></script>
You can instead use:
<script src="//code.jquery.com/jquery-2.1.3.min.js"></script>
Using the protocol-relative syntax, the resource will load in HTTP when requested from a non-secure page, and HTTPS when requested from a secure one.
The downfall to this is that using protocol-relative schemes on non-secure pages will retrieve cross-origin assets in a non-secure fashion. This means that you could be missing out on benefits that HTTPS provides when requesting (for example) resources from a CDN, such as receiving the assets over HTTP/2*. As you're going full HTTPS this is not an actual concern, so use it at your own discretion.
*HTTP/2 does not require the use of encryption (e.g. TLS), but some implementations have stated that they will only support HTTP/2 when it is used over an encrypted connection, and currently no browser supports HTTP/2 unencrypted. (HTTP/2 FAQ)