Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#52237 closed defect (bug) (invalid)

WordPress performance

Reported by: websirs's profile websirs Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.6
Component: General Keywords:
Focuses: performance Cc:

Description

Hi WordPress,

Concerned about WordPress performance.

We are working with eCommerce stores using WooCommerce and due to issues like websites going down when there's more traffic we have to look into the performance.

What we are seeing using the tools provided by Kinsta for example, is that when we are loading the homepage of the website.

WordPress is going through so many processes, we can see almost all our plugins names being called by different functions.

And these plugins don't really need to load on the homepage and they don't really exist there either (as in nothing usable from them on that page for example)

Why do we need to load everything or allow everything to be loaded on all pages causing a massive delay between a request and a response while PHP is trying to process all of this useless requests?

What's stopping us from making WordPress super fast?

Obviously there is a point where we need to upgrade servers and that's fine, right now it seems we are not being efficient.

What do you think?

Thank you

Change History (2)

#1 @dingo_d
4 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Hi! This doesn't seem like a core related question, and you should better ask it in the support forums :)

https://wordpress.org/support/forums/

#2 @peterwilsoncc
4 years ago

  • Focuses coding-standards removed
  • Milestone Awaiting Review deleted
  • Severity changed from major to normal

As mentioned, this is best asked in the forums.

In basic terms, it's up to each plugin to determine which code it needs to run on each WordPress page. It's a common programming conundrum that the only way to determine if executing code will have an effect is to allow the code to execute.

Reaching out to the plugin developers with performance suggestions may help too.

Note: See TracTickets for help on using tickets.