Loading gitlab project takes 20s to open

How to Use GitLab
1

Loading gitlab project takes up to 20s to open due to DOM content to load (more than 10k DOM content)

Gitlab-ce version 15.7.3.
Description:
For project which has been created in Gitlab, when I try to open an empty project with just a readme.MD file, it takes approximately 20 seconds to load all the contents.

Debug:
I enable the performance bar and it shows me that more than 10k DOM contents have been loaded ( see screenshot below)

1
12538Ă—1287 188 KB

2
22541Ă—1287 140 KB

3
32543Ă—1293 291 KB

Remark:
For projects which I import in Gitlab, it loads fast and have only approximately 1k DOM content loaded.

4
42560Ă—4331 689 KB

5
52543Ă—1293 412 KB

I dont know why I have more than 10k dom content for an empty project…

Thank you by advance for any help !

2

is any other projects being run through that one? if not i will keep thinking

3

Thanks for the reply ! No, there is only that one … and this “bug” occurs on all projects which are created through Gitlab.

4

um have you tried making the project on GitHub then migrate it to git lab

5

For the project which load fast, it was imported from another gitlab instance or/and imported from basic local git repository.
I don’t know why for some project like the empty project one, it needs 10k+ DOM content to load

6

maybe delte that one and remake it it could work

7

Ok I found the reason… I create an empty project in other namespace and it works perfectly.

The difference between the 2 namespaces was that I configured badges display for pipelines status. I then remove the badge display and It load perfectly.

The question now is why the badge status makes the loading page very slow…

1 Like
8

oh sorry i could not help but it is good you found the problem

9

No problem, Thank you for your help ! :smile:

1 Like
10

An idea for testing - copy the URL for the badge, replace the template variables to raw text, and run a few curl commands on the CLI with time before to see how to long the requests take. Maybe there is a performance problem with that specific HTTP endpoint (and warnings in the logs maybe).

$ time curl https://gitlab.example.com/....