espacemusculation

Unfortunately the file number has increased overnight, up to about 1000

Yes the same execphp-xx are used every page, it is the ID of my widgets.
and it is the same css for all execphp

I do not understand, the file number has not changed since then.

Thank you for your help in any case, I keep you informed tomorrow (here it is 11h pm) if the number of file exploded

• This reply was modified 9 years, 7 months ago by espacemusculation.

#execphp-xx is ok I know these id, they are fixed.

Very bizarre, since all by the hour the file counter does not move anymore !! 🙂

Maybe my problem came from the preload system? (That I did not activate this time)

• This reply was modified 9 years, 7 months ago by espacemusculation.

The source code comes from the wp-rocket cache plugin

So there is no change of id or class

Unless the plugin continues in background to refer to something that changes but that does not change with the creation of the cache.

This is a good question, my inline CSS doesn’t change.

I do not see how and why it would change 🙁

thanks you 🙂

Is file production endless?

in other words

If I do not empty the cache regularly, will tomorrow I have 10,000 files and next week 100,000 files? Or it will stop ?

In the other post, I wanted to know if it was possible to have 1 file css for all website pages.

• This reply was modified 9 years, 7 months ago by espacemusculation.
• This reply was modified 9 years, 7 months ago by espacemusculation.
• This reply was modified 9 years, 7 months ago by espacemusculation.

Thanks you very muuch for your anwser
my problem is no really that

I have too many file and I would like to have only 1 file (.css) for all website

Thanks you for your help 🙂

PS : If try to uncheck the “also aggregate inline CSS”-option

but I have a Google Pagespeed issue :

Afficher en priorité le contenu visible (Show visible content first)
Votre page doit effectuer des allers-retours supplémentaires sur le réseau afin que la partie au-dessus de la ligne de flottaison s’affiche. Pour obtenir des performances optimales, réduisez la quantité de code HTML nécessaire à l’affichage de la partie au-dessus de la ligne de flottaison.
Il a fallu 59,4 Ko octets de la réponse HTML pour afficher le contenu au-dessus de la ligne de flottaison. Cela nécessite 3 boucles sur le réseau. Traitez en priorité le contenu au-dessus de la ligne de flottaison pour qu’il puisse s’afficher dès les 2 premières boucles du code HTML sur le réseau.
Environ 16 % seulement du contenu final au-dessus de la ligne de flottaison a pu être affiché avec le code HTML diffusé en 2 boucles sur le réseau afficher une capture d’écran Afficher l’original.

• This reply was modified 9 years, 7 months ago by espacemusculation.
• This reply was modified 9 years, 7 months ago by espacemusculation.