My account Get a quote
Web

Website Speed Optimization Guide: Improving Core Web Vitals

Website speed optimization guide: Core Web Vitals thresholds, measurement tools, image, CSS, JavaScript and caching fixes, and a step-by-step speed plan.

· 6 min read
Website Speed Optimization Guide: Improving Core Web Vitals

Website speed optimization is the work of improving images, code, the server and third-party scripts so that a page appears to the visitor sooner and responds instantly to clicks. The quickest gains usually come from three places: shrinking images, reducing unnecessary CSS and JavaScript load, and setting up caching and compression correctly on the server. This guide covers measuring first, then ranking problems by their impact and solving them.

Why does site speed matter?

Visitors do not wait for a slow page; especially on mobile connections, users who do not want to wait leave. Speed is more than comfort: it affects completing a basket in e-commerce, filling in a form on a corporate site, and visibility in search results. Google explicitly names the page experience metrics (Core Web Vitals) among the signals it uses in search ranking, but the relevance and quality of content remain the main factors. Speed alone does not guarantee rankings, but fixing a poor experience is always a gain.

What are Core Web Vitals?

Core Web Vitals is a set of metrics that measure real user experience across three main areas. The thresholds Google considers "good" are listed below.

MetricWhat it measuresGood thresholdTypical causes
LCP (Largest Contentful Paint)Time until the largest content element (usually the main image or heading) becomes visible2.5 seconds or lessLarge images, slow server response, render-blocking CSS and JavaScript
INP (Interaction to Next Paint)Delay in responding to clicks, taps and key presses200 milliseconds or lessHeavy JavaScript, long tasks, too many third-party scripts
CLS (Cumulative Layout Shift)Elements shifting position while the page loads0.1 or lessImages without dimensions, late-loading ad and embed areas, font swapping

These thresholds may be updated over time; confirm the latest values in Google's web developer documentation.

Measure first: which tools to use?

Optimizing by guesswork wastes time. First measure the current state:

  • PageSpeed Insights: Shows both lab data and, where available, real user data, and provides a list of recommendations.
  • Lighthouse: Runs in browser developer tools; suitable for repeatable tests.
  • Search Console Core Web Vitals report: Lists problematic page groups on your site with real user data.
  • Browser network tab: Shows directly how much space each file takes and how long it waits.

Lab results and real user data can differ. When making decisions, look at real user data where possible, and at lab tests while trying out fixes. Also measure your home page separately from the pages that receive the most traffic and generate the most sales.

Optimize your images

On most sites, images make up the largest part of page weight, so this is the easiest and most effective improvement.

  • Resize images to the size they are displayed at; do not show a 3000-pixel photo in a 600-pixel area.
  • Use modern, smaller formats such as WebP where possible, and provide a fallback for older browsers.
  • Compress images at a level that does not degrade visual quality.
  • Apply lazy loading to images below the fold, but not to the main image visible when the page opens, because that delays LCP.
  • Give every image width and height values so the page does not shift while loading (CLS).
  • Use responsive images: a small version for phones, a large version for wide screens.

Reduce CSS and JavaScript load

Clean up unnecessary code

Unused plugins, old libraries and style rules that are never used on a page needlessly burden the browser. Minify files, weigh the benefit of bundling against its real effect under HTTP/2, and load on each page only the scripts that page needs.

Manage render-blocking resources

CSS and scripts that hold back the display of a page delay LCP. Prioritize the minimum CSS needed for the first screen, load the rest later, and apply defer or async to non-critical JavaScript.

Reduce interaction delay

Most INP problems come from JavaScript that keeps the main thread busy for long periods. Break heavy work into smaller pieces, reduce unnecessary animation and tracking code, and keep interactive components such as forms and menus lightweight.

Server, cache and network side

No matter how good the front end is, if the server response is slow, the page will open slowly. Check the following:

  • Server response time (TTFB): If it is slow, review database queries, plugins and hosting resources. If your plan is insufficient, see our hosting types guide.
  • Compression: Gzip or Brotli should be enabled for text-based files.
  • Browser cache: Give long cache durations to unchanged images, fonts, CSS and JS files, and manage updates by adding a version to file names.
  • Page cache: Cache rarely changing pages on the server side so they are not regenerated on every request.
  • CDN: Serving static files from a point close to the visitor reduces latency.
  • Current protocols: A valid HTTPS setup together with HTTP/2 or HTTP/3 is essential; see our SSL certificate guide.

