#107386PageTree rendering becomes significantly slower with expanded subtrees
Description
With more items in the pagetree loaded and displayed, the pagetree itself becomes slower and less reactive until normal editing is not possible.
I recognized this problem in 2 different customer projects on different infrastucture and can also reproduce this in a clean ddev setup.
I know that the pagetree rendering was rewritten in v13, but the old pagetree was a lot faster when dealing with many pages.
Steps to reproduce:
- have a pagetree with lots of pages and start expanding the subtrees
- the more pages are loaded, the slower the pagetree becomes
- scroll up and down the pagetree, it takes several seconds until the pagetree is displayed
- expanding further subtrees takes also some time, until the changes are reflected in the pagetree
I have attached an SQL file with about 600 pages, where the effect becomes observable, when all subtrees are expanded. The export comes from a clean ddev installation with
ddev composer create "typo3/cms-base-distribution:^13"
on PHP 8.2.
If I scroll up and down, it takes >1s until the pagetree is rendered. From my point of view it’s not a backend problem, as the timings for ajax-fetching the pages are always the same (<100ms with my setup) and the delay comes from rendering the response by the web-component. I also observed the same problem on PHP 8.4.
With more expanded pages, the delay increases to several seconds. The same amount of expanded pages is significantly faster with pagetree in TYPO3 v11.
Reviews 3
Related issues 1
Files 3
History 1623
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2025-09-03T16:31:16+00:00" > 09/03/25, 16:31 </span> -
Tim Horstmann commented <span data-processor="relativetime" data-value="2025-09-04T06:19:08+00:00" > 09/04/25, 06:19 </span>
Hardware- Windows 11 Enterprise
- i7-1185G7 (Lenovo Thinkpad T14 Gen 2i)
- Firefox 142.0.1 (with some addons, with all addons deactivated)
- Firefox 142.0.1 Inkognito Mode without addons
- Chrome 139.0.7258.127 without addons
The issue was also confirmed by 2 colleagues of mine, that are on macOS.
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-09-04T06:22:45+00:00" > 09/04/25, 06:22 </span>
OK thanks, I just wanted to rule out hardware/browser issues. It’s quite fast on my “large pagetree” setup, but I’ll check out your dump and try to reproduce. Will also check on main (v14) because I vaguely remember sonething with pagetree there.
-
Sven Liebert commented <span data-processor="relativetime" data-value="2025-09-04T06:25:54+00:00" > 09/04/25, 06:25 </span>
I can confirm that. We have a client with over 6000 pages in page tree. The loading time increases when opening more and more pages/directories.
Hardware- MacBook Pro 2023 (M2 Max, 64 GB RAM)
- macOS 15.6.1
- Google Chrome 139.0.7258.140 in incognito mode without addons
-
Garvin Hicking commented and changed status
Needs FeedbackAccepted <span data-processor="relativetime" data-value="2025-09-04T07:42:13+00:00" > 09/04/25, 07:42 </span>Acknowledged, reproduced on v14/main even on my beefy ;) MBP M4 Pro.
-
Lorenz Ulrich commented <span data-processor="relativetime" data-value="2025-09-18T14:59:25+00:00" > 09/18/25, 14:59 </span>
Same problem here with a larger TYPO3 instance, don’t know yet what causes it, but a pretty big problem.
-
Daniel Huf commented <span data-processor="relativetime" data-value="2025-09-19T14:16:47+00:00" > 09/19/25, 14:16 </span>
Same issue here also.
Did you try to reduce the
protected int $levelsToFetch = 1;in the vendor/typo3/cms-backend/Classes/Controller/Page/TreeController.php
That helped a bit for us, at least until a better solution is found.
-
Florian Seirer commented <span data-processor="relativetime" data-value="2025-10-02T11:46:36+00:00" > 10/02/25, 11:46 </span>
I can confirm this behaviour on our biggest site with 13000+ pages: The more you expand the page tree, the slower it gets. Eventually, the browser just gives up and crashes.
This is also true for the category tree, where we have about 250 different categories. Not as bad as with the page tree, but still noticable.
This prevents us from updating to TYPO3 13.
-
Simon Eller commented <span data-processor="relativetime" data-value="2025-10-21T08:06:35+00:00" > 10/21/25, 08:06 </span>
We can confirm this new behavior during updates in our customer’s website staging environments with relatively small page trees of 900 pages.
Especially when searching for page titles, where large parts of the page tree expand, the request to /typo3/ajax/page/tree/filterData alone takes 20 seconds (in Typo3 12 it takes 1.5 seconds). Scrolling causes CPU usage exceeding 20%, and the browser tab (Firefox on Windows 11) freezes. -
Rafael Kähm commented and changed attached TYPO3_PageTree_performance_trouble.webm <span data-processor="relativetime" data-value="2025-10-22T12:58:12+00:00" > 10/22/25, 12:58 </span>
We can confirm it as well, the editors can not work properly since upgrade(two months) to TYPO3 13
Don’t know how to embed the video here: please see
TYPO3_PageTree_performance_trouble.webmin attachments. -
Gerrit Code Review pushed patch set 1 for main to change 91284 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-10-27T17:59:15+00:00" > 10/27/25, 17:59 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91284 <span data-processor="relativetime" data-value="2025-10-27T18:28:31+00:00" > 10/27/25, 18:28 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91284 <span data-processor="relativetime" data-value="2025-10-27T20:18:47+00:00" > 10/27/25, 20:18 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 91284 <span data-processor="relativetime" data-value="2025-10-28T09:52:22+00:00" > 10/28/25, 09:52 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 91284 <span data-processor="relativetime" data-value="2025-10-28T10:30:38+00:00" > 10/28/25, 10:30 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 91284 <span data-processor="relativetime" data-value="2025-10-28T11:02:39+00:00" > 10/28/25, 11:02 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 91306 <span data-processor="relativetime" data-value="2025-10-28T11:17:38+00:00" > 10/28/25, 11:17 </span>
-
Benjamin Franzke commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-10-28T11:50:09+00:00" > 10/28/25, 11:50 </span>Applied in changeset commit:403d402cd91be5a703f6a91f030799fe31c07707.
-
Florian Seirer commented <span data-processor="relativetime" data-value="2025-10-28T13:40:22+00:00" > 10/28/25, 13:40 </span>
I just applied the patch, and scrolling in a looong page tree now works without delay. Thanks!
Filtering the pagetree is also faster than before, but can take up to 3 seconds in my case.
Clearing the filter still takes 12+ seconds for the page tree to return to the unfiltered state, though.
Also faster than before, but there might still be room for improvement. A visual clue that the pagetree is being generated might also help. -
Ayke Halder changed Related to #106182 <span data-processor="relativetime" data-value="2025-10-28T14:48:49+00:00" > 10/28/25, 14:48 </span>
-
Ayke Halder commented <span data-processor="relativetime" data-value="2025-10-28T14:55:23+00:00" > 10/28/25, 14:55 </span>
Maybe this one further improves the performance:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/88229/ -
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T13:58:21+00:00" > 12/02/25, 13:58 </span> -
Ayke Halder commented <span data-processor="relativetime" data-value="2026-11-13T08:12:44+00:00" > 11/13/26, 08:12 </span>
Some more improvements to solve calling `findLast()` on all tree-nodes in a loop:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/91284/comments/d11daad0_78c4b269
Can you please describe your environment: hardware (client), browser (version and model), OS (version and model), possible browser extensions (something like 1pass, dev tools).
Did you also try this in incognito mode (no browser plugins) ?