Website review, no card needed

eglinpharma.com logo

eglinpharma.com website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 69 checks

This review found 31 issues worth fixing on eglinpharma.com, 11 of them high impact, across 69 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
7.1 s4.6 sMay 9Oct 246.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.8 s
May 16, 20265.4 s
May 23, 20266.1 s
May 30, 20266.0 s
Jun 6, 20266.1 s
Jun 13, 20266.1 s
Jun 20, 20266.0 s
Jun 27, 20265.8 s
Jul 4, 20265.2 s
Jul 11, 20264.9 s
Jul 18, 20265.7 s
Jul 25, 20265.7 s
Aug 1, 20265.8 s
Aug 8, 20265.8 s
Aug 15, 20265.8 s
Aug 22, 20266.4 s
Aug 29, 20266.6 s
Sep 5, 20266.6 s
Sep 12, 20266.7 s
Sep 19, 20266.6 s
Sep 26, 20266.8 s
Oct 3, 20266.8 s
Oct 10, 20266.7 s
Oct 17, 20266.7 s
Oct 24, 20266.4 s
Real-visitor tap response (INP)75th percentile, phones
308 ms241 msMay 9Oct 24275 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026260 ms
May 16, 2026261 ms
May 23, 2026265 ms
May 30, 2026272 ms
Jun 6, 2026275 ms
Jun 13, 2026278 ms
Jun 20, 2026286 ms
Jun 27, 2026277 ms
Jul 4, 2026268 ms
Jul 11, 2026264 ms
Jul 18, 2026249 ms
Jul 25, 2026293 ms
Aug 1, 2026292 ms
Aug 8, 2026285 ms
Aug 15, 2026281 ms
Aug 22, 2026277 ms
Aug 29, 2026280 ms
Sep 5, 2026291 ms
Sep 12, 2026300 ms
Sep 19, 2026294 ms
Sep 26, 2026286 ms
Oct 3, 2026285 ms
Oct 10, 2026280 ms
Oct 17, 2026277 ms
Oct 24, 2026275 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 eglinpharma.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eglinpharma.com at 1.3 s1.3 s
  2. eglinpharma.com at 2.6 s2.6 s
  3. eglinpharma.com at 3.8 s3.8 s
  4. eglinpharma.com at 5.1 s5.1 s
  5. eglinpharma.com at 6.4 s6.4 s
  6. eglinpharma.com at 7.7 s7.7 s
  7. eglinpharma.com at 9.0 s9.0 s
  8. eglinpharma.com at 10.3 s10.3 s

Speed

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Analytics), adding 189 KiB and 110 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 348 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix0
  • 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.55

    0.55

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

  • Speed Index: 7.4 s

    7.4 s

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

  • Real-user INP: 216 ms

    216 ms

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) got 17% slower for real visitors

    +17%

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

4 checks passed
  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 667 ms

    667 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.053

    0.053

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

Images and page weight

6 to fix33
  • 1 image over 500 KB

    hero1.5de69b0c.webp weighs 3.4 MB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    3.6 MB

    5 images are downloaded at several times the size a phone draws them, for example hero1.5de69b0c.webp at 5,120 px wide, shown at 390 px. Resized copies would save about 3.6 MB.

  • Page weight: 3.0 MB in 33 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 33 requests on a phone: images 2.5 MB (13), scripts 376 KiB (15) and fonts 48 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    factory2.c9a75a8a.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images in older formats

    4 images (651 KiB) 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.

  • 1 image below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.84 g

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

Accessibility

4 to fixGoogle 9091
  • 5 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 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 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10075
  • No structured data

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

  • Meta description is short (59 characters)

    Your meta description is only 59 characters: “Perusahaan Industri Obat Tradisional berkualitas sejak 1973”. 70 to 160 characters is enough to sell the click.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Selamat datang di PT. EAGLE INDO PHARMA”, “Pengalaman Lebih dari 50 Tahun” and “Obat Tradisional Berkualitas”). 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://eglinpharma.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 15 internal links, 4 external

    The homepage links to 15 pages on eglinpharma.com and 4 external pages.

2 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “PT. EAGLE INDO PHARMA - CAP LANG”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://eglinpharma.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

    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 (568 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 3 pages share a title

    /, https://eglinpharma.com/visi-dan-misi and https://eglinpharma.com/karir all use the title “PT. EAGLE INDO PHARMA - CAP LANG”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://eglinpharma.com/visi-dan-misi and https://eglinpharma.com/karir use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://eglinpharma.com/visi-dan-misi and https://eglinpharma.com/karir have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://eglinpharma.com/karir has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 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 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 small tap targets

    5 of 16 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

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

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • 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 488 words of copy

    The homepage carries about 488 words of visible text.

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 eglinpharma.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
Next.js
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on eglinpharma.com, including 4 speed issues, 6 SEO issues and 5 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
eglinpharma.com website review: scores and fixes