Slow mobile page loads - Google says "Fix LCP" (Largest Contentful Paint)

Anyone have quick and dirty solutions to finding LCP problems for OpenCart 3.0.3.6?
I'm thinking part of it may have to do with how OC caches stuff, and what are people doing about images - are they reformating the JPEG2000 or other formats (png, etc.) to try to speed up the page loads?
I didn't see any discussion on this topic so thought I'd start one...
John :-#)#
PS, is OC ever going to fix the notification that the OP's post is responded to?

With regards to the images, you can convert them to webp using this extension https://www.opencart.com/index.php?rout ... _license=0.

fegdeed wrote: ↑

Mon Dec 20, 2021 1:32 am

With regards to the images, you can convert them to webp using this extension https://www.opencart.com/index.php?rout ... _license=0.

Nice that the developer has made this free, however I use Clear Thinking's Smart Search Pro so I hope this will work with that engine...the designer says to ask first before trying if not using the default search engine - so I asked.
The question now is, is it most likely to be images that are producing these delays in loading the page on mobile devices?

I think I may have found a partial answer to my question. To test page load speed and get a report (provided by Google) go here:

https://pagespeed.web.dev/

Drilling through this by providing my OC catalog address URL yields a bunch of issues that I am at a bit of a loss to understand so far - images were way, way down at the bottom of the list by the way - 0.3 seconds:


Opening the first element:

More work needs to be done!

Thanks

Another free webp images extension:

https://www.opencart.com/index.php?rout ... _license=0

jrr wrote: ↑

Mon Dec 20, 2021 2:56 am

fegdeed wrote: ↑

Mon Dec 20, 2021 1:32 am

With regards to the images, you can convert them to webp using this extension https://www.opencart.com/index.php?rout ... _license=0.

Nice that the developer has made this free, however I use Clear Thinking's Smart Search Pro so I hope this will work with that engine...the designer says to ask first before trying if not using the default search engine - so I asked.
The question now is, is it most likely to be images that are producing these delays in loading the page on mobile devices?

I think I may have found a partial answer to my question. To test page load speed and get a report (provided by Google) go here:

https://pagespeed.web.dev/

Drilling through this by providing my OC catalog address URL yields a bunch of issues that I am at a bit of a loss to understand so far - images were way, way down at the bottom of the list by the way - 0.3 seconds:


Opening the first element:

More work needs to be done!

Thanks

This depends on the theme you are using. If Journal then update to there latest theme they have released a new update to that.

Many things are render blocking resources. Some of them you may load on async some by defer but many you cannot.
Pagespeed does not make that determination for you, it just lists the lot and states "you may consider...", its up to you which you can and cannot tackle.

As such, these website evaluation tools merely give you pointers, guidance, not ready solutions as they cannot.
For example, it states that you could put css inline, but when you put all your css inline it will state that your source it too big and suggests putting css external.

First question would be, do you have the same issues for desktop as for mobile?
Because, other than that Pagespeed throttles the response times for mobile, the issues should be pretty much the same.

your biggest issues seem to be:

1) reduce initial server response time:
Probably TTFB which means that your server takes a long time to even produce and deliver a page (the html part).
That could be anything from network latency, slow web-server, slow database, inefficient code, etc. or a combination of those. If it is your theme, well that is a choice also.

Using web developer tools, check your TTFB for your html and for your static assets (css,js,images or a static html or text page).
If the TTFB of the static assets are acceptable then you can eliminate the network and web-server as the cause which leaves the database and code.

2) enable text compression:
You probably do not use compression which seems rather strange.
Check with your host if they have default compression for text based content in their server config or do it yourself in htaccess.

Both of these have no relation to LCP which comes into play once the html has been received and is parsed.
LCP relates to actually building the page in the browser based on the html and associated static assets received. There webp can help a little, but image size reduction has a much greater impact.