Website review, no card needed

indonesian-aerospace.com logo

indonesian-aerospace.com website review

Visit site (opens in a new tab)Reviewed 2 November 202640 issues · 78 checks

This review found 40 issues worth fixing on indonesian-aerospace.com, 18 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.4 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20263.0 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
126 ms91 msMay 16Oct 398 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026100 ms
May 30, 2026107 ms
Jul 11, 2026122 ms
Jul 18, 2026114 ms
Jul 25, 2026107 ms
Aug 15, 2026103 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202697 ms
Sep 26, 202697 ms
Oct 3, 202698 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of indonesian-aerospace.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. indonesian-aerospace.com at 0.6 s0.6 s
  2. indonesian-aerospace.com at 1.3 s1.3 s
  3. indonesian-aerospace.com at 1.9 s1.9 s
  4. indonesian-aerospace.com at 2.5 s2.5 s
  5. indonesian-aerospace.com at 3.1 s3.1 s
  6. indonesian-aerospace.com at 3.8 s3.8 s
  7. indonesian-aerospace.com at 4.4 s4.4 s
  8. indonesian-aerospace.com at 5.0 s5.0 s

Speed

9 to fix33
  • Use efficient cache lifetimes

    5.8 s · 53.3 MB

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

  • Render-blocking requests

    6.6 s

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

  • Reduce unused CSS

    2.4 s · 439 KiB

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

  • Reduce unused JavaScript

    1.5 s · 331 KiB

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

  • Font display

    1.4 s

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

  • Mobile performance score: 33

    33/100

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

  • Minify JavaScript

    600 ms · 87 KiB

    87 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    555 KiB

    7 images could be 555 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    440 ms · 85 KiB

    85 KiB could be saved by minifying CSS.

  • Document request latency

    18 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (JSDelivr CDN and Google Fonts), adding 55 KiB and 2 ms of main-thread time.

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 92 ms of it running JavaScript. That is comfortably low.

  • Server response: 42 ms

    42 ms

    Your server sent the HTML in 42 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix50
  • Fails Core Web Vitals for real visitors

    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.

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PT Dirgantara Indonesia (Persero) (Indonesian-aircraft Indu…”. Most of its time is element render delay (3.5 s).

  • Cumulative Layout Shift: 0.801

    0.801

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Time to Interactive: 8.4 s

    8.4 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix43
  • Page weight: 53.4 MB in 56 requests

    53.4 MB

    Your homepage downloads 53.4 MB in 56 requests on a phone: media 49.8 MB (5), images 2.1 MB (15) and scripts 590 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.4 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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 6 images far larger than shown

    41 KiB

    6 images are downloaded at several times the size a phone draws them, for example news_3615.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 41 KiB.

  • About 15.1 g of CO₂ per visit

    15.14 g

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

Accessibility

4 to fixGoogle 9093
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 10 tap targets too small

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

  • Page should contain a level-one heading (1 element)

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9265
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    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

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

  • No X (Twitter) card tag

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

  • 27 internal links, 7 external

    The homepage links to 27 pages on indonesian-aerospace.com and 7 external pages.

2 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “PT Dirgantara Indonesia (Persero)”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://indonesian-aerospace.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (255 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 16 pages share a title

    https://indonesian-aerospace.com/en, https://indonesian-aerospace.com/en/about_us/corporateoverview, https://indonesian-aerospace.com/en/about_us/certificate, https://indonesian-aerospace.com/en/about_us/orgstructure, https://indonesian-aerospace.com/en/about_us/subsidiaries and https://indonesian-aerospace.com/en/gcg/code-of-cg and 10 others all use the title “PT Dirgantara Indonesia (Persero)”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://indonesian-aerospace.com/en/about_us/corporateoverview, https://indonesian-aerospace.com/en/about_us/certificate, https://indonesian-aerospace.com/en/about_us/orgstructure, https://indonesian-aerospace.com/en/about_us/subsidiaries, https://indonesian-aerospace.com/en/gcg/code-of-cg and https://indonesian-aerospace.com/en/portfolio/aircraft and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages with very little text

    https://indonesian-aerospace.com/en/gcg/code-of-cg, https://indonesian-aerospace.com/en/portfolio/aircraft, https://indonesian-aerospace.com/en/portfolio/aircraft_engine_services, https://indonesian-aerospace.com/en/media/photogallery, https://indonesian-aerospace.com/en/media/annual_report and https://indonesian-aerospace.com/en/contact 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.

  • 3 pages slow to respond

    https://indonesian-aerospace.com/en/about_us/subsidiaries, https://indonesian-aerospace.com/en/media/news and https://indonesian-aerospace.com/en/media/photogallery took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 205 words

    The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

  • No risk reducer

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

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 3 email links.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at indonesian-aerospace.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
OVHcloud

Company

Founded
1976
Headquarters
Bandung

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on indonesian-aerospace.com, including 18 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25