jablock.co website review

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

The page has 3,935 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Google Maps costs a phone 158 ms of main-thread work and 329 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.

Google CDN costs a phone 65 ms of main-thread work and 352 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.

6 third-party services load with your homepage (Google Maps, Google CDN and Cloudflare and others), adding 732 KiB and 239 ms of main-thread time.

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

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

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.

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

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

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

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.24 g of CO₂e: 29.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Certain ARIA roles must be contained by particular parents: 18 elements on the page fail this check, rated critical by axe-core.

10 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 3 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.

1 dropdown has no label.

ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 12 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (34 elements).

Your title is 75 characters, so Google will cut it off around 60: “BETON88: Solusi Bahan Bangunan Blok Beton Berkualitas untuk Konstruksi Kuat”.

25 links have no real href, so search engines can't follow them.

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

The homepage links to 68 pages on jablock.co and 65 external pages.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to https://jablock.co/about, https://jablock.co/kebijakan-privasi, https://jablock.co/legal and https://jablock.co/sitemap, which answer with an error. Visitors hit a dead end and search engines drop them.

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

7 images failed to load on a phone, for example https://res.cloudinary.com/vtevsnhx/image/upload/v1787907074/AASS.png.

51 of 71 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 “Failed to load resource: the server responded with a status of 401 ()”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,658 words of visible text.

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.