Website review, no card needed

indofarma.id logo

indofarma.id website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 82 checks

This review found 40 issues worth fixing on indofarma.id, 22 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
10.3 s7.0 sMay 30Nov 147.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20268.3 s
Jun 6, 20268.5 s
Jun 13, 20268.9 s
Jun 20, 20268.6 s
Jun 27, 20269.1 s
Jul 4, 20268.9 s
Jul 11, 20268.5 s
Jul 18, 20268.7 s
Jul 25, 20268.9 s
Aug 1, 20269.2 s
Aug 8, 20269.2 s
Aug 15, 20269.5 s
Aug 22, 20268.9 s
Aug 29, 20268.7 s
Sep 5, 20269.2 s
Sep 12, 20269.8 s
Sep 19, 20269.9 s
Sep 26, 20269.1 s
Oct 3, 20269.1 s
Oct 10, 20268.7 s
Oct 17, 20268.7 s
Oct 24, 20269.3 s
Oct 31, 20268.7 s
Nov 7, 20268.1 s
Nov 14, 20267.3 s
Real-visitor tap response (INP)75th percentile, phones
168 ms123 msMay 30Nov 14146 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026155 ms
Jun 6, 2026156 ms
Jun 13, 2026163 ms
Jun 20, 2026161 ms
Jun 27, 2026159 ms
Jul 4, 2026156 ms
Jul 11, 2026146 ms
Jul 18, 2026156 ms
Jul 25, 2026145 ms
Aug 1, 2026149 ms
Aug 8, 2026137 ms
Aug 15, 2026134 ms
Aug 22, 2026141 ms
Aug 29, 2026137 ms
Sep 5, 2026138 ms
Sep 12, 2026131 ms
Sep 19, 2026136 ms
Sep 26, 2026128 ms
Oct 3, 2026136 ms
Oct 10, 2026131 ms
Oct 17, 2026133 ms
Oct 24, 2026138 ms
Oct 31, 2026133 ms
Nov 7, 2026144 ms
Nov 14, 2026146 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 indofarma.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. indofarma.id at 2.0 s2.0 s
  2. indofarma.id at 3.9 s3.9 s
  3. indofarma.id at 5.9 s5.9 s
  4. indofarma.id at 7.8 s7.8 s
  5. indofarma.id at 9.8 s9.8 s
  6. indofarma.id at 11.7 s11.7 s
  7. indofarma.id at 13.7 s13.7 s
  8. indofarma.id at 15.6 s15.6 s

Speed

10 to fix50
  • Reduce unused JavaScript

    18.1 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.1 s faster on a phone.

  • Improve image delivery

    4.8 s · 9.5 MB

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

  • Render-blocking requests

    5.5 s

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

  • Use efficient cache lifetimes

    1.5 s · 1.8 MB

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

  • Font display

    2.1 s

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

  • Reduce unused CSS

    1.8 s · 239 KiB

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

  • YouTube adds 1.6 s

    1.6 s

    YouTube costs a phone 1.6 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 5.0 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 4.3 MB and 1.6 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • 13 long tasks on the main thread

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

  • Minify CSS

    150 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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.

1 checks passed
  • Server response: 442 ms

    442 ms

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

Core Web Vitals

11 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 LCP: 13.1 s

    13.1 s

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

  • Real-user FCP: 11.2 s

    11.2 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 52.9 s

    52.9 s

    Your largest element takes 52.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 24.1 s

    24.1 s

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

  • Time to Interactive: 56.1 s

    56.1 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Real-user INP: 252 ms

    252 ms

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

  • Total Blocking Time: 378 ms

    378 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 8.3 s to 7.3 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 19.4 MB in 214 requests

    19.4 MB

    Your homepage downloads 19.4 MB in 214 requests on a phone: images 14.1 MB (38), scripts 3.9 MB (74) and stylesheets 603 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (47 KiB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.5 g of CO₂ per visit

    5.51 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9598
  • 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.

  • 5 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 8566
  • 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.

  • Title is short (13 characters)

    Your title is only 13 characters: “Indofarma Tbk”. 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 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 X (Twitter) card tag

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

  • 89 internal links, 15 external

    The homepage links to 89 pages on indofarma.id and 15 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://indofarma.id/.

  • 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://indofarma.id/wp-sitemap.xml.

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.

  • No llms.txt

    There is no https://indofarma.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.

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://indofarma.id/sejarah, https://indofarma.id/struktur-perusahaan, https://indofarma.id/visi-dan-misi, https://indofarma.id/corporate-values, https://indofarma.id/dewan-direksi and https://indofarma.id/tanggung-jawab-sosial-perusahaan and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://indofarma.id/sejarah, https://indofarma.id/visi-dan-misi, https://indofarma.id/corporate-values, https://indofarma.id/dewan-direksi, https://indofarma.id/tanggung-jawab-sosial-perusahaan and https://indofarma.id/tata-kelola-perusahaan-yang-baik and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://indofarma.id/sejarah, https://indofarma.id/struktur-perusahaan, https://indofarma.id/visi-dan-misi and https://indofarma.id/corporate-values took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 found) 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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 7389
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was 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

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

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 49 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 2 other companies contacted

    Loading the homepage contacts 2 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 indofarma.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
WordPress
Framework
jQuery
Hosting
Idnic Colo As Id Pt Ardetamedia Global Komputindo

Company

Employees
1,179
Founded
1918
Headquarters
Bekasi

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 indofarma.id, including 21 speed issues, 5 SEO issues and 6 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