Waiting for server response is more than 2 mins and hence there is delay in launching https URL in Windows 11 system with Microsoft Edge browser

Swathi K S 0 Reputation points
2025-06-05T10:04:18.0866667+00:00

While hosting a https URL on an IIS Server using Microsoft Edge browser in Windows 11 system (Microsoft Windows Version 24H2 OS Build 26100.2314), waiting for server response is more than 2 minutes. For processing the network requests, it takes about 120-140 seconds Win11_DelayIssue.png, because of which the page login is delayed for about 120-140 seconds. Kindly let us know if there is any resolution to fix this delay issue.

Please let us know how to optimize the waiting time taken for server response.

Microsoft Edge | Microsoft Edge development
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Tom Tran (WICLOUD CORPORATION) 525 Reputation points Microsoft External Staff
    2025-08-20T04:18:24.2666667+00:00

    Hi Swathi K S,

    Thank you for providing the details and the screenshot. From your description, the issue typically indicates a Time to First Byte (TTFB) issue, which often happens during the initial connection or TLS handshake rather than page rendering.


    Why This Happens

    • Certificate Revocation Check Delays Edge and Windows validate SSL certificates via CRL or OCSP. If the CRL distribution point is unreachable, the browser can wait up to 2 minutes.
    • Proxy or Network Auto-Detection WPAD or misconfigured proxy settings can introduce long delays before sending the request.
    • IIS Authentication Configuration If IIS uses Negotiate (Kerberos) and SPNs or domain connectivity are misconfigured, authentication can hang.
    • Security Software Interference Antivirus or firewall software that inspects HTTPS traffic can cause delays.

    You can check out these steps to optimize response time:

    Check Certificate Revocation Settings

    • Open Internet Options:
    • Press Win + R, type inetcpl.cpl, and press Enter.
    • Go to the Advanced tab → Security section.
    • Temporarily uncheck Check for server certificate revocation and test again.
    • If the delay disappears, ensure your server’s CRL/OCSP endpoints are reachable from the client.

    Verify Proxy Settings

    • Run:
    netsh winhttp show proxy
    
    • If WPAD or auto-detect is enabled, try disabling it in Internet Options → Connections → LAN Settings.

    Test with Another Browser

    • Check if Chrome or Firefox shows the same delay. If not, the issue may be Edge-specific.

    1. Review IIS Logs and Authentication
    • Check C:\inetpub\logs\LogFiles\W3SVC* for request start vs. response times.
    • If using Windows Authentication, verify SPNs and domain connectivity.

    Rule Out Security Software

    • Temporarily disable antivirus/firewall HTTPS inspection and retest.

    Reference:


    Hope this helps! If you have any more issue - please feel free to ask!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.