rumakuko.com website review

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

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Cloudflare and Cloudflare CDN and others), adding 391 KiB and 317 ms of main-thread time.

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

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

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

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

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

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Buat Bio link di Jagel”.

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

1 image 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.

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

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

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

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

Your meta description is only 65 characters: “Buat Link-in-bio untuk hubungkan semua bisnismu & perluas koneksi”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 9 pages on rumakuko.com and 9 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://web.rumakuko.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.

Your homepage links to https://web.rumakuko.com/career, which answers with an error. Visitors hit a dead end and search engines drop it.

https://web.rumakuko.com/cara-membuat-aplikasi has no <title>, so Google invents the link text in results.

https://web.rumakuko.com/cara-membuat-aplikasi has no meta description, so Google writes the search snippet from whatever text it finds.

https://web.rumakuko.com/cara-membuat-aplikasi has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

Requests the notification permission on page load.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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.

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