WordPress.org

Making WordPress.org

Opened 13 months ago

Last modified 4 weeks ago

#5104 new defect

Relax request limits on Showcase URLs

Reported by: jonoaldersonwp Owned by:
Milestone: Priority: high
Component: Showcase Keywords: seo
Cc:

Description

Historically, various sections of wp.org have implemented rate-limiting restrictions for performance reasons.

Many of these limitations have since been lifted/reduced, and, many performance optimisations have been put in place elsewhere.

The showcase, however, still aggressively limits requests. This may be harming our SEO, as Google frequency receives a 429 status when requesting these pages.

I'd like us to review and reduce/remove the limitations on this section. If there are performance concerns, there are myriad optimisation opportunities across the site (and in this section in particular) which we can launch before/after/in conujnction.

Change History (6)

#1 @jonoaldersonwp
10 months ago

  • Priority changed from lowest to low

This continues to cause crawling/indexing headaches.

#2 @jonoaldersonwp
9 months ago

  • Priority changed from low to normal

#3 @jonoaldersonwp
4 weeks ago

(How) can we address this?

#4 @dd32
4 weeks ago

A redesign of the showcase, both visually and code, has been on the cards for a long time. The performance issues that resulted in the rate limits here will likely persist until that's done at some point.

The majority of the performance issues the site currently experience date back to the fact that the code for it was written prior to custom post types being a thing, and it's reliance upon posts & comments and storing unstructured content within those content fields. A number of bandaids have been put on it to remove those issues over time, but nothing that could result in removal of the rate limiting.

It doesn't help that it's a common DOS target for some reason, perhaps malicious people determined it's one of the slower pages? I'm not sure.

#5 @dd32
4 weeks ago

  • Priority changed from normal to high

#6 @jonoaldersonwp
4 weeks ago

Makes sense! Nasty.
The initial server response looks pretty performant, and, since the last round of improvements to images + lazy-loading the front-end isn't too terrible. Might be worth revisiting/re-measuring some of the percieved performance bottlenecks.

Note: See TracTickets for help on using tickets.