Optimising website for core web vitals issues for mobile

Hi,
I have been trying to optimize https://www.clickmaint.com/ for mobile devices. The score for desktop is good in PageSpeed Insights But in mobile it’s around 45 to 50 I’m trying to achieve the LCP to be around 2.5 from 5.
I have attached the below file with issues I’m trying to fix for better improvements on mobile.
Can anyone help on this issue?
Thanks,
Farooq

Issues


Mobile Score

Hi @06Farooq,
Great question, thanks for asking!
I found similar threads that can help you:
1. The solution from @Sjardo on this post “Website Optimization”
2. The solution from @stefen on this post “Eliminating Render-blocking resources?”
3. This similar thread “How to increase the speed of the website to get good ranking in Google Speed Insights”

If anybody else has anything to add and/or share, please feel free to join in the conversation :slightly_smiling_face:

Thanks :heart: and have a fantastic day!
Best,
Bérangère

The gap is because HubSpot’s Google Ads integration logs ad interactions at the session level but does not pull cost or spend data into the contact or deal record. Spend lives in Google Ads and HubSpot does not sync it natively.

In practice: you can see a contact clicked a Google Ad but cannot report on what that click cost or calculate ROAS at the contact level inside HubSpot.

Common workarounds:
- Pull spend into a BI tool and join with HubSpot exported contact/deal data
- Use UTM parameters to match contacts to campaigns, then cross-reference spend in Google Ads directly

Some teams write campaign spend as a custom HubSpot property updated via API on a schedule.

What reporting outcome are you ultimately trying to reach?

Hi , @06Farooq

This is pretty common - a site can have a good desktop score and still struggle on mobile because the mobile device has much less processing power.

Since your LCP is around 5s and you’re trying to get it closer to 2.5s, I’d start with the LCP element shown in the mobile report. If it’s the hero image, use a properly sized WebP/AVIF image, compress it, preload it, and make sure it isn’t lazy-loaded. If it’s text, check font loading and remove/defer any CSS that is blocking the first render.

I’d then look at the JavaScript side. Chat widgets, analytics, tracking and other third-party scripts can easily delay the initial render on mobile. Defer non-critical scripts, remove anything you’re no longer using, and load marketing/tracking scripts after the main content where possible.For the hero section itself, keep it lightweight. If there’s a slider, video, animation or multiple large assets loading above the fold, try replacing it with a simpler static section and load the heavier content afterward. Also check whether the mobile version is downloading desktop-sized images or unnecessary assets. Serving the right image size for the actual mobile viewport can make a noticeable difference to LCP.

I’d make these changes and rerun PageSpeed after each one so you can see which change is actually moving the LCP from 5s toward 2.5s.

If you want a quicker way to handle some of the optimization, Website Speedy is also worth testing for things like image and script optimization. Disclaimer: I’m affiliated with Website Speedy.

Note: Wrote this out and used AI to clean up the formatting.