[nromiun]

That is surprising. It is the opposite for me.

  $ time curl -L 'https://codeberg.org/'
  real    0m3.063s
  user    0m0.060s
  sys     0m0.044s

  $ time curl -L 'https://github.com/'
  real    0m1.357s
  user    0m0.077s
  sys     0m0.096s

[skydhash]

A better benchmark is done through the web browser inspector (network tab or performance tab). In the network tab I got (cache disabled)

  Github
  158 requests
  15.56 MB (11.28 MB transferred)
  Finish in 8.39s
  Dom loaded in 2.46s
  Load 6.95s

  Codeberg
  9 requests
  1.94 MB (533.85 KB transferred)
  Finish in 3.58s
  Dom loaded in 3.21s
  Load 3.31s

[nromiun]

I guess Github uses a lot of cache vs Codeberg.

[Left5250]

That depends on location and GitHub pages generally take a while to execute all the javascript for a usable page even after the html is fetched while pages on Codeberg require much less javascript to be usable and are quite usable even without javascript.

Here are my results for what it's worth

  $ time curl -o /dev/null -s -L 'https://codeberg.org'

  real    0m0.907s
  user    0m0.027s
  sys     0m0.009s

  $ time curl -o /dev/null -s -L 'https://github.com/'

  real    0m0.514s
  user    0m0.028s
  sys     0m0.016s

[nromiun]

Sure, it depends on your internet connection. But for Codeberg I see a blank page for 3-4 seconds until it shows something. On a big repo like Zig the delay is even worse.

On Github any page loads gradually and you don't see a blank page even initially.

[chrisbrandow]

Try changing tabs when reviewing a PR. 5-10 seconds on basic PRs often

[reppap]

GitHub frontpage is very quick indeed, but browsing repos can sometimes have load times over a full second for me. Especially when it's less popular repos less likely to be in a cache.