kerjayagroup.com website review

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

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

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

8 third-party services load with your homepage (YouTube, Google Maps and Google Tag Manager and others), adding 1.8 MB and 1.4 s of main-thread time.

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

Your mobile performance score is 51 (desktop: 64). Pages that score under 90 lose visitors before the first paint.

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

YouTube costs a phone 806 ms of main-thread work and 972 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 Maps costs a phone 409 ms of main-thread work and 480 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.

A phone's processor spends 3.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

11 KiB could be saved by minifying CSS.

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

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.

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

5 KiB could be saved by minifying JavaScript.

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

Visually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 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 “Together, we can.”. Most of its time is element render delay (3.6 s).

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

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

Scripts block taps and scrolling for 565 ms in total while the page loads. Good is under 200 ms.

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 8.6 MB in 111 requests on a phone: images 6.2 MB (49), scripts 1.7 MB (35) and stylesheets 360 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

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

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.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

Headings skip levels (h1 → h3 and h3 → h5), 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 21 characters: “Kerjaya Prospek Group”. 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.

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://kerjayagroup.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

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

The homepage links to 37 pages on kerjayagroup.com and 27 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://kerjayagroup.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://kerjayagroup.com/about.php, https://kerjayagroup.com/bod.php, https://kerjayagroup.com/corporate_structure.php, https://kerjayagroup.com/corporate_info.php and https://kerjayagroup.com/construction.php and 1 other all use the title “Kerjaya Prospek Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kerjayagroup.com/about.php, https://kerjayagroup.com/bod.php, https://kerjayagroup.com/corporate_structure.php, https://kerjayagroup.com/corporate_info.php, https://kerjayagroup.com/construction.php and https://kerjayagroup.com/property.php have no meta description, so Google writes the search snippet from whatever text it finds.

https://kerjayagroup.com/about.php, https://kerjayagroup.com/bod.php, https://kerjayagroup.com/corporate_structure.php, https://kerjayagroup.com/corporate_info.php, https://kerjayagroup.com/construction.php and https://kerjayagroup.com/property.php have no <h1> headline, so visitors and search engines get no clear main topic.

https://kerjayagroup.com/corporate_structure.php has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

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