By ssnobben on Sunday, 17 May 2020
Posted in General Issues
Replies 3
Likes 0
Views 689
Votes 0
Hi !

after doing a analysis with Lighthouse I got some bad performance metrics especially about performance for ES and just without much users and data. Also testing on EasySocial score on demo page http://easysocial.stackideas.com/

b]Legend best score = 100%[/b]

- Performance --> 10
- Accessibility --> 37
- Best Practices --> 54
- SEO --> 75

Here is the test url everybody can test and see some results.

https://googlechrome.github.io/lighthouse/viewer/?psiurl=http://easysocial.stackideas.com/#best-practices

Some EasySocial improvments issus suggestions example Performance. from the test.

"Opportunities- These suggestions can help your page load faster. They don't directly affect the Performance score."
Opportunity

- Serve images in next-gen formats
- Eliminate render-blocking resources
- Properly size images
- Efficiently encode images
- Remove unused CSS

etc

What you think about this test is is good for analysis for improvements for EasySocial ?

All the best!
Hello Ssnobben,

I think people need to start realizing that social networks are not just any CRUD application. It is a sophisticated and complicated system to begin with.

As for the recommendations that Lighthouse provides, it is very technical but I will try my best to make it less technical for you.


- Serve images in next-gen formats

Next generation image formats is webp and at this point of time, webp is not supported by Safari and Internet Explorer. There are work arounds but you also need to consider that your web server needs to have webp support compiled with php or a CLI. Not every hosting company will provide such tools and therefore we can't roll this out.



- Eliminate render-blocking resources

This has always been something that I always want to achieve but because we are just an extension level, we cannot do much. This has to happen on the CMS / template level.



- Properly size images

Same as the above. In order for us to be able to know what sizes are needed, we need to first know what is the template trying to do. Example: If your template renders a sidebar that is 300px in width, and if you only load an image that has 128px in width, the image would be pixelated.



- Efficiently encode images

This can be solved using the image optimizer service that we provide. Our demo site does not use this currently.



- Remove unused CSS

This is the same thing. This cannot be achieved by an extension, we have no idea what is needed on the template level. On the extension level, it becomes really tricky which pose the same problem as the render-blocking resources and efficiently encode image


With all said and done, we are continuously trying to improve all of this but I really do not think, this has much impact on most users unless most of your users are connecting with a slow internet connection
·
Sunday, 17 May 2020 17:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for this insights and analysis Mark.

I dont use Safari and IE is going out now bcs of Edge.

One Joomla free WebP extension you can try is https://dj-extensions.com/downloads/cat_view/354-dj-webp and I have tested it and working well on one site I tested it there.
·
Monday, 18 May 2020 01:02
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem If your hoster supports webp, you could try using such a plugin.

But I think you got to cautiously use this plugin because this plugin would need to scan the entire html output for png/jpg imgages and that alone is going to consume CPU and will affect your FCP.
·
Monday, 18 May 2020 10:28
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post