Hi Mike
Thank you for looki8ng into this so thoroughly! It’s very much appreciated.
I will go and look at why this is being duplicated – it could be the Beta feature in WP-Rocket’s new CSS cleanup tool – I will send them a support ticket to ask them to check it.
In the meantime thank you!
All the best
Ed

Thanks for your help Yigit.
Sadly, if I have to turn off CSS compression I will compromise the site performance so at least now I know where I’m at.
Thanks for sorting this.
Kind regards
Ed

Thanks Rikard

So the only way to reduce the bloat is to remove more files across the whole site. So that will mean going through al my pages and removing elements I think I don’t need then removing them at a global level? Crazy!

I would love Kreisi to take the speed and performance issues more seriously. I have half a second of bloat on every page.
Thank you for your efforts – I do appreciate it. But it seems I can do nothing now except strip everything put I don’t want and then go back and fix the pages that are broken.

Thanks
Ed

Hi Rikard
Private info link sent, sorry, I thought I’d sent one! My apologies.
Kind regards and thank you
Ed

• This reply was modified 3 years, 7 months ago by Swarez.

Hi Rikard
Please keep the post open – I just need to get a little time free to gather the info together/.
Many thanks
Ed

Hi Rikard
Thanks for your reply.
None of that makes any difference. The merged-styles CSS file has been regenerated and is still 512KB and still contains everything. All caches cleared and KEYCDN zones purged.
All old files deleted through the Performance tab option.
This is madness and I need to find a way of reducing all this bloat that I don’t need.
Any other suggestions please?
We have a new algorithm update coming regarding Core Web Vitals and this will make all the difference to the performance of my site. All I want is for the theme to recognize the code I DON’T want.
Thanks
Ed

Thanks Ismael – I will paste the new code and test!
Thank you
Ed

Hi Rikard

All updates done, caches cleared and asked for a couple of test emails from Facebook friends – still the same problem….

Screengrab

Thanks
Ed

Hi Victoria
Yes that’s what I’m referring to – thank you for the screen-grab.

I have a major problem here.
When I go to a Portfolio item all the images (in any image container) are NOT displayed. Additionally when I click in to the image and, for instance, choose ‘insert’ (to perhaps re-select it) I go to ‘Uploaded to this post’ and the list is empty – it say ‘no items found’.

This was not the case beforehand. So suddenly there is an issue with the theme not associating images with Portfolio items – yet they were before I switched themes temporarily.

So the images you see in the screen-grab should all be the same dimensions – 650px x 450px. It looks like the theme is not picking up this in the image element.

Will provide logins in Private data.

Hope you can help? This is rather stressful!
Thanks
Ed

Thank you Nikko
I will test and report back! Thanks for the code – that will be a big help if it works okay.
Kind regards
Ed

by the way that link from above doesn’t link to anything – did you mean it to?

Hi Nikko

Thank you for replying but unfortunately your information is a little inaccurate.

For example, in version 4.1 the functions.php file registers this:
$avia_config['imgSize']['portfolio'] = array('width'=>402, 'height'=>325 ); // images for portfolio entries (2,3 column)
That clearly sends a request to create an image at these dimensions for the tag ‘portfolio’

In version 4.5 (that I refer to) that has now changed to this:
$avia_config['imgSize']['portfolio'] = array('width'=>495, 'height'=>400 ); // images for portfolio entries (2,3 column)
which now registers a different size upon image upload. So, with reference to my original problem, WordPress will not generate a 402x325px image unless I physically go and change this directly in functions.php

I don’t want to do this every time you have an update. So please either change it back or explain why you have changed the properties of this entry please? It messes with all the resizing optimization for all my Portfolio entries.

I would be grateful if you could paste me some code where I can override this in my child theme functions.php

Thank you in advance
Regards
Ed

PS – I have unzipped a fresh copy of 4.07 and there is no mention of a 495 x 400 px image size! FYI this is the entire selection of registered image sizes from 4.07

$avia_config['imgSize']['widget'] 			 	= array('width'=>36,  'height'=>36);						// small preview pics eg sidebar news
$avia_config['imgSize']['square'] 		 	    = array('width'=>180, 'height'=>180);		                 // small image for blogs
$avia_config['imgSize']['featured'] 		 	= array('width'=>1500, 'height'=>430 );						// images for fullsize pages and fullsize slider
$avia_config['imgSize']['featured_large'] 		= array('width'=>1500, 'height'=>630 );						// images for fullsize pages and fullsize slider
$avia_config['imgSize']['extra_large'] 		 	= array('width'=>1500, 'height'=>1500 , 'crop' => false);	// images for fullscrren slider
$avia_config['imgSize']['portfolio'] 		 	= array('width'=>402, 'height'=>325 );						// images for portfolio entries (2,3 column)
$avia_config['imgSize']['portfolio_small'] 		= array('width'=>260, 'height'=>185 );						// images for portfolio 4 columns
$avia_config['imgSize']['gallery'] 		 		= array('width'=>845, 'height'=>684 );						// images for portfolio entries (2,3 column)
$avia_config['imgSize']['magazine'] 		 	= array('width'=>710, 'height'=>375 );						// images for magazines
$avia_config['imgSize']['masonry'] 		 		= array('width'=>705, 'height'=>705 , 'crop' => false);		// images for fullscreen masonry
$avia_config['imgSize']['entry_with_sidebar'] 	= array('width'=>845, 'height'=>321);		            	// big images for blog and page entries
$avia_config['imgSize']['entry_without_sidebar']= array('width'=>1210, 'height'=>423 );						// images for fullsize pages and fullsize slider
$avia_config['imgSize'] = apply_filters('avf_modify_thumb_size', $avia_config['imgSize']);

• This reply was modified 6 years, 1 month ago by Swarez.

Thank you Rickard
Works great now that I figured out where to place the snippet (after creating the CSS class).
Thank you for your help – one to bear in mind for the future!
Kind regrads
Ed