Package page extremely laggy/missing CSS

[Reterino]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

Going to the Zoom Package page (https://community.chocolatey.org/packages/zoom) is extremely slow to load and then loads with broken CSS/scripts. Confirmed with a few other people that it occurs on this page for them too.

What is Expected?

Page should load as normal with other pages

How Did You Get This To Happen?

1. Opened browser
2. Navigated to Chocolatey packages page
3. Search for zoom
4. Click on Zoom Client

Or

1. Go to https://community.chocolatey.org/packages/zoom

System Details

• Operating System: Windows 11
• Windows PowerShell version: N/A
• Chocolatey CLI Version: N/A
• Chocolatey Licensed Extension version: N/A
• Chocolatey License type: N/A
• Terminal/Emulator: N/A

Installed Packages

N/A

Output Log

N/A

Additional Context

No response

┆Issue is synchronized with this Gitlab issue by Unito

[gep13]

@Reterino thank you for taking the time to raise this issue.

This is actually a known problem, and it isn't to do with missing CSS. Due to the number of package versions for Zoom, and also some associated problems with fetching the icon URL's for each package version, this page takes a LONG time to load. Typically what happens it that our CDN provider will then show a much older, cached, version of the page.

[Reterino]

Hey @gep13

The package maintainer for Zoom is also unable to update the package using his normal automatic pipeline (@mikecole), so the package is stuck pretty far out of date.

Do you know if there's a way to clean up old versions (with permission of the package maintainer) from your end to resolve this?