If you have more than 3k changes the UI just informs you it won't show you the remainder. C'mon Github, can't we do better than that?

I used to switch from Safari to Chrome for a small performance boost on huge PR's.

Today Chrome is also choking. I am literally unable to review large PR's :(

I am also having this problem. We had a refactor that could only be done in a single PR w/o breaking the code in the repo. We had ~2,200 files changed in the PR. Why isn't there some sort of paging that exists?

Even a couple hundred files renders the UI extremely slow - filtering a tree with 200 entries shouldn't require locking up the browser for 10-seconds.

I can confirm that Firefox works great. Here's my pull request:

Chrome was stuck when I switched to the Files changed section while Firefox works like a charm.

I compared memory usage. Chrome comes up to 2GB, while Firefox is most of the time 0.7 - 1GB on the same page.

I have a pretty mild PR compared to some of these examples (1200 files, 1700 changes) and Chrome outright crashes, and firefox seems barely any better if at all.

Feels like this gets worse with every Github update. Please fix this, this has the potential to make people move to other tools.

I've been using mostly Vivaldi except when I need to review PRs because it lags there. For viewing PRs I use Chrome but it's lagging now there too.

The PR is not that big, 3,700 additions, 1800 removals. I've worked with much larger PRs without lag in the past.

I'm having the same issue here using Chrome. I tried using Firefox as a temporary solution to this lag situation, and it works only partially. Marking items as 'viewed' is fine, but searching for comments through the 'jump to conversation' feature doesn't work on both crashing the app.

Hope someone can solve this issue asap. 🤞

Still a huge issue. I've been using Brave and for PRs with >1000 files, despite filtering out to have only ~100 files, there's a huge lag, the Ui is unresponsive, Brave keeps asking me to kill the tab.

I can also confirm tested today with a PR of 2600+ it was snappy on firebox, but really slow on chrome.

on FF the only thing a little slow is when adding a comment to a line of code, but still much better than chrome.

Just experienced this today with a PR having ~800 files changed. Sadly, it is unbearable to work with.

+1 on this, Safari is particularly painful on PRs with 100+ files

I think that a quick fix would be to have all the changes collapsed when the PR is over N files/changes long, and that might make it better.

Other ideas would be to have some dynamic pagination on the page which only shows some files and the rest are kept on a display hidden, might cause some scrolling bumps though when switching between them 🤔

Our team is having this issue with PRs with only 40 changes, it's annoying to review anything in there.

Is there any way we can get this escalated?

Experiencing the same issue in safari. Incredibly unresponsive UI when reviewing PRs.

This is so bad. Unbelivable. We were planning from switching from ADO to GitHub but this is unusable. How're people using this service?

This is still a very real issue, there's around 5 seconds of delay when doing anything on a pull request with about 200 files for me on Firefox.

For what it's worth if you're using VSCode, the performance using the Github Pull Requests plugin is excellent and gives access to more tools while reviewing. I'll be switching to this method until they figure things out.

Temporary solution: Do not use the “Create Auto Pull Request” button. Instead, the user should click “New Request”, then select the target branch and the compare branch to proceed.

Still an issue, yawn!

I've noticed this message start appearing, and also the performance may indeed have improved.

This page has been optimized for large pull requests. Some browser features (like Find on Page or Select All) may not work as expected.

Still horrendous

Maybe they've fixed it??

I had a large PR 2 days ago and it seemed to be reasonably reponsive.
Also this message box has started appearing 'This ... has been optimised for large PRs' - so microsoft are aware of the issue!

Could others test and see if they are getting the same problem still?

--- ticket response below ---

Please do not write below this line

Your request (Ticket 4386935) has been updated.

To review the status of your request and add additional comments, please visit: Ticket 4386935.

Rick (GitHub Support)

May 15, 2026, 7:27 PM UTC
Hi there jonholdsworth,

Sorry to hear you are experiencing issues when using GitHub.com.

Based on the information you have provided, I was unable to replicate this issue using a chrome browser. Is there any chance you could have conflicting browser extensions that may be causing this behavior?

If you visit the page again with browser extensions disabled or in an incognito/private browsing window, or in another browser, do you experience the same trouble?

This can also sometimes occur when accessing GitHub using an outdated browser. Likewise, sometimes using a future Dev or Beta release can account for the same behavior. Browser versions update so frequently we recommend verifying that you're using the latest stable release of a supported browser.

With any luck, one of these options should resolve this issue, but please do let me know if you continue to run into any further trouble.

If you could confirm the exact browser version and operating system you're using as well as that would be most appreciated.

It would also be very helpful for us to see a screenshot of the Console view in your web browser.

Google Chrome Console Overview
Use the developer tools in the Develop menu in Safari on Mac
Firefox Browser Console Overview

Hopefully there will be something in either the console or network logging that can help shed some light on this.

Once I have more information, I'll certainly do my best to help! 😁

All the best,
Rick

GitHub Support

Still happening.

Try opening the 300+ comments at the end in Linux chrome.

oven-sh/WebKit#249

I've replied to their ticket with that url.