Saturday morning, the online store of a clothing brand in Yogyakarta is running a flash sale. At ten o'clock, a broadcast message goes out to tens of thousands of customers. Ten minutes later, the owner checks the sales numbers: not the hundreds of orders he expected, but twenty. He opens his own website on his phone — and waits. The logo appears, then a long pause. Product images fill the screen one by one. The "Buy Now" button can only be tapped after five seconds, and when he taps it, the page jumps upward because the layout shifted. He realizes: his customers left before the website finished loading.
Website speed is no longer just a convenience. It is one of the most decisive factors between making a sale and losing it, and search engines now measure it officially through Core Web Vitals.
This article is a complete web performance optimization guide: what Core Web Vitals are, why they determine rankings and conversions, how to measure your website's condition, and practical improvement steps, from what you can do this week to what needs a developer.
What Are Core Web Vitals?
Core Web Vitals are Google's official set of metrics that measure the real user experience of opening a website. Unlike older technical metrics that only looked at server speed, they focus on what visitors actually feel.
The three main metrics:
LCP (Largest Contentful Paint) measures the time until the largest piece of content on the page — usually the main image, big heading, or video — finishes loading and becomes visible. Simply put: how long does a visitor wait to see the "core" of the page? Google's threshold: LCP of 2.5 seconds or less is considered good.
INP (Interaction to Next Paint) measures the page's responsiveness to user interactions: clicks, taps, or keystrokes. How quickly does the page respond after you press a button? This metric replaced FID (First Input Delay) as an official metric in 2024. Threshold: INP of 200 milliseconds or less is considered good.
CLS (Cumulative Layout Shift) measures how much the page layout shifts unexpectedly while loading. Ever almost tapped a button, then the layout jumped and you tapped an ad instead? That is bad CLS. Threshold: CLS of 0.1 or less is considered good.
Google combines all three in assessments that affect search rankings. Websites that fail these thresholds are not automatically penalized, but websites that meet them gain a real competitive advantage.
Why Website Speed Determines Money
Technical metrics can feel abstract until translated into rupiah. Let's do that translation.
First, conversion. Industry studies show a consistent pattern: the slower the website, the lower the conversion. The exact conversion drop varies by study, but the direction is always the same — some visitors patient enough to wait for a slow page become buyers on a faster website instead. For an online store with tens of thousands of monthly visitors, one second of load time difference can mean tens of millions of rupiah in monthly sales.
Second, search rankings. Core Web Vitals is one of the factors considered by Google's algorithm. Fast, stable pages gain an advantage; slow, janky pages lose to faster competitors in the same search results. Lower rankings mean lower organic traffic, and organic traffic is the cheapest traffic that exists.
Third, ad costs. This is often overlooked: Google Ads gives a quality score for every keyword, and page experience is part of that score. A slow website pays more per click for the same ad position as a fast one. Performance optimization does not just save visitors; it lowers acquisition costs.
Fourth, retention. Research shows users who experience a slow website once are less likely to return. Every bad visit is a permanently lost potential customer, and in the social media era, one bad experience spreads faster than one good one.
For businesses in Indonesia, this dimension matters even more: internet penetration is growing, but network quality varies, and most users access through phones with data plans. A website optimized for mobile and mid-range connections is not a value-add; it is a basic requirement.
Measuring Your Website's Condition
Before fixing, you need to know where you stand. The good news: Core Web Vitals measurement is free with several tools.
PageSpeed Insights
Google's most popular tool. Enter your website's address, and it shows scores for LCP, INP, and CLS, for both mobile and desktop, complete with a prioritized list of issues to fix. It also uses field data from real users (CrUX) if your website has enough traffic, which reflects the actual experience of Indonesian visitors.
Google Search Console
If your website is registered in Search Console, open the "Core Web Vitals" report under Enhancements. Google shows a list of problematic URLs, grouped by metric and device type. This is the most accurate priority map: it shows which pages your users actually experience, not just test results.
Lighthouse in Chrome DevTools
For deep analysis, open your website in Chrome, right-click, select Inspect, open the Lighthouse tab, and run an audit. Results are more technical than PageSpeed Insights, with per-asset details: which images are too large, which JavaScript blocks rendering, and so on.
Web Vitals Extension
This official Google browser extension shows LCP, INP, and CLS scores in real time as you browse. Useful for feeling your website's condition across pages while quickly testing the impact of fixes.
One important note: lab scores (from testing tools) and field scores (from real users) can differ dramatically. Testing tools simulate ideal conditions; real users face slow networks, budget phones, and unstable connections. Do not be satisfied just because PageSpeed Insights shows green; also check real-user data in Search Console.
Understanding the Diagnosis: Most Common Problems
When you open audit results, technical terms can be confusing. Here is a translation of the problems most often found on Indonesian websites, and what they mean.
"Reduce initial server response time" (high TTFB). Your server is slow to answer the first request. Common causes: overloaded cheap hosting, servers far from users, or inefficient applications. Solutions: move to better hosting, enable caching, or use a CDN.
"Eliminate render-blocking resources". Certain CSS and JavaScript files block the page from displaying until they finish downloading. It is like a guest refused entry to the room until all party supplies are arranged, when the guest just wants to sit down first. Solutions: defer non-essential JavaScript, load CSS efficiently, and remove unused files.
"Properly size images". Your images download larger than they are displayed. The classic example: a 3000-pixel photo shown in a 400-pixel box. The file can be 30 times larger than needed. Solutions: resize and compress images, use modern formats like WebP or AVIF.
"Defer offscreen images". Images below the fold download even though visitors have not seen them yet. Solution: lazy loading — images download only as visitors approach them.
"Reduce unused JavaScript/CSS". Your website carries code this page does not use. Common with themes or templates that bundle every feature at once. Solutions: remove or split unused code.
"Avoid enormous network payloads". The total page weight is too large. A healthy page should be under 2 MB total; many Indonesian websites carry far more due to large images and excessive scripts.
"Minimize main-thread work". The browser is too busy running code to respond quickly to user input. Solutions: reduce JavaScript, split large tasks, and avoid heavy continuous animations.
Improvement Strategies: From Quick to Deep
Step 1: Fixes You Can Make This Week
Some fixes have major impact and can be done without deep code changes:
Image compression. Most websites lose most of their speed potential here. Resize images to display size, compress files, and use modern formats. As a reference: a photo that was 2 MB can drop to 200 KB without noticeable visual difference. Many free tools exist, and modern CMS platforms often have automatic plugins.
Enable caching. Caching stores copies of pages and files so returning visitors do not download everything from scratch. Browser caching makes return visits much faster; server-side caching speeds up first visits. On many platforms, this is just enabling a setting or plugin.
Use a CDN. A Content Delivery Network copies your website to servers in various locations, so a visitor in Medan is served by the nearest server instead of one in America or Jakarta. For Indonesia, a CDN with local nodes makes a significant difference, especially for visitors outside Java.
Install a performance plugin. If your website runs on a popular CMS, a good performance plugin combines image compression, caching, and file minification in one setup. Choose one that is well maintained and does not clash with other plugins.
Check hosting. Sometimes the biggest problem is in the foundation: overloaded shared hosting. Moving to better hosting or a managed VPS often delivers the most noticeable speed jump, and costs remain reasonable in the Indonesian market, starting from tens of thousands to a few hundred thousand rupiah per month for business scale.
Step 2: Intermediate Fixes
After the quick steps, it is time to touch page structure:
Defer non-essential JavaScript. Analytics scripts, chat widgets, and media players do not need to block page display. Load them after main content is visible. This technique is called deferring or lazy-loading scripts, and its impact on INP and LCP is often large.
Optimize fonts. Web fonts downloaded in multiple formats and weights can add hundreds of kilobytes. Use modern formats, load only the fonts actually used, and set display swap so text stays visible while fonts load. Invisible text during the first seconds is a commonly ignored problem.
Set up responsive images. One image can be provided in several sizes, and the browser picks the one matching the user's screen: small version for phones, medium for tablets, large for desktops. This differs from mere compression; it ensures phones never receive files designed for large screens.
Simplify the page. A homepage carrying twenty different modules — carousels, five promo blocks, autoplay video — will always be slower than a page with three clear modules. Content curation is the most forgotten performance strategy.
Step 3: Deep Fixes
For serious websites — high-traffic online stores, web apps, or complex platforms:
Code splitting. Application code is split into parts loaded only when needed. Product page visitors do not need to download the code for the admin page. This is front-end developer territory, and its speed impact is enormous.
Server-side rendering or prerendering. Pages rendered on the server arrive at the browser ready to display, instead of waiting for JavaScript to build them from scratch. For modern applications, this often is the difference between a 2-second LCP and a 6-second one.
Advanced caching architectures. API caches, edge caches, and stale-while-revalidate are techniques that make dynamic pages feel as fast as static ones.
Third-party audit. Third-party scripts — analytics, ads, widgets — are the most underrated source of performance damage. Calculate the performance cost of each script: if a chat widget's value (chats) is smaller than its cost (adding 0.8 seconds to LCP for every visitor), consider loading it only on specific pages.
Performance and Business: The Indonesian Perspective
For Indonesian businesses, two contexts make performance optimization different from merely chasing a score.
First, diverse networks. Your visitors range from big cities with fast internet to areas with fluctuating 3G signals. A website optimized for ideal connections will still be slow for some visitors. The right strategy is optimizing for the slowest: reduce page weight, prioritize important content, and ensure the website remains usable on low connections. This technique, called progressive enhancement, is standard practice in countries with diverse infrastructure like Indonesia.
Second, users' data costs. Every kilobyte downloaded is money from your visitors' data plans. An 8 MB page opened thousands of times a day is a burden your visitors carry. Respecting their data costs is part of a good experience — and respected visitors tend to return.
Both contexts strengthen the business argument: the Indonesian market is largely mobile-first, and mobile with diverse connections is where performance truly separates winners.
Performance, Security, and Foundations
A website whose performance is maintained is usually maintained in other ways too. There is a practical relationship between speed and security that is rarely discussed: many performance fixes — HTTPS, updated plugins, clean code, minimized third-party scripts — are the same security layers. A website untouched since launch is usually slow and vulnerable at once. We cover the defense side in our article on website security for business, and both should be maintained in the same rhythm: routine, scheduled, without waiting for a breakdown.
Performance is also not a one-time affair. Google periodically updates its metrics and thresholds, browsers change behavior, and your website grows: new pages, new images, new features. Performance optimization is a maintenance process, not a one-off project. A healthy website is one that is measured and maintained regularly — the same concept as post-launch system maintenance.
Common Optimization Mistakes
Several common mistakes are worth avoiding:
Optimizing only for the score. Chasing green numbers in testing tools without considering real experience can mislead. A perfect lab score does not guarantee a good field experience. Balance: check tool scores, but also check real-user data and feel the website yourself on various connections.
Too many plugins. Every plugin adds code, and code adds weight. A website with thirty optimization plugins is often slower than one with three right ones. Reduce, do not pile up.
Compressing until broken. Images compressed to the limit look pixelated and lower the professional impression. Good compression balances file size and visual quality.
Ignoring mobile. A website optimized only for desktop will fail in Indonesia's mobile-first market. Always measure and optimize the mobile version first.
Stopping after passing. Green metrics today can turn red in six months. Schedule periodic audits, at least quarterly, and monitor Search Console for changes.
When You Need Professional Help
Many performance fixes can be done yourself. But there is a point where professional help becomes the more efficient choice: when the problem lies in application code, hosting architecture, or when your team has no time for technical deep dives.
Signs you need help: scores stay red after basic steps; the website is built with a modern framework needing deep adjustments; or your business depends on online traffic and conversion so much that performance downtime means money lost every day.
Before starting an optimization project with a third party, also read the website cost guide to understand reasonable cost structures, and the guide to choosing a web development service to know what to ask potential partners.
Your First Step This Week
Performance optimization does not have to start with a big project. Follow this order:
- Measure. Open PageSpeed Insights for your homepage and main product pages, mobile version. Record LCP, INP, CLS scores.
- Check Search Console. Open the Core Web Vitals report and see which pages are actually problematic for your users.
- Do the quick steps. Image compression, caching, CDN — three high-impact fixes that can be done in days.
- Measure again. Compare scores before and after. Keep the evidence: score improvements are potential conversion improvements.
Every second you shave off load time is a second that could become a purchase decision. Thousands of visitors, times seconds saved, times the value of each visit — that is the number you are chasing.
The Kartech team in Bandar Lampung helps businesses measure, diagnose, and fix website performance: from image optimization and caching to front-end architecture overhauls, including ongoing measurement after launch. We start from your website's current condition, not from a package. Discuss your needs through the contact page or explore our services.
Your website only has a few seconds to convince a first-time visitor. Make sure those seconds are used well.
