Website review, no card needed

amt-it.com logo

amt-it.com website review

Visit site (opens in a new tab)Reviewed 25 October 202630 issues · 67 checks

This review found 30 issues worth fixing on amt-it.com, 7 of them high impact, across 67 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
3.5 s2.8 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.3 s
May 9, 20263.4 s
May 16, 20263.3 s
May 23, 20263.2 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
137 ms103 msMay 2Oct 17111 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026124 ms
May 16, 2026109 ms
May 23, 2026118 ms
May 30, 2026123 ms
Jun 6, 2026127 ms
Jun 13, 2026127 ms
Jun 20, 2026126 ms
Jun 27, 2026127 ms
Jul 4, 2026114 ms
Jul 11, 2026131 ms
Jul 18, 2026122 ms
Jul 25, 2026116 ms
Aug 1, 2026111 ms
Aug 8, 2026108 ms
Aug 15, 2026110 ms
Aug 22, 2026107 ms
Sep 5, 2026133 ms
Sep 12, 2026126 ms
Sep 19, 2026114 ms
Sep 26, 2026126 ms
Oct 3, 2026122 ms
Oct 10, 2026115 ms
Oct 17, 2026111 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 amt-it.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amt-it.com at 0.7 s0.7 s
  2. amt-it.com at 1.4 s1.4 s
  3. amt-it.com at 2.1 s2.1 s
  4. amt-it.com at 2.8 s2.8 s
  5. amt-it.com at 3.6 s3.6 s
  6. amt-it.com at 4.3 s4.3 s
  7. amt-it.com at 5.0 s5.0 s
  8. amt-it.com at 5.7 s5.7 s

Speed

8 to fix52
  • Render-blocking requests

    4.2 s

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

  • Improve image delivery

    450 ms · 997 KiB

    4 images could be 997 KiB 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.

  • Reduce unused JavaScript

    900 ms · 153 KiB

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

  • Mobile performance score: 52

    52/100

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

  • Reduce unused CSS

    750 ms · 172 KiB

    About 172 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Font display

    750 ms

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

  • Google Tag Manager adds 269 ms

    269 ms

    Google Tag Manager costs a phone 269 ms of main-thread work and 180 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.

  • Main-thread work: 2.6 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, AddToAny and WordPress Site Stats and others), adding 315 KiB and 286 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    21 KiB

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

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

1 checks passed
  • Server response: 308 ms

    308 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Largest Contentful Paint: 14.0 s

    14.0 s

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

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Total Blocking Time: 258 ms

    258 ms

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

  • Cumulative Layout Shift: 0.1

    0.1

    The layout shifts by 0.1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest content (LCP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user INP: 107 ms

    107 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

Images and page weight

1 to fix50
  • Page weight: 3.1 MB in 115 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 115 requests on a phone: images 1.9 MB (17), scripts 538 KiB (48) and fonts 403 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

Accessibility

2 to fix92
  • 31 links without text

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

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 9282
  • Title is short (16 characters)

    Your title is only 16 characters: “AMT IT Solutions”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 7 H1 headlines

    There are 7 <h1> headlines (“”, “” and “LEADING”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “WebSite: missing name”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 111 internal links, 19 external

    The homepage links to 111 pages on amt-it.com and 19 external pages.

5 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “AMT IT Solution adalah Perusahaan yang bergerak dibidang IT Solution berlokasi di Jakarta. Kami menyediakan solusi tekn…”.

  • Canonical URL set

    The canonical URL is https://amt-it.com/.

  • 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://amt-it.com/sitemap.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

2 to fix70
  • 11 linked pages are broken

    Your homepage links to https://amt-it.com/solutions/governance-risk-compliance, https://amt-it.com/solutions/information-management, https://amt-it.com/solutions/information-security, https://amt-it.com/solutions/infrastructure-series, https://amt-it.com/solutions/network-optimization and https://amt-it.com/solutions/robotic-process-automation and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://amt-it.com/f5-case-study has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.

5 checks passed
  • 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 console error

    1 error was logged to the browser console during Google's test (“Failed to set referrer policy: The value '' is not one of 'no-referrer', 'no-referrer-when-downgrad…”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,224 words of copy

    The homepage carries about 1,224 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Subscribe to my rss feed”.

  • 4 short forms

    4 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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 amt-it.com, 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
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 30 issues on amt-it.com, including 18 speed issues, 4 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