GOTEN Digital

Journal

6 min read
  • web development
  • seo

Website Performance Optimization: Where to Start

Slow pages lose customers. What Core Web Vitals measure, free tools to test your site, and the fixes to make first.

Illustration of a browser window with a yellow lightning bolt, standing for a fast-loading website

A slow website quietly costs you customers. People tap a link from Google or Instagram, wait, and leave before your page appears. Website performance optimization is the work of making pages load and respond quickly, and it pays off twice: visitors stay longer, and Google has one less reason to rank a competitor above you.

This guide is for business owners and marketing teams, not only developers. It explains what Google measures, how to test your own site for free, and which fixes to make first.

Even a few seconds’ delay is enough to create an unpleasant user experience.

Jakob Nielsen, Nielsen Norman Group

Why speed matters for your business

Speed shapes the first impression of your brand. A page that jumps around while loading, or a button that does nothing for a second after you tap it, feels broken even when it works. In Indonesia many visitors browse on mid-range Android phones over mobile data, so a site that feels fine on the office Wi-Fi can feel slow to the people you actually want to reach.

Speed also affects search. Google uses page experience signals, including Core Web Vitals, as part of how it ranks pages. Good content still matters most, but when two pages are similarly useful, the faster one has an edge.

The three numbers Google looks at: Core Web Vitals

Google sums up real-world page experience with three Core Web Vitals. A page passes when at least 75% of visits meet the "good" threshold:

  • Largest Contentful Paint (LCP): loading. How long it takes for the main content, usually the hero image or headline, to appear. Good is 2.5 seconds or less.
  • Interaction to Next Paint (INP): responsiveness. How quickly the page reacts when someone taps, clicks or types. Good is 200 milliseconds or less. INP replaced the older First Input Delay metric in March 2024.
  • Cumulative Layout Shift (CLS): visual stability. How much the layout jumps around while loading. Good is 0.1 or less.

How to measure your site for free

You do not need paid tools to start. Three free options cover most needs:

  • PageSpeed Insights (pagespeed.web.dev). Paste any URL to see real-user Core Web Vitals, when Google has enough data, plus a lab test with a list of suggested fixes. Always check the mobile tab first.
  • Google Search Console. The Core Web Vitals report groups your pages into good, needs improvement and poor, based on real visits. Use it to find which page templates need work.
  • Lighthouse in Chrome DevTools. Useful for developers to test a page before it goes live.

Test your most important pages, not only the homepage: product or service pages, landing pages for ads, and your contact page.

Where to start: fixes in order of impact

On most business websites the same problems come up again and again. Work through them in this order.

1. Images

Oversized images are the most common cause of slow pages. A photo straight from a camera or design tool can be several megabytes, when a well-compressed version would look the same at a fraction of the size.

  • Resize images to the largest size they are actually displayed at, and serve smaller versions to phones.
  • Use modern formats such as WebP or AVIF.
  • Lazy-load images further down the page, but never the main hero image: it should load first.
  • Set a width and height on every image so the layout does not jump when it appears. This alone often fixes a poor CLS score.

2. Fonts

Custom fonts make a brand look polished but can delay text from appearing. Limit the number of font families and weights, host fonts on your own domain where possible, and use font-display: swap so text shows immediately in a fallback font.

3. Third-party scripts

Chat widgets, analytics, ad pixels, embedded social feeds and video players all add weight, and each one can slow down how quickly the page responds. List every third-party script on your site, remove the ones nobody uses, and load the rest after the main content.

4. JavaScript

Heavy JavaScript is the usual cause of poor INP: the phone is busy running code instead of responding to the tap. Developers can split code so each page only loads what it needs, defer non-essential scripts and break up long tasks.

5. Caching, compression and a CDN

Browser caching lets returning visitors reuse files they already downloaded. Compression such as Brotli or gzip shrinks text files before they are sent. A content delivery network (CDN) serves files from a server close to each visitor, which matters if your customers are spread across Indonesia or abroad.

6. Server response time

If the server itself takes a long time to answer, every other fix has a ceiling. Cheap shared hosting, slow database queries or a bloated plugin setup are common culprits. Check the server response time in PageSpeed Insights; if it is consistently slow, it is time to look at hosting or the backend.

What not to do first

  • Do not chase a perfect 100 score. Aim for passing Core Web Vitals on your key pages, then focus on content and conversions.
  • Do not redesign to fix speed. Most gains come from images, scripts and caching, not a new layout.
  • Do not install yet another "speed" plugin before removing the ones you do not need.

A simple two-week plan

  1. Days 1–2: Run PageSpeed Insights on your five most important pages and note LCP, INP and CLS on mobile.
  2. Days 3–7: Compress and resize images, set image dimensions and lazy-load below-the-fold images.
  3. Days 8–10: Audit third-party scripts and fonts. Remove what you do not need and defer the rest.
  4. Days 11–14: Turn on caching, compression and a CDN, then test again and compare.

Real-user data in Search Console takes about four weeks to fully reflect changes, so keep testing with PageSpeed Insights in the meantime.

When to get help

If your pages still fail Core Web Vitals after these steps, the cause is usually deeper: the theme, the framework or the hosting setup. That is where a development team can help. At GOTEN Digital we build fast websites and apps for Indonesian businesses and can audit an existing site to show you exactly what is slowing it down. Chat with us on WhatsApp for a free consultation.

More from the Journal

Back to Journal