mmsgroup.co.id website review

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

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

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 536 KiB of JavaScript is downloaded but never used on this page.

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.1 MB and 337 ms of main-thread time.

YouTube costs a phone 322 ms of main-thread work and 1,006 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “20 Tahun MMSGI Berdayakan Masa Depan “Berdayakan Masa Depan…”. Most of its time is resource load delay (4.1 s).

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

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 129 requests on a phone: images 2.7 MB (22), scripts 1.2 MB (43) and fonts 350 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example CFX-TOWER-2-2-1-scaled.jpg at 2,253 px wide, shown at 358 px. Resized copies would save about 160 KiB.

2 images (294 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 further down the page (87 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 29 characters: “Beranda - MMS Group Indonesia”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 96 pages on mmsgroup.co.id and 6 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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.

There is no https://www.mmsgi.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.

/ and https://www.mmsgi.co.id/en all use the title “Beranda - MMS Group Indonesia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mmsgi.co.id/tentang-mmsgi, https://www.mmsgi.co.id/mms-resources, https://www.mmsgi.co.id/mms-land, https://www.mmsgi.co.id/mms-solution, https://www.mmsgi.co.id/esg and https://www.mmsgi.co.id/esg/environment and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mmsgi.co.id/tentang-mmsgi, https://www.mmsgi.co.id/esg/environment, https://www.mmsgi.co.id/esg/social, https://www.mmsgi.co.id/esg/governance and https://www.mmsgi.co.id/line have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 375 words of visible text.

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

Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.