Website review, no card needed

newarmada.co.id logo

newarmada.co.id website review

Visit site (opens in a new tab)Reviewed 31 October 202654 issues · 89 checks

This review found 54 issues worth fixing on newarmada.co.id, 19 of them high impact, across 89 checks. The most urgent: page weight: 48.0 MB in 404 requests. 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.7 s1.3 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.5 s
Jun 27, 20262.6 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.6 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Oct 17, 20263.5 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
921 ms0 msMay 9Oct 24562 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026105 ms
May 16, 2026110 ms
May 23, 2026109 ms
May 30, 2026106 ms
Jun 6, 2026105 ms
Jun 13, 2026101 ms
Jun 20, 2026100 ms
Jun 27, 2026128 ms
Jul 4, 2026147 ms
Jul 11, 2026226 ms
Jul 18, 2026311 ms
Jul 25, 2026773 ms
Aug 1, 2026814 ms
Aug 8, 2026737 ms
Aug 15, 2026574 ms
Aug 22, 2026546 ms
Aug 29, 2026523 ms
Sep 5, 2026506 ms
Sep 12, 2026511 ms
Sep 19, 2026501 ms
Sep 26, 2026545 ms
Oct 3, 2026594 ms
Oct 10, 2026648 ms
Oct 17, 2026653 ms
Oct 24, 2026562 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 newarmada.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. newarmada.co.id at 0.6 s0.6 s
  2. newarmada.co.id at 1.2 s1.2 s
  3. newarmada.co.id at 1.8 s1.8 s
  4. newarmada.co.id at 2.3 s2.3 s
  5. newarmada.co.id at 2.9 s2.9 s
  6. newarmada.co.id at 3.5 s3.5 s
  7. newarmada.co.id at 4.1 s4.1 s
  8. newarmada.co.id at 4.7 s4.7 s

Speed

11 to fix63
  • Render-blocking requests

    3.4 s

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

  • Document request latency

    1.1 s

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

  • Reduce initial server response time

    1.1 s

    Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

  • Improve image delivery

    31.1 MB

    21 images could be 31.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    22.8 MB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (JSDelivr CDN, Google Tag Manager and Unpkg and others), adding 588 KiB and 624 ms of main-thread time.

  • Reduce unused JavaScript

    649 KiB

    About 649 KiB of JavaScript is downloaded but never used on this page.

  • JSDelivr CDN adds 251 ms

    251 ms

    JSDelivr CDN costs a phone 251 ms of main-thread work and 190 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.

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Server response: 1.1 s

    1.1 s

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

  • Reduce unused CSS

    280 ms · 45 KiB

    About 45 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • Duplicated JavaScript

    40 KiB

    40 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

13 to fix33
  • 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.

  • Real-user INP: 550 ms

    550 ms

    Real visitors wait 550 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Speed Index: 35.0 s

    35.0 s

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

  • Time to Interactive: 60.8 s

    60.8 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “New Armada Logo”. Most of its time is element render delay (3.5 s).

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Tap response (INP) got 465% slower for real visitors

    +465%

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

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

    +84%

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

  • Real-user TTFB: 983 ms

    983 ms

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

  • Total Blocking Time: 203 ms

    203 ms

    Scripts block taps and scrolling for 203 ms in total while the page loads. Good is under 200 ms.

  • 10 images without width and height

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

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.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 48.0 MB in 404 requests

    48.0 MB

    Your homepage downloads 48.0 MB in 404 requests on a phone: images 39.3 MB (57), scripts 6.1 MB (246) and stylesheets 2.1 MB (63). Under 2 MB keeps phones on slow connections fast.

  • 16 images over 500 KB

    16 images weigh 30.3 MB together. On a phone connection a single image that size takes seconds.

  • 14 images far larger than shown

    8.6 MB

    14 images are downloaded at several times the size a phone draws them, for example 01HMT903QJDA52CKADWAGPYZF4.jpg at 1,600 px wide, shown at 276 px. Resized copies would save about 8.6 MB.

  • 17 images in older formats

    17 images (30.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.

  • 15 images below the first screen load straight away

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

  • About 13.6 g of CO₂ per visit

    13.62 g

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

Accessibility

8 to fixGoogle 8189
  • 14 buttons without a name

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • 2 tap targets too small

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

  • All page content should be contained by landmarks (12 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • No main landmark

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

7 to fixGoogle 9266
  • No H1 headline

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

  • Title is short (10 characters)

    Your title is only 10 characters: “New Armada”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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.

  • Meta description is long (276 characters)

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

  • 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 18 internal links, 10 external

    The homepage links to 18 pages on newarmada.co.id and 10 external pages.

2 checks passed
  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://newarmada.co.id/sitemap.xml.

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://newarmada.co.id/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 (235 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 5 linked pages are broken

    Your homepage links to https://newarmada.co.id/contact, https://newarmada.co.id/product/skylander-r25, https://newarmada.co.id/news/launching-grand-touristo-on-bustruck-south-asia-2025, https://newarmada.co.id/privacy-policy and https://newarmada.co.id/terms-conditions, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://newarmada.co.id/karir has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 3 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 167 words

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

  • 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
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 15 other companies contacted

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

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 newarmada.co.id, 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
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on newarmada.co.id, including 24 speed issues, 7 SEO issues and 4 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