Website review, no card needed
pindad.com website review
Visit site (opens in a new tab)Reviewed 31 October 202645 issues · 84 checks
This review found 45 issues worth fixing on pindad.com, 19 of them high impact, across 84 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 9.8 s |
| May 16, 2026 | 11.3 s |
| May 23, 2026 | 13.1 s |
| May 30, 2026 | 12.4 s |
| Jun 6, 2026 | 12.2 s |
| Jun 13, 2026 | 12.2 s |
| Jun 20, 2026 | 12.3 s |
| Jun 27, 2026 | 12.5 s |
| Jul 4, 2026 | 13.0 s |
| Jul 11, 2026 | 13.4 s |
| Jul 18, 2026 | 13.4 s |
| Jul 25, 2026 | 13.2 s |
| Aug 1, 2026 | 11.7 s |
| Aug 8, 2026 | 9.2 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 5.9 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 6.0 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 6.0 s |
| Oct 17, 2026 | 5.9 s |
| Oct 24, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 115 ms |
| May 16, 2026 | 119 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 114 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 114 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 119 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
Speed
Improve image delivery
67.2 s · 18.7 MB34 images could be 18.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 67.2 s faster on a phone.
Reduce unused CSS
6.5 s · 561 KiBAbout 561 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.
Render-blocking requests
5.5 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Font display
1.8 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.8 s).
Reduce unused JavaScript
1.3 s · 180 KiBAbout 180 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Minify CSS
900 ms · 89 KiB89 KiB could be saved by minifying CSS.
Minify JavaScript
740 ms · 64 KiB64 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
500 ms · 121 KiB6 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
Legacy JavaScript
150 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Document request latency
34 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 172 ms of it running JavaScript. That is comfortably low.
Server response: 462 ms
462 msYour server sent the HTML in 462 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.8 s
4.8 sReal visitors wait 4.8 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 7.7 s
7.7 sThe first text or image appears after 7.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 178.5 s
178.5 sYour largest element takes 178.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MEMBANGUN INFRASTRUKTUR,MEMPERCEPAT KONEKTIVITAS Produk ind…”.
Speed Index: 43.3 s
43.3 sVisually, the page fills in at 43.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 181.5 s
181.5 sThe page becomes fully interactive after 181.5 s. Good is under 3.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 115 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 174 ms
174 msReal visitors wait 174 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Largest content (LCP) got 45% faster for real visitors
-45%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 9.8 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 70 ms
70 msScripts block the page for only 70 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 36.7 MB in 146 requests
36.7 MBYour homepage downloads 36.7 MB in 146 requests on a phone: images 34.5 MB (78), stylesheets 1.2 MB (28) and scripts 714 KiB (30). Under 2 MB keeps phones on slow connections fast.
About 10.4 g of CO₂ per visit
10.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.39 g of CO₂e: 1247.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
34 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: 34 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (27 characters)
Your title is only 27 characters: “PT. Pindad (Persero) - Home”. 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.
6 H1 headlines
There are 6 <h1> headlines (“MEMBANGUN INFRASTRUKTUR,MEMPERCEPAT KONEKTIVITAS”, “TANGGUH DAN ADAFTIF DI SEGALA MEDAN” and “MENJAGA KEDAULATAN, MENGHANCURKAN ANCAMAN”). One clear main headline is easier for people and search engines.
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://pindad.com/sitemap.xml, so Google discovers your pages only by following links.
17 links with vague text
17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No robots.txt
There is no robots.txt at pindad.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
85 internal links, 7 external
The homepage links to 85 pages on pindad.com and 7 external pages.
AI search readiness
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://pindad.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
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.
Text is in the HTML
Your server sends the page's text in the HTML (942 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
/, https://pindad.com/set-language/125/home, https://pindad.com/set-language/107/home and https://pindad.com/home all use the title “PT. Pindad (Persero) - Home”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://pindad.com/set-language/125/home, https://pindad.com/set-language/107/home, https://pindad.com/home, https://pindad.com/profil-perusahaan, https://pindad.com/company-objective-and-target and https://pindad.com/corporate-culture and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://pindad.com/profil-perusahaan, https://pindad.com/company-objective-and-target, https://pindad.com/corporate-culture, https://pindad.com/business-field-and-business-development, https://pindad.com/legality and https://pindad.com/finance have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://pindad.com/set-language/125/home, https://pindad.com/set-language/107/home, https://pindad.com/company-objective-and-target, https://pindad.com/corporate-culture, https://pindad.com/business-field-and-business-development and https://pindad.com/legality and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
4 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
55 small tap targets
55 of 110 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,566 words of copy
The homepage carries about 1,566 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
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 pindad.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
- PT Jalawave Cakrawala
Company
- Founded
- 1808
- Headquarters
- Bandung
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on pindad.com, including 18 speed issues, 9 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.