Website review, no card needed
eigerindo.co.id website review
Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 70 checks
This review found 34 issues worth fixing on eigerindo.co.id, 8 of them high impact, across 70 checks. The most urgent: fails Core Web Vitals for real visitors. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 188 ms |
| May 16, 2026 | 182 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 234 ms |
| Jun 13, 2026 | 234 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 198 ms |
| Jul 11, 2026 | 195 ms |
| Jul 18, 2026 | 197 ms |
| Jul 25, 2026 | 190 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 201 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 193 ms |
| Sep 19, 2026 | 193 ms |
| Sep 26, 2026 | 193 ms |
| Oct 3, 2026 | 166 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 184 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
How it loaded on a phone
0.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Improve image delivery
450 ms · 1.5 MB11 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (framerusercontent.com, framer.com and JSDelivr CDN and others), adding 3.4 MB and 871 ms of main-thread time.
framerusercontent.com adds 858 ms
858 msframerusercontent.com costs a phone 858 ms of main-thread work and 3.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.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 92 KiBAbout 92 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,865 HTML elements
The page has 1,865 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
26 KiB23 files are served with short cache lifetimes, so returning visitors download them again (26 KiB).
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: 79 ms
79 msYour server sent the HTML in 79 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 CLS: 0.51
0.51For real visitors the layout shifts by 0.51 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 12.0 s
12.0 sYour largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.7 s
12.7 sThe page becomes fully interactive after 12.7 s. Good is under 3.8 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 188 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 662 ms
662 msReal visitors wait 662 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 86 requests
3.4 MBYour homepage downloads 3.4 MB in 86 requests on a phone: images 2.9 MB (29), scripts 406 KiB (50) and fonts 70 KiB (3). Under 2 MB keeps phones on slow connections fast.
8 images below the first screen load straight away
8 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
88 KiB2 images are downloaded at several times the size a phone draws them, for example cKel8HEQ6FhaKbQzUL50Mz7fCw8.jpg at 800 px wide, shown at 233 px. Resized copies would save about 88 KiB.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 115.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 148 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (13 characters)
Your title is only 13 characters: “EIGERINDO MPI”. 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.
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.
28 internal links, 29 external
The homepage links to 28 pages on eigerindo.co.id and 29 external pages.
5 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “This is the new face of Eigerindo, lets take a look inside PT Eigerindo MPI and revel in the fun of exploring !”.
Canonical URL set
The canonical URL is https://www.eigerindo.co.id/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.eigerindo.co.id/sitemap.xml.
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://www.eigerindo.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 (892 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.eigerindo.co.id/contact-us is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages share 2 titles
/, https://www.eigerindo.co.id/Career, https://www.eigerindo.co.id/About/distribution and https://www.eigerindo.co.id/About/history all use the title “EIGERINDO MPI”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://www.eigerindo.co.id/Career, https://www.eigerindo.co.id/contact-us, https://www.eigerindo.co.id/Division/Distribution, https://www.eigerindo.co.id/About/distribution and https://www.eigerindo.co.id/About/history use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.eigerindo.co.id/Career, https://www.eigerindo.co.id/contact-us, https://www.eigerindo.co.id/Division/Distribution, https://www.eigerindo.co.id/About/distribution and https://www.eigerindo.co.id/About/history have no <h1> headline, so visitors and search engines get no clear main topic.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 5 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 a meta description
All 5 pages that loaded have a meta description.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 478 words of copy
The homepage carries about 478 words of visible text.
1 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Contact Us”, “Shop EIGER” and “Learn More Our Distribution”.
Privacy and tracking
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.
5 other companies contacted
Loading the homepage contacts 5 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 eigerindo.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
- CMS
- Framer
- Hosting
- Framer
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on eigerindo.co.id, including 15 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.