Fonts and third-party scripts

Fonts look small but cause delays. Limit the number of font families and weights you use, serve fonts from your own server if needed, and make sure text stays visible while the font loads.

Third-party scripts such as analytics, advertising, chat boxes, maps and social media embeds are often the most expensive part of a site. Question whether each one actually has business value; remove the unused ones and load the rest with a delay. A chat widget that takes up as much page space as your own content is the first candidate for speed optimization.

Mobile experience and slowness caused by ready-made software

A significant share of visitors come from phones, and mobile devices work with weaker processors and more variable connections than desktops. So a page can look fast on desktop and slow on mobile. Always run tests with the mobile setting, and try interactions such as the main menu, search box and product filter on a real phone.

In ready-made content management systems and e-commerce software, the typical source of slowness is plugin and theme features that have accumulated over time. Each plugin may bring extra CSS, JavaScript and database queries. Remove plugins you do not use, keep only one if several plugins do the same job, and limit heavy page builder components to where you really need them. Old revisions, temporary records and spam comments that pile up in the database should also be cleaned regularly. For a maintenance routine, see our website maintenance checklist.

On custom-developed sites, the problem is usually inefficient database queries, data recalculated on every request, and caching never having been considered. In this case, the greatest gain comes from measuring queries and fixing indexing and the server-side caching strategy.

Step-by-step speed plan

  1. Measure the home page, the most-visited page, and your payment or contact page with PageSpeed Insights, and record the results.
  2. Identify problematic page groups in the real user data in Search Console.
  3. Resize and compress images, and prioritize loading of the main image.
  4. Remove unused plugins, scripts and styles; minify the rest.
  5. Enable compression, browser cache and page cache.
  6. Evaluate third-party scripts one by one and remove the unnecessary ones.
  7. Measure again after the changes; compare results at each step and revert any change that causes a problem.
  8. Repeat the measurement once a month; speed declines as new plugins or content are added.

Quick checklist

AreaCheck
ImagesCorrect size, modern format, width/height values, no lazy loading on the main image
CSS/JSMinified, unused code removed, non-critical scripts deferred
ServerLow response time, Gzip/Brotli, HTTP/2 or HTTP/3
CacheBrowser and page cache on, static files with long lifetimes
Third-partyNo unnecessary scripts, the rest load late
Layout shiftSpace reserved for ad and embed areas, no shifting while fonts load

If you want to consider search visibility together with speed, running the technical audit and the content plan on the same schedule as your speed work tends to give good results.

Common mistakes

  • Installing speed plugins without measuring; speed plugins sometimes break the site or add their own load.
  • Looking only at desktop results; most visitors come from mobile.
  • Fixating on a single score; monitor user experience and real data instead of the number alone.
  • Not noticing that updates do not appear after setting up caching; plan for versioning.
  • Not re-testing speed after adding a new component.

Conclusion

A fast site is not a one-time task but a habit that requires regular maintenance: measure, fix the biggest problem, and measure again. If you want us to analyze your site's speed issues together and apply lasting solutions, you can get in touch with Erdem Software.

Frequently asked questions

Does website speed affect SEO?

Yes, page experience metrics are among the signals search systems consider. However, content quality and relevance remain decisive; speed alone does not guarantee rankings.

What are the three metrics that make up Core Web Vitals?

LCP (time until the largest content is visible), INP (delay in responding to interactions) and CLS (layout shift). All three measure real user experience.

What should I look at first to speed up my site?

Measure first. On most sites, image sizes, unnecessary scripts and missing caching give the biggest gains; rank the problems by their impact.

Is installing a speed plugin enough?

Not on its own. A plugin can help with caching and minification, but it does not solve basic problems such as heavy images, excess scripts and an underpowered server.

How often should speed be measured?

After every major change, and regularly, around once a month. Performance changes as new plugins, content or ad code are added.

Need help with this?

Fast, search-friendly, multilingual sites you can update easily from a panel.

See the serviceGet a quote

Related posts

All →