Page 1 of 1

slow site with 300 products ,

Posted: Sat Jun 27, 2020 9:29 am
by sva260
Hello ,
Can someone help me ,why when i open (products) for the first time it is very slow ,

google pagespeed : https://developers.google.com/speed/pag ... 9%258A-004

opencart 3.0.3.3
Journal 3

Re: slow site with 300 products ,

Posted: Sat Jun 27, 2020 10:33 pm
by EvolveWebHosting
What type of server are you using? Have you considered using a CDN? Most CDNs will handle compression and converting images to Webp format, etc. Google Pagespeed is really hard to rank high with as well.

Re: slow site with 300 products ,

Posted: Sat Jun 27, 2020 11:05 pm
by JNeuhoff
The Google pagespeed report is quite clear!

The Script Evaluation used 2,349 ms, the Style & Layout another 945 ms. Your Javascripts took almost 4 secs of total CPU time. And you have an excessive DOM size. This is mainly caused by your using a quite bloated software, namely Journal3. Your website should become a lot faster by using a proper web theme, not Journal3, see this forum thread.

Re: slow site with 300 products ,

Posted: Sat Jun 27, 2020 11:32 pm
by IP_CAM
Google Pagespeed is really hard to rank high with as well ....
Well, it's not really that hard, one just has to decide on, to either look like a professional site,
or then look and act like a professional site. But for that, it takes a little more than just installing
some bulky Journal Theme.
---
Image

Re: slow site with 300 products ,

Posted: Sun Jun 28, 2020 3:05 am
by sva260
JNeuhoff wrote:
Sat Jun 27, 2020 11:05 pm
The Google pagespeed report is quite clear!

The Script Evaluation used 2,349 ms, the Style & Layout another 945 ms. Your Javascripts took almost 4 secs of total CPU time. And you have an excessive DOM size. This is mainly caused by your using a quite bloated software, namely Journal3. Your website should become a lot faster by using a proper web theme, not Journal3, see this forum thread.
wow ,
so there no solution for this ?

Re: slow site with 300 products ,

Posted: Sun Jun 28, 2020 4:15 am
by IP_CAM
You could use something like this, to speed up your Site:
https://nitropack.io/
Site Test results:
https://nitropack.io/demo/#https://www.mareezsa.com/

Re: slow site with 300 products ,

Posted: Sun Jun 28, 2020 11:01 pm
by sva260
IP_CAM wrote:
Sun Jun 28, 2020 4:15 am
You could use something like this, to speed up your Site:
https://nitropack.io/
Site Test results:
https://nitropack.io/demo/#https://www.mareezsa.com/
Thank you IP_CAM ,
I don't like this idea , is there anything be my side to fix this problem ?

Re: slow site with 300 products ,

Posted: Mon Jun 29, 2020 12:01 am
by JNeuhoff
I don't like this idea , is there anything be my side to fix this problem ?
To start with, uninstall Journal and set your website to the default theme, and then redo the speedtest, to see whether it makes any difference. If it does, get rid of Journal and use a proper web theme.

Re: slow site with 300 products ,

Posted: Mon Jun 29, 2020 5:46 pm
by paulfeakins
JNeuhoff wrote:
Mon Jun 29, 2020 12:01 am
I don't like this idea , is there anything be my side to fix this problem ?
To start with, uninstall Journal and set your website to the default theme, and then redo the speedtest, to see whether it makes any difference. If it does, get rid of Journal and use a proper web theme.
Agreed.

Re: slow site with 300 products ,

Posted: Mon Jun 29, 2020 7:16 pm
by letxobnav
Well, some nuance here.
1) These page appraisal sites measure first page loads only, no client-side caching of any kind. First page load is important but not the whole story.
2) They do not use http/2 protocol which is standard now on most mobiles.
3) They heavily throttle mobile measurements (i.e. they add percentages to the actual scores) as they assume mobiles have higher latency and slower processors which is not an unreasonable assumption.
4) Client-side processing (js and css) is extra hit on mobile measurements so if you have a top-heavy js/css template like journal, it hurts in the scores.
5) if you want to focus on first page loads, use a cdn as that will potentially reduce latency for your static assets (only on first reference as the browser also caches those). It will also increase latency for your dynamic assets and since journal likes to put truckloads of css inline, you might not see that much improvement with that template.

Then again, you could also just choose not to be fixated on these scores and just test the responsivenes of your site yourself and see if it is acceptable for a desktop/tablet/phone or not and merely take advantage of the recommendations in the reports instead of trying to hit a number.