mnc-insurance.com website review

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

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

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

24 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

96 KiB could be saved by minifying JavaScript.

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

4 third-party services load with your homepage (JSDelivr CDN, Cloudflare CDN and Google Fonts and others), adding 323 KiB and 20 ms of main-thread time.

13 KiB could be saved by minifying CSS.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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

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

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Melindungi yang Berarti, Menenangkan Hati”. Most of its time is element render delay (4.6 s).

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

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

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.

Your homepage downloads 9.5 MB in 77 requests on a phone: images 8.3 MB (42), scripts 876 KiB (23) and fonts 307 KiB (3). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example CmsFile.ashx at 1,600 px wide, shown at 326 px. Resized copies would save about 588 KiB.

20 images (5.4 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.

14 images further down the page (3.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

6 tap targets are too small or too close together to hit reliably with a finger.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings skip levels (h1 → h3, h3 → 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 13 characters: “MNC Insurance”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 12 <h1> headlines (“Melindungi yang Berarti, Menenangkan Hati”, “Proteksi Mudah Liburan Bebas Resah” and “Wujudkan Tata Kelola yang Bersih dengan Berani La…”). One clear main headline is easier for people and search engines.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://mnc-insurance.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mnc-insurance.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 59 pages on mnc-insurance.com and 21 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://mnc-insurance.com/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://mnc-insurance.com/AboutCompany/vision.aspx, https://mnc-insurance.com/Media/Event.aspx, https://mnc-insurance.com/AboutCompany/csr.aspx, https://mnc-insurance.com/AboutCompany/corporate.aspx and https://mnc-insurance.com/AboutCompany/organization.aspx and 10 others all use the title “MNC Insurance”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mnc-insurance.com/AboutCompany/vision.aspx, https://mnc-insurance.com/Media/Event.aspx, https://mnc-insurance.com/AboutCompany/csr.aspx, https://mnc-insurance.com/AboutCompany/corporate.aspx, https://mnc-insurance.com/AboutCompany/organization.aspx and https://mnc-insurance.com/AboutCompany/management.aspx and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mnc-insurance.com/AboutCompany/vision.aspx, https://mnc-insurance.com/Media/Event.aspx, https://mnc-insurance.com/AboutCompany/csr.aspx and https://mnc-insurance.com/AboutCompany/corporate.aspx took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 33 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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

3 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 364 words of visible text.

Opening the homepage sets 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.