Website review, no card needed

ams.co.id logo

ams.co.id website review

Visit site (opens in a new tab)Reviewed 20 October 202634 issues · 77 checks

This review found 34 issues worth fixing on ams.co.id, 11 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
2.5 s2.0 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
112 ms84 msMay 2Oct 1799 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026104 ms
May 9, 2026100 ms
May 16, 2026106 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026102 ms
Jun 13, 2026102 ms
Jun 20, 2026104 ms
Jun 27, 2026106 ms
Jul 4, 2026109 ms
Jul 11, 2026105 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 2026101 ms
Aug 15, 2026100 ms
Aug 22, 202699 ms
Aug 29, 202696 ms
Sep 5, 202692 ms
Sep 12, 202687 ms
Sep 19, 202688 ms
Sep 26, 202690 ms
Oct 3, 202693 ms
Oct 10, 202695 ms
Oct 17, 202699 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 ams.co.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ams.co.id at 0.9 s0.9 s
  2. ams.co.id at 1.8 s1.8 s
  3. ams.co.id at 2.8 s2.8 s
  4. ams.co.id at 3.7 s3.7 s
  5. ams.co.id at 4.6 s4.6 s
  6. ams.co.id at 5.5 s5.5 s
  7. ams.co.id at 6.4 s6.4 s
  8. ams.co.id at 7.4 s7.4 s

Speed

7 to fix55
  • Render-blocking requests

    6.5 s

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

  • Use efficient cache lifetimes

    4.1 s · 1.5 MB

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

  • Reduce unused CSS

    2.6 s · 633 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    770 ms · 228 KiB

    About 228 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.

  • Font display

    950 ms

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

  • Improve image delivery

    300 ms · 295 KiB

    6 images could be 295 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 3 third-party services on the page

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

  • Minify JavaScript

    70 ms · 3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Document request latency

    28 KiB

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

2 checks passed
  • Server response: 489 ms

    489 ms

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

  • Main-thread work: 0.4 s

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

Core Web Vitals

7 to fix100
  • 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.

  • First Contentful Paint: 9.1 s

    9.1 s

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

  • Largest Contentful Paint: 9.9 s

    9.9 s

    Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Best Distribution and Marketing Company”. Most of its time is element render delay (5.4 s).

  • Speed Index: 14.2 s

    14.2 s

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

  • Time to Interactive: 9.9 s

    9.9 s

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

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.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

    -5%

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

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

    +13%

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

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • 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.007

    0.007

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix88
  • An image on the first screen is lazy-loaded

    gedung.jpg 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).

  • 1 image far larger than shown

    168 KiB

    1 image is downloaded at several times the size a phone draws it, for example gedung.jpg at 1,800 px wide, shown at 360 px. Resized copies would save about 168 KiB.

  • 2 images in older formats

    2 images (303 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.

  • 4 images below the first screen load straight away

    4 images further down the page (94 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.51 g

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

1 checks passed
  • Page weight: 1.8 MB in 42 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 42 requests on a phone: stylesheets 674 KiB (15), scripts 463 KiB (12) and images 397 KiB (6). That is a lean page.

Accessibility

4 to fixGoogle 9093
  • Elements must only use permitted ARIA attributes (6 elements)

    Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

    4 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 (16 elements)

    All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10078
  • Title is short (4 characters)

    Your title is only 4 characters: “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.

  • 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at ams.co.id/robots.txt, the first file search crawlers ask for.

  • 33 internal links, 1 external

    The homepage links to 33 pages on ams.co.id and 1 external page.

3 checks passed
  • Meta description: 91 characters

    Your meta description is 91 characters: “Marketer and distributor of pharmaceutical product, consumer product and medical healthcare”.

  • One H1 headline

    Your main headline reads: “The Best Distribution and Marketing Company”.

  • XML sitemap found

    Your XML sitemap is reachable at https://ams.co.id/sitemap.xml.

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://ams.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

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

Other pages

4 to fix79
  • 5 linked pages hidden from search

    https://ams.co.id/com/news-events, https://ams.co.id/com/contact-us/vacancy, https://ams.co.id/com/vacancy, https://ams.co.id/com/news-events/cegah-penyebaran-covid-19 and https://ams.co.id/com/news-events/penanganan-keluhan-pelanggan are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages share 2 titles

    https://ams.co.id/com/services and https://ams.co.id/com/our-services all use the title “Services”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://ams.co.id/com/about, https://ams.co.id/com/about/branch-offices, https://ams.co.id/com/about/ams-marketing, https://ams.co.id/com/services, https://ams.co.id/com/partners and https://ams.co.id/com/news-events and 7 others use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://ams.co.id/com/about/ams-marketing, https://ams.co.id/com/services, https://ams.co.id/com/partners, https://ams.co.id/com/news-events, https://ams.co.id/com/contact-us and https://ams.co.id/com/contact-us/vacancy and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://ams.co.id/com/about/branch-offices and https://ams.co.id/com/contact-us have 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.

  • 14 internal pages checked

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

4 checks passed
  • Linked pages load

    All 14 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 13 pages that loaded have a meta description.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 7 small tap targets

    7 of 17 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

2 to fix79
  • No social proof

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

  • Only about 239 words

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

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact us”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

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.

  • 3 cookies set on arrival

    3

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 ams.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
Joomla
Framework
jQuery
Analytics
Google Analytics

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 ams.co.id, including 14 speed issues, 5 SEO issues and 2 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