New answers tagged

0

There are no doubt a lot of factors at play when talking Wordpress performance optimization. Implementing a caching plugin and a CDN are certainly great options for accelerating your site speed. A CDN will help speed up your static content globally, will help with scalability, among many other things. A caching plugin will generate a static HTML file of ...


0

As Antony Gibbs noted the caching plugin will work best if you have rarely updated content. This is in my experience a key factor to caching tools. As for using a CDN, I use Cloud Flare on a few of my busier sites and the analytics screen from Cloud Flare regularly shows that I save an average bandwidth anywhere between 30%-60% depending on the type of ...


0

It determines which exact resources do you measure. Retrieving feed is essentially a network request. Making network request isn't CPU or memory intensive, but it is relatively very slow. Depending on limitations and configuration of specific hosts it might or might not be a problem. Also feeds are natively cached. However if cache if flushed in use cases ...


0

Yes it's true your code can consume more resources then normal.Because you are working with feed and fetch_feed() consume more. It creates SimplePie object based on RSS or Atom feed from URL. You can do one thing just limiting your post as below: <h2><?php _e( 'Recent news from Some-Other Blog:', 'wpdocs_textdomain' ); ?></h2> <?php // ...


0

If your content is rarely updated and that you have configured a caching solution to have what is commonly called a 'supercache'. This means that ounce a page is cached, next call to that page will return a static content, without requiring a call to a php interpreter. Even on a cheap hosting, you can hold some huge traffic (over 1000 hits/s) and your next ...


2

1 If you look at the source code of get_the_title you will see that there is no difference between the two ways of writing the same thing, because if you call it without a parameter it is supposed to be the current ID. 2 There is no substantial difference between the two loops you use. All go through the same amount of items and do the same thing with it. ...


2

You should be using get_the_terms(). wp_get_post_terms() queries the db to get post term info, where as get_the_terms() returns the post term objects directly from the post term cache and only queries the db if that info is not available. By default, all post's terms are cached by the query being executed. EDIT I cannot comment (crappy mobile), but there ...


2

In my opinion you are focusing on a wrong issue in this case. For instance, if I want to change the Read More message I have to browse all files to see if it is there. This doesn't indicate localization problem. This indicates templating problem. What if you want to change markup of Read More of whatever else? Do you have to do this in multiple ...


-1

There is an easy way to get around this problem. Store all frontend messages as options of your theme. Let's define an option 'messages': add_option('messages',array()); Now we must populate this option. Let's define the defaults: $theme_messages_defaults = array ( 'read-more' => __('Read more','tekko'), 'next-page' => ...


0

The head of your site is full of scripts. The site is loading pretty fast, but rendering is slow because the browser is first waiting for the last (external) script to arrive. The scripts in the head, after all, may contain stuff that changes the page. First thing to do is move scripts that have nothing to do with rendering (especially google analytics) from ...


3

How often are the theme mods changed? A lot in the design phase, maybe a couple of times later on. Always by admins, never by ordinary users, let alone visitors. So, it doesn't make sense to generate the full css at every pageload. A better approach is to generate the css only for the admin and store the result for others. This will reduce the amount of ...


0

OK. The issue can be regarded as closed. The issue was: A dev had made changes to .htaccess which resulted in the parent theme assets to be redirected to the uri root - resulting in 404 errors for all those assets. Thanks for all input.


0

Sorry to hear this. That is a lot of plugins! Since you have no worries installing/using so many, I have to ask: have to tried using a plugin to minimize and impact performance of Javascript and CSS? Might be worth trying something like this just to see how it impacts overall performance: https://wordpress.org/plugins/autoptimize/ Also, have to you ...


0

Fatal error: Allowed memory size of 146800640 bytes exhausted (tried to allocate 57 bytes) makes the problem clear in the error message. You're running out resources - php memory. You can increase the php memory or you can ask the hosting provider to increase it for you. There are several ways to increase php memory. Some may work for you and others not. ...



Top 50 recent answers are included