What speed optimization changes
A slow site loses twice: Google’s page experience signals count against it in rankings, and the visitors who do arrive leave before the page finishes. Most of the traffic in Nepal and a majority abroad is on mobile, often on a mid-range phone on a variable connection, and a page that a developer sees load instantly on office wifi can take six seconds there. Core Web Vitals optimization, part of my SEO services and one of the layers of technical SEO, is the work of finding what actually makes the page slow for those users and fixing it, measured by the field data Google itself uses: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift from the Chrome User Experience Report, as shown in Search Console and PageSpeed Insights. A lab score of 95 is nice; a passing field assessment on mobile is what matters.
Who this is for
- Sites whose Search Console Core Web Vitals report shows “poor” or “needs improvement” URLs on mobile.
- WordPress sites built with Elementor, WPBakery or Divi that have grown to three to five megabytes a page.
- Stores whose category pages take seconds to become usable and whose checkout drops customers.
- Businesses on shared Nepali hosting where the server takes more than a second to respond before anything else happens.
- Sites where a previous “speed plugin” was installed and made things worse.
What the service includes
- Diagnosis from field data: which templates and URL groups fail, on which metric, on which devices, from CrUX and Search Console, then lab profiling to find the causes.
- Server and hosting: time to first byte measured and fixed through caching, PHP and database tuning, a CDN, or a hosting move where the current host cannot be made fast; hosting moves are handled through the hosting and website migration service.
- Images: correct sizing per breakpoint, modern formats (WebP, AVIF), compression, lazy loading below the fold, and priority loading for the largest above-the-fold image, which is usually the Largest Contentful Paint element.
- Scripts and third parties: render-blocking scripts deferred, unused plugin and theme code removed, chat widgets, tag managers, review badges, maps and video embeds loaded on interaction or delayed, and tags consolidated in Google Tag Manager.
- CSS and fonts: critical CSS inlined, unused CSS removed, fonts self-hosted, subset and loaded with a swap strategy that does not shift the layout.
- Layout shift: dimensions on images and embeds, reserved space for ads and late content, and fixes for sliders, cookie banners and menus that push the page around.
- Interaction responsiveness: long JavaScript tasks broken up, heavy sliders and animation libraries replaced, and event handlers on menus and filters made cheap.
- Caching: page, object and browser caching configured correctly for the platform, with exclusions for carts, logins and personalized pages.
- Platform-specific work: WordPress plugin and theme cleanup; WooCommerce cart fragment and AJAX fixes; Shopify app script audits and theme trimming; custom builds through developer tickets.
How speed work runs
- Baseline. Field data per template, lab profiles of the worst pages, a full list of scripts and their cost, and a record of scores before any change.
- Quick wins. Image, caching and script deferral fixes that typically halve load time within the first week on a WordPress site.
- Structural fixes. Hosting, theme, builder and third-party changes that need decisions from you, with the trade-offs explained.
- Verification. Lab re-test immediately; field data checked after 28 days, which is how long CrUX takes to reflect a change.
- Protection. A short standard for adding images, plugins and scripts so the site does not slow down again, and a quarterly check while the engagement runs.
Typical business sites take one to two weeks of work; stores and heavily built sites two to four. The field data confirmation comes about a month after the fixes ship.
Speed mistakes I fix most often
- A caching plugin installed on top of another caching plugin on top of server caching, breaking the cart.
- Full-resolution photos uploaded straight from a phone, five megabytes each, on the homepage slider.
- A dozen third-party tags loaded on every page for tools nobody uses any more.
- Shared hosting with a one-to-three-second server response, which no front-end fix can overcome.
- Optimizing for a lab score with tricks (delaying all JavaScript, lazy loading the hero image) that make the real experience worse.
- On Chandragiri Hills, the combination of heavy images, no caching and broken internal links produced load times above six seconds; fixing those was the first step before content could work.
What you receive
- The baseline report with field and lab data per template and the script inventory.
- The fixes implemented on WordPress, WooCommerce and Shopify, or as developer tickets elsewhere.
- Before-and-after lab results immediately and field results after 28 days.
- The upkeep standard and a quarterly check.
Speed work is included in every tier on the SEO packages and pricing page at the level the site needs, and available as a standalone project. Sites that need a rebuild rather than a tune are better served by the website redesign service, with the SEO protected through migration SEO.
Next step
Request a free speed check with your URL and I will reply with your field Core Web Vitals status on mobile, the three largest causes, and what fixing them would involve. Related work is under SEO services.