Website review, no card needed
biofarma.co.id website review
Visit site (opens in a new tab)Reviewed 3 November 202638 issues · 88 checks
This review found 38 issues worth fixing on biofarma.co.id, 12 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 116 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 118 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 117 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 125 ms |
| Oct 31, 2026 | 122 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.7 s
1.4 s
2.0 s
2.7 s
3.4 s
4.1 s
4.8 s
5.4 s
Speed
Reduce unused JavaScript
2.6 s · 520 KiBAbout 520 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 496 KiB13 files are served with short cache lifetimes, so returning visitors download them again (496 KiB).
Improve image delivery
1.1 s · 1.5 MB9 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 1.1 s faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, omnix.co.id and go.id and others), adding 1.4 MB and 527 ms of main-thread time.
Render-blocking requests
600 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Google Tag Manager adds 323 ms
323 msGoogle Tag Manager costs a phone 323 ms of main-thread work and 584 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.
omnix.co.id adds 185 ms
185 msomnix.co.id costs a phone 185 ms of main-thread work and 537 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 193 ms. During a long task the page ignores taps.
Reduce unused CSS
97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 736 ms of it running JavaScript. That is comfortably low.
Server response: 78 ms
78 msYour server sent the HTML in 78 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide imunisasi (2)”.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 271 ms
271 msScripts block taps and scrolling for 271 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 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-10-31, real Chrome visitors' tap response (inp) went from 116 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 686 ms
686 msReal visitors wait 686 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image over 500 KB
untitled-design-6-4590-340_thumb.png weighs 649 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
646 KiB1 image is downloaded at several times the size a phone draws it, for example untitled-design-6-4590-340_thumb.png at 4,590 px wide, shown at 105 px. Resized copies would save about 646 KiB.
Page weight: 3.8 MB in 64 requests
3.8 MBYour homepage downloads 3.8 MB in 64 requests on a phone: images 2.1 MB (26), scripts 1.1 MB (16) and other files 276 KiB (7). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.7 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.
5 images below the first screen load straight away
5 images further down the page (171 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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 (h3 → h6), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (4 elements).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 (243 characters)
Your meta description is 243 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.biofarma.co.id/sitemap.xml, so Google discovers your pages only by following links.
18 links crawlers can't follow
18 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
100 internal links, 38 external
The homepage links to 100 pages on biofarma.co.id and 38 external pages.
2 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Biofarma | The Leading Vaccine Manufacturer in Indonesia”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.biofarma.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 (664 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://www.biofarma.co.id/en/biofarma all use the title “Biofarma | The Leading Vaccine Manufacturer in Indonesia”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without an H1
https://www.biofarma.co.id/en/biofarma, https://www.biofarma.co.id/id/holding-bumn-farmasi, https://www.biofarma.co.id/id/pt-bio-farma-persero, https://www.biofarma.co.id/id/kimia-farma-tbk-kaef, https://www.biofarma.co.id/id/indofarma-tbk-inaf and https://www.biofarma.co.id/id/pt-inuki-persero and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.biofarma.co.id/en/biofarma, https://www.biofarma.co.id/id/about-us, https://www.biofarma.co.id/id/holding-bumn-farmasi, https://www.biofarma.co.id/id/pt-bio-farma-persero and https://www.biofarma.co.id/id/researcher took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
12 small tap targets
12 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.
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 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.
About 523 words of copy
The homepage carries about 523 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Call Center 1500810” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
11 other companies contacted
Loading the homepage contacts 11 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 biofarma.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- PT Jalawave Cakrawala
Company
- Headquarters
- Bandung
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on biofarma.co.id, including 15 speed issues, 7 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.