zirmaes.com website review

2 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.7 s faster on a phone.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 56 KiB and 33 ms of main-thread time.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Utama ALAM128”.

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

The layout shifts by 0.336 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 see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

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

banner-alam128.webp weighs 2.5 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example banner-alam128.webp at 1,254 px wide, shown at 296 px. Resized copies would save about 1.3 MB.

Your homepage downloads 2.6 MB in 10 requests on a phone: images 2.5 MB (2), scripts 33 KiB (3) and fonts 22 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

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

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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 145 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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