Mobile version slowness issue

Hello, we use wprocket in our theme, there seems to be no problem on the web side, but we are having a lot of problems on the mobile view side. Too many CSSs are causing us slowness on the mobile side. We would be very happy if you can help.

Attachments:

You must be logged in to view attached files.

Hello,

On my end, the result is 83 – https://prnt.sc/ojsPmd-zz0g1, which is okay for mobile.

Let me know if you have fixed that or if you have more questions.

Kind Regards

The value there is constantly changing. So you can see the 60 you made after 1-2 hours. I could not fix the problems I sent in the picture. Could you please check it by logging in.

It also loads extremely late in the transition between pages. Although we have optimized everything.
I’m sending you the test I just took.

Attachments:

You must be logged in to view attached files.

Also, no matter what I do, I can’t bring the login screen in the section on the side that opens when I click login, I guess it’s a situation related to css.

Attachments:

You must be logged in to view attached files.

Hello,

May I disable 3rd party plugins for testing?

Looking forward to collaborating with you!

Kind Regards

Of course you can test it as you wish. I appreciate your help. I can’t fix the errors in the picture I sent. I need your support on that too.

Attachments:

You must be logged in to view attached files.

Have you been able to check? Even though we use CDN, the values are still very bad. Really, our customers are having a lot of difficulty on mobile, we have already received 1 negative comment. They commented that it was extremely slow and late loading and hanging.

Thanks in advance for your help.

Attachments:

You must be logged in to view attached files.

[Luke Nielsen]

Hello,

Sorry for the delay.

Properly size images: define this image https://prnt.sc/Z9MKgzCgk-Dn via an appropriate element “Image”.

Serve static assets with an efficient cache policy: You should cache immutable static assets for a long time, such as a year or longer, so you need to configure your server to return the Cache-Control HTTP response header:

https://take.ms/vXMSl

For now, it’s adjusted for 1 on your server – https://prnt.sc/91uMTP5TKYTd.

It should be 1year+ as in the example: https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/?utm_source=lighthouse&utm_medium=lr#how_to_cache_static_resources_using_http_caching

Also, here are a few steps as well – https://codefile.io/f/UZ5N2xNLuH , please check

Let me know the result.

Kind Regards

• This reply was modified 4 days, 6 hours ago by Luke Nielsen.

I tried to do most of what you posted but there are a few places I can’t figure out.

Largest Contentful Paint
Eliminate resources that block rendering
Correctly sized images

If these problems are solved, I feel like everything will be fine. I’ve done some of the things you sent, but no matter how much I change the size of the images, I can’t get past those errors.

Thank you for your help.

Attachments:

You must be logged in to view attached files.

I am waiting for your help. I would appreciate it if you could get back to me soon.

Hello,

Sorry for the delay.

LCP(Largest Contentful Paint) message doesn’t mean that this particular element is loaded slowly. It just indicates which element is the Larger Contentful Paint. Read more here https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/?utm_source=lighthouse&utm_medium=lr

The Correctly sized images were fixed, you can recheck.

Kind Regards

[Author]

Posts