PROJECT PLANNING GUIDE · Saudi Services AI

How to improve website speed and Core Web Vitals

A slow service page can interrupt an enquiry before the customer reaches your form.

More details

A slow service page can interrupt an enquiry before the customer reaches your form. Start by finding the cause on the pages people actually use, then test each change.

Check your website

Measure the customer journey first

Choose your homepage, a priority service page and the contact journey. Test mobile and desktop separately, noting the test conditions and date. PageSpeed Insights can provide laboratory diagnostics and real-user data when available. A single test score is not evidence that every customer gets the same experience. Keep the initial results so the effect of each change can be compared.

Understand LCP, INP and CLS

Core Web Vitals cover loading, interaction responsiveness and layout stability. Google’s good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, evaluated at the 75th percentile of real-user visits. A new or low-traffic page may lack field data. Laboratory checks help diagnose issues but do not replace that real-user measurement.

Reduce image and media weight

Use appropriately sized images for the space they occupy, efficient formats and responsive image variants. Give images explicit dimensions to reserve their space. Keep the main visible image discoverable early; load media further down the page when needed. Review background videos and animated assets on mobile. Preserve useful product or landmark detail instead of compressing every image until it becomes unclear.

More details

Improve interactions without adding plugins

Inventory chat widgets, analytics, embedded videos and other scripts. Remove unused code and avoid loading every tool before the customer needs it. Check whether long-running work delays menus, form validation or buttons. A custom-coded site can also be slow: changing the platform alone does not fix oversized assets or expensive scripts. On WordPress, diagnose the actual theme and plugin behaviour before deciding what to replace.

Verify the fix and agree maintenance

Repeat tests under comparable conditions, then check forms, language switching, keyboard access and animations. Record what changed and watch real-user trends when sufficient data becomes available. A useful performance brief specifies the affected pages, implementation work, verification and ongoing monitoring. Share your URL to scope a technical review; a performance score does not guarantee search rankings or sales.

Bring these details to the project discussion

Priority page URLs
Mobile and desktop baseline results
Image, video and script inventory
Access to the current hosting and source
Working forms and language-switch checks
Agreed review period and maintenance owner