Fred

found a dirty solution
1- Edit the file style.min.css (or edit the style.css file and recompile it after you made the changes )
2- Remove the last line of the css which contains the following stuff :
@font-face{font-family:’GeneratePress’;src:url(fonts/generatepress.eot);src:url(fonts/generatepress.eot#iefix) format(’embedded-opentype’),url(fonts/generatepress.woff2) format(‘woff2’),url(fonts/generatepress.woff) format(‘woff’),url(fonts/generatepress.ttf) format(‘truetype’),url(fonts/generatepress.svg#GeneratePress) format(‘svg’);font-weight:400;font-style:normal}.menu-toggle:before,.search-item a:before,.dropdown-menu-toggle:before,.cat-links:before,.tags-links:before,.comments-link:before,.nav-previous .prev:before,.nav-next .next:before,.generate-back-to-top:before{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-style:normal;font-variant:normal;text-rendering:auto;line-height:1;speak:none}.cat-links:before,.tags-links:before,.comments-link:before,.nav-previous .prev:before,.nav-next .next:before{opacity:.7}.infinite-scroll .paging-navigation,.infinite-scroll.neverending .site-footer{display:none}.infinity-end.neverending .site-footer{display:block}.so-panel.widget{padding:0}#mc_embed_signup .clear{display:block;height:auto;visibility:visible;width:auto}.container.grid-container{width:auto}.main-navigation .slideout-toggle a:before,.slide-opened .slideout-overlay .slideout-exit:before{font-family:GeneratePress}
2- You will have to rebuild or add a couple of css rules to use your own icon like this (for the menu icon it is really easy):
.menu-toggle::before {
content: “?”;
font-family: helvetica; // switch to normal fonts and nothing else needed
width: 1.28571429em;
text-align: center;
display: inline-block;
}
.toggled .menu-toggle::before {
content: “X”;
}
3- This generatepress font is used a few times only, so beside the menu css you will not get into trouble by removing this few lines.

Watch out if you update the theme since it will put the font back into the minified version (only).
If you prefer to keep it and remove lighthouse error just add the font somewhere else so to load it earlier.

• This reply was modified 5 years, 11 months ago by Fred.

Thanks for your reply,
The theme is self-made, no plugin beside resmushit and security one.
The easiest solution I found is to upload images bigger than the one needed and let your plugin compress the size used in the page (uploading images 1100×1100 and have a custom size of 1000×1000). This way the image used is the best compressed one and not the original (bigger)… The strange thing is that it is not happening on every images but only for a few ones in the same gallery. All my images are 1000×1000 so it should pick the right one or the wrong one in every case but it is not. Strange anyway but not a big issue, just boring.
Thanks anyway
Frederic

Yes no difference with paid version but using the free one on other smaller websites remained an issue. I did not want to get into the same nightmare next update if you decided not to backup images or not restore files larger than 10kbytes or who knows what you might think of!
So the solution is now to remove WP Migration from every single website and use another paid plugin so not to get back into any of your wierd plugin updates attitude. The premium WP Migration plugins we bought are going straigth into the trash. Cannot take any other chance of blowing a full day updating small websites with paid versions just because you changed your mood. Anyway advise users before they backup so they know they will never be able to restore anything with the free version. Maybe use some marketing advisor before launching a hack.

Looks like I am not the only one getting into this mess. This should be enough for reconsidering your updates without advising users upfront. Do not worry about me claiming or proving anything because I hate to jusitfy myself to people that should themselves consider using a more friendly approch to their customers and OTHER users.

On the other hand the backup itseldf is far from beeing right. It does not backup everything (root files like htaccess or config and so on) making the whole restore process more likely to blow your site if you do not disable all plugins and more likely security plugins that rely upon such files (obviously people restoring a website will not restore a blank wordpress site!).

Also, the fact that you are using a dedicated packing system makes the backup unsafe since any bug or update within your code will make the whole files unreadable (a zip file is so much better to recover only a couple of files).

I understand you need money to keep up a plugin but your method is unfair since your undercover update process and “restore only on payment option” is more likely a surprising way to convince users of your good faith. Before letting people think they can recover their files please advise that they will not be able to do unless they pay. Have people pay before backing up! As easy as that.