sinarmas.co.id website review

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

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.

1.3 MB could be saved by minifying JavaScript.

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

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

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

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

68 KiB could be saved by minifying CSS.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 956 KiB and 426 ms of main-thread time.

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

1 image could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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.

Your largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Perusahaan Asuransi Umum dengan Penghargaan The Excellent P…”.

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 48 requests on a phone: scripts 3.4 MB (11), stylesheets 411 KiB (5) and images 269 KiB (17). Under 2 MB keeps phones on slow connections fast.

3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example banner-home-personal-mobile.jpg at 1,563 px wide, shown at 178 px. Resized copies would save about 885 KiB.

11 images (2.8 MB) 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.

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

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

2 images have no alt text, which hurts accessibility and image search.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 82 characters, so Google will cut it off around 60: “Melayani Dengan Hati Lebih Dari 40 Tahun - Asuransi Sinar Mas - Asuransi Sinar Mas”.

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

Your meta description is 243 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

The homepage links to 17 pages on sinarmas.co.id and 7 external pages.

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.

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

https://sinarmas.co.id/read/all declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://sinarmas.co.id/personal/produk and https://sinarmas.co.id/personal/layanan all use the title “Produk & Layanan - Asuransi Sinar Mas”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sinarmas.co.id/personal/produk, https://sinarmas.co.id/personal/layanan, https://sinarmas.co.id/kontak, https://sinarmas.co.id/bisnis and https://sinarmas.co.id/personal use the same meta description. A description written for each page earns more clicks.

https://sinarmas.co.id/call-me, https://sinarmas.co.id/personal/produk, https://sinarmas.co.id/produk-online, https://sinarmas.co.id/personal/layanan, https://sinarmas.co.id/read/all and https://sinarmas.co.id/csr and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.google.com/cse/static/element/dc6f600a0d4404e5/default_v6+en.css' from origin …”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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 8 cookies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.