Website review, no card needed

hanindogroup.com logo

hanindogroup.com website review

Visit site (opens in a new tab)Reviewed 24 October 202634 issues · 76 checks

This review found 34 issues worth fixing on hanindogroup.com, 14 of them high impact, across 76 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

Full-page screenshot of hanindogroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hanindogroup.com at 1.4 s1.4 s
  2. hanindogroup.com at 2.9 s2.9 s
  3. hanindogroup.com at 4.3 s4.3 s
  4. hanindogroup.com at 5.8 s5.8 s
  5. hanindogroup.com at 7.2 s7.2 s
  6. hanindogroup.com at 8.6 s8.6 s
  7. hanindogroup.com at 10.1 s10.1 s
  8. hanindogroup.com at 11.5 s11.5 s

Speed

9 to fix53
  • Render-blocking requests

    12.3 s

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

  • Use efficient cache lifetimes

    8.2 s · 1.7 MB

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

  • Reduce unused CSS

    2.9 s · 512 KiB

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

  • Reduce unused JavaScript

    1.8 s · 365 KiB

    About 365 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Font display

    1.4 s

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

  • Mobile performance score: 53

    53/100

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

  • Improve image delivery

    450 ms · 146 KiB

    8 images could be 146 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.

  • Minify CSS

    450 ms · 88 KiB

    88 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    400 ms · 33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google/Doubleclick Ads and others), adding 309 KiB and 184 ms of main-thread time.

  • Minify JavaScript

    160 ms · 42 KiB

    42 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 226 ms

    226 ms

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

Core Web Vitals

5 to fix64
  • First Contentful Paint: 9.7 s

    9.7 s

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

  • Largest Contentful Paint: 14.9 s

    14.9 s

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

  • Speed Index: 14.6 s

    14.6 s

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

  • Time to Interactive: 14.9 s

    14.9 s

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

  • 6 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.069

    0.069

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

  • Total Blocking Time: 126 ms

    126 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.0 MB in 83 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 83 requests on a phone: scripts 942 KiB (29), stylesheets 592 KiB (23) and images 393 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (812 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.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7286
  • Images must have alternative text (10 elements)

    Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (22 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 9 text elements with low contrast

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

  • 7 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 29 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10079
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 1 problem

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

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

  • 60 internal links, 11 external

    The homepage links to 60 pages on hanindogroup.com and 11 external pages.

4 checks passed
  • Meta description: 95 characters

    Your meta description is 95 characters: “Hanindo Group | Your Solution Provider (Official Distributor of Gilbarco Vedeer-Root Indonesia)”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Welcome to the Hanindo Group | Your Solution Provider”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://hanindogroup.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

Other pages

100
  • 1 page slow to respond

    https://hanindogroup.com/fire-fighting took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 18 small tap targets

    18 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions or the arguments objects fo…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 317 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “[object Object]”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before 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

    5

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 hanindogroup.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
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 hanindogroup.com, including 14 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