YouTube Interface Is Painfully Slow and Unresponsive

Issue #16089123 • Assigned to Travis L.


Luke B.
Feb 25, 2018
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Go to
  2. Attempt to navigate through the UI
  3. For me, it is extremely unresponsive and slow. It takes nearly 10 seconds to BEGIN loading a page when navigated to.
  4. Hover effects on buttons do not show up because it is so slow.
  5. I am using a budget laptop from 2014 with a Celeron and 8gb RAM
  6. Using developer tools like Performance profiling are very slow
  7. Issue is only existent on
  8. This issue is also present on my other i5-6400, 8gb RAM, GTX 1050 machine
  9. The site uses nearly 50% of CPU and may spike up with no other tabs open.
  10. This problem is nonexistent on Google Chrome and Firefox Quantum

Bonus: Typing text is slow in YouTube as well. It takes 5 seconds after typing a string to begin displaying characters on the screen, which come up one-by-one 2 seconds apart for each. Sometimes the browser recovers the page when typing really fast.


1 attachment

Comments and activity

  • I can confirm that performing a reset and/or repair on Microsoft Edge DOES NOT fix the issue. A temporary fix is to restore the legacy YouTube layout from the user menu.

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. We are unable to reproduce this problem in Edge. Since this is only happening on one site, let’s start by analyzing the site traffic. To do that, please perform a fiddler trace while repeating the repro steps, then attach the resulting SAZ file so we may investigate further.

    Please note that fiddler traces can share private information such as your login to YouTube and we recommend you prefix the name of your SAZ file with the word “private” and a hyphen (e.g. private-mytrace.saz) so that the file will not be viewable by the public. You may alternatively open a new private case and attach the file there instead, then report back with the new case number.

    Best Wishes,
    The MS Edge Team

  • Hello James,

    Many thanks for taking the initiative to help me resolve this issue. I have attached the Fiddler trace I recorded from YouTube. I can confirm that this issue is somewhat less noticeable on build 17604.1000 compared to the stable 16299 build. However, it remains present. Also, when upgrading my relatives’ mid-range computer to Windows 10 16299, this issue is very noticeable.

    I hope that this trace helps.
    -Luke B.

  • Hey James,

    I just wanted to check in on the status of this issue. Please let me know, as I will be more than happy to provide extra information.

    -Luke B.

  • Hello,

    The header response times and results from look fine, so next I am looking at the response times from other hosts which load with the site, such as ad services. I will let you know what I find.

    Best Wishes,
    The MS Edge Team

  • Thanks for getting back to me.

    I’m no Microsoft Engineer, but I suspect that the problem is less of a response issue and more of an issue with the UI of YouTube using EdgeHTML. Again, it seems to be fine on Chrome and Firefox, but occurs only in Edge. (happens on work, other family members’ computers too) I’ll leave that up to your discretion ;)

    -Luke B.

  • Hello,

    Thank you for providing this information about the issue. Since it doesn’t happen to you in other browsers, I do not suspect network latency. Since it does not happen to us in our tests, I thought this might give us some clues to what you are experiencing. Unfortunately, I did not find anything unusual in the fiddler trace. Can you please use the Feedback Hub to collect more information?

    1. Open the Feedback Hub app on your device 
    2. Click on the “Feedback” tab 
    3. Click on the " Add new feedback" button 
    4. Click "Problem", fill in the title/details and select “Microsoft Edge” as the category and the appropriate sub-category 
    5. Under "Recreate the problem", press “Start capture” 
    6. Once the capture has started, run through the steps required to reproduce your issue 
    7. Click “Stop capture” back in the Feedback Hub app 
    8. Attach a screenshot of the behavior (e.g. CPU spike)
    9. Press “Submit” 

    This will provide us with a trace we can use to debug the issue further. Once you’ve submitted this, please paste a link to the newly created Feedback Hub issue in this bug so that we can link the two together and continue to investigate.

    Best Wishes,
    The MS Edge Team

  • Link to feedback hub issue:

  • Microsoft Edge Team

    Changed Assigned To to “wprpprtri”

  • Hello community,

    I have an important update on this issue. After downgrading to the latest 16299 build, I saw a noticeable performance improvement on YouTube compared to the latest “Skip Ahead” build. Some aspects of the problem I faced are still present, so I will provide an updated list of them all below:

    1. Loading uses 75-80% of CPU for just one tab, but then it will return back to the typical 2-5% after page is rendered fully. (Usually after about 30 seconds)

    2. Clicking a button/link will still slowly load pages

    3. All animations on the page seem to have a 2-3 second delay before they run.

    Thanks for your help so far.

    • Luke B.
  • Let me know if I should post an updated ticket with this new information.

  • I can now confirm that this bug affects the legacy YouTube layout in Internet Explorer. Issue is present, but less severe.
    (Issue report details have been updated to include this new info)

  • Hey, are there any updates on this issue?

  • Microsoft Edge Team

    Changed Assigned To to “Travis L.”

You need to sign in to your Microsoft account to add a comment.

Sign in