Website review, no card needed

indomobilnissan.com logo

indomobilnissan.com website review

Visit site (opens in a new tab)Reviewed 17 November 202636 issues · 62 checks

This review found 36 issues worth fixing on indomobilnissan.com, 14 of them high impact, across 62 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
2.2 s1.8 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Nov 7, 20262.0 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
170 ms151 msMay 30Oct 24162 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026154 ms
Jun 6, 2026162 ms
Jun 13, 2026161 ms
Jun 20, 2026154 ms
Jun 27, 2026167 ms
Jul 4, 2026156 ms
Jul 11, 2026156 ms
Jul 18, 2026168 ms
Jul 25, 2026156 ms
Aug 1, 2026153 ms
Aug 8, 2026162 ms
Aug 15, 2026153 ms
Aug 22, 2026164 ms
Aug 29, 2026162 ms
Sep 5, 2026159 ms
Sep 12, 2026163 ms
Sep 19, 2026161 ms
Sep 26, 2026160 ms
Oct 3, 2026165 ms
Oct 24, 2026162 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 indomobilnissan.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. indomobilnissan.com at 1.5 s1.5 s
  2. indomobilnissan.com at 3.0 s3.0 s
  3. indomobilnissan.com at 4.5 s4.5 s
  4. indomobilnissan.com at 6.0 s6.0 s
  5. indomobilnissan.com at 7.5 s7.5 s
  6. indomobilnissan.com at 9.1 s9.1 s
  7. indomobilnissan.com at 10.6 s10.6 s
  8. indomobilnissan.com at 12.1 s12.1 s

Speed

12 to fix41
  • Use efficient cache lifetimes

    7.5 s · 11.1 MB

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

  • Improve image delivery

    6.3 s · 8.1 MB

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

  • Render-blocking requests

    1.4 s

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

  • Font display

    1.3 s

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

  • Mobile performance score: 41

    41/100

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

  • Reduce unused JavaScript

    950 ms · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 950 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Amazon Web Services and Clarity and others), adding 2.2 MB and 827 ms of main-thread time.

  • Reduce unused CSS

    160 ms · 281 KiB

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

  • 11 long tasks on the main thread

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

  • Google Tag Manager adds 285 ms

    285 ms

    Google Tag Manager costs a phone 285 ms of main-thread work and 317 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: 3.0 s

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

  • Amazon Web Services adds 161 ms

    161 ms

    Amazon Web Services costs a phone 161 ms of main-thread work and 1.3 MB 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.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 200 ms

    200 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “promo terbaru indomobil nissan indonesia”.

  • Time to Interactive: 43.6 s

    43.6 s

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

  • Speed Index: 12.3 s

    12.3 s

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

  • Cumulative Layout Shift: 0.282

    0.282

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

  • Real-user TTFB: 836 ms

    836 ms

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

  • Total Blocking Time: 408 ms

    408 ms

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix0
  • Page weight: 13.1 MB in 130 requests

    13.1 MB

    Your homepage downloads 13.1 MB in 130 requests on a phone: images 8.6 MB (41), scripts 3.8 MB (45) and stylesheets 348 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 3.7 g of CO₂ per visit

    3.72 g

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

Accessibility

4 to fix76
  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 24 text elements with low contrast

    24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 links without text

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

  • 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 (h1 → h5, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

SEO

5 to fixGoogle 8381
  • No structured data

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

  • 5 H1 headlines

    There are 5 <h1> headlines (“Vehicles Line - Up”, “Book a Test Drive” and “Locate our Network”). One clear main headline is easier for people and search engines.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at indomobilnissan.com/robots.txt, the first file search crawlers ask for.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 74 internal links, 11 external

    The homepage links to 74 pages on indomobilnissan.com and 11 external pages.

4 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Indomobil Nissan - Jaringan Dealer, Service & Maintenance, Body Repair, dan penyedia Sparepart resmi mobil Nissan di In…”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Indomobil Nissan - Nissan Indonesia”.

  • Canonical URL set

    The canonical URL is https://www.indomobilnissan.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix83
  • 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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

1 to fix0
  • 2 linked pages are broken

    Your homepage links to https://www.indomobilnissan.com/cars/march and https://www.indomobilnissan.com/cars/elgrand, which answer with an error. Visitors hit a dead end and search engines drop them.

Best practices

2 to fixGoogle 7388
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 console errors

    4 errors were logged to the browser console during Google's test (“Access to XMLHttpRequest at 'https://www.instagram.com/indomobilnissan/' from origin 'https://www.i…”).

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. 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.

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

  • About 1,189 words of copy

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

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Get a Brochure”, “Request Update” and “Book a Test Drive”.

  • Analytics in place

    Analytics detected: Google Analytics.

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 indomobilnissan.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
Analytics
Google Analytics
Hosting
PT Telekomunikasi Indonesia

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on indomobilnissan.com, including 20 speed issues, 5 SEO issues and 2 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