ngkbusi.com website review

55 files are served with short cache lifetimes, so returning visitors download them again (5.7 MB).

20 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

About 478 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.

About 270 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

5 third-party services load with your homepage (Google Tag Manager, Clarity and Google Analytics and others), adding 866 KiB and 542 ms of main-thread time.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 565 ms on a phone.

Google Tag Manager costs a phone 433 ms of main-thread work and 809 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your server takes 665 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

6 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PRODUK UNGGULAN BUSI HARIAN-MU UPGRADE EKONOMIS UPGRADE PER…”.

The page becomes fully interactive after 23.9 s. Good is under 3.8 s.

Visually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

The layout shifts by 0.332 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 199 ms to 403 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 930 ms for your server to start answering (75th percentile). Good is under 800 ms.

33 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 6.6 MB in 79 requests on a phone: images 2.6 MB (33), media 1.9 MB (3) and scripts 1.0 MB (17). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example button-lazada.png at 3,840 px wide, shown at 75 px. Resized copies would save about 1.7 MB.

button-lazada.png weighs 806 KiB. On a phone connection a single image that size takes seconds.

8 images (1.9 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

FA_FakeSP_Legal-Action_Web-Banner.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 1.87 g of CO₂e: 224.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 18 characters: “NGK Busi Indonesia”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://ngkbusi.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 74 pages on ngkbusi.com and 23 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/ and https://ngkbusi.com/did all use the title “NGK Busi Indonesia”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://ngkbusi.com/products, https://ngkbusi.com/did, https://ngkbusi.com/updates, https://ngkbusi.com/updates/view/Editorial, https://ngkbusi.com/updates/view/Tips and https://ngkbusi.com/updates/view/Activity and 6 others use the same meta description. A description written for each page earns more clicks.

https://ngkbusi.com/products, https://ngkbusi.com/did, https://ngkbusi.com/motorsports/domestic and https://ngkbusi.com/about have no <h1> headline, so visitors and search engines get no clear main topic.

https://ngkbusi.com/about and https://ngkbusi.com/about/worldwide have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://ngkbusi.com/did, https://ngkbusi.com/updates and https://ngkbusi.com/updates/view/Editorial took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

38 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,313 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 10 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.