Hi @jatinder1987,
After you do an Asset Optimization scan, please try to visit the front page to trigger the processing of assets. If you hover over the spinning icons, you’ll see the tooltip, explaining when the files are optimized.
If none of the files are optimized, regardless of visiting the front page of your site, please verify that WordPress cron is functioning properly.
Also, the accusation in the article is not true. You can see that the theme styles are present on your screenshot. Hummingbird will detect any assets that are enqueued with proper WordPress functions.
Best regards,
Anton
Hello Anton,
Thanks for your response. I think the plugin will not combine the files into 1.
I am getting this ( We’ve disabled the Combine option because your server has HTTP/2 activated. HTTP/2 automatically optimizes the delivery of assets for you ) when i activate the “Asset Optimization”. I need to resolve this issue -> https://screenpresso.com/=A5iJb . Can your plugin do this ?
Recently I was using Autoptimize and it was working perfectly to combine files into 1 but we are trying to learn hummingbird functionalities now.
@jatinder1987,
Combining assets on HTTP/2 is not recommended as it makes browser caching more difficult.
Best regards,
Anton
Hi,
So what would you recommend me to resolve this error?
@jatinder1987,
I would not recommend combining with HTTP/2. But if the numbers in YSlow are more important than the actual performance, you can override the default Hummingbird behavior by editing the file core/class-utils.php in the plugin directory. In the function get_http2_status() add return false; as the first line inside the function, it should look something like this:
public static function get_http2_status() {
return false;
...all other code will be here...
}
Best regards,
Anton
@vanyukov,
What do you suggest? I should skip Y slow and also 3% of page speed score ? If i am on HTTP/2 then i should not try to make fewer HTTP requests ? Please advice me
@jatinder1987,
HTTP/2 can download the assets concurrently, so there is no need to combine as there was with HTTP 1.0. Also, keeping assets separately gives you an advantage with browser caching. For example, if there’s a change in one file, user will need to re-download that single file, not the whole bundle.
My recommendation would be to try and combine if you have 100+ assets. But you need to keep in mind, that combining files can break stuff. So it’s a trial and error process. Also, the 3% page speed score is just a number, it’s not a 3% increase in the actual page speed.
Best regards,
Anton
