pentechsolution.com.my website review

About 809 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

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

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

Your mobile performance score is 46 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (Google CDN, Hotjar and Facebook and others), adding 1.7 MB and 827 ms of main-thread time.

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

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

7 images could be 412 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

5 KiB could be saved by minifying JavaScript.

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.

Real visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Malaysia's IT Solution Provider”. Most of its time is element render delay (8.4 s).

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

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

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

The layout shifts by 0.198 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 3.6 MB in 99 requests on a phone: scripts 1.8 MB (41), images 917 KiB (18) and other files 349 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images (513 KiB) 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.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 138 characters, so Google will cut it off around 60: “IT Managed Service Provider In Malaysia | IT Solutions Malaysia | Data Center Specialist …”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 41 pages on pentechsolution.com.my and 1 external page.

There is no https://pentechsolution.com.my/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://pentechsolution.com.my/contacts, which answers with an error. Visitors hit a dead end and search engines drop it.

https://pentechsolution.com.my/investor-relations has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pentechsolution.com.my/infrastructure-solution, whose canonical is https://pentechsolution.com.my/service/infrastructure-solution. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pentechsolution.com.my/partners, https://pentechsolution.com.my/about-us, https://pentechsolution.com.my/investor-relations and https://pentechsolution.com.my/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://pentechsolution.com.my/investor-relations and https://pentechsolution.com.my/contact-us have 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.

https://pentechsolution.com.my/about-us, https://pentechsolution.com.my/news, https://pentechsolution.com.my/careers-it-solutions-malaysia, https://pentechsolution.com.my/investor-relations, https://pentechsolution.com.my/contact-us and https://pentechsolution.com.my/supply-of-hardware-and-software and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

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.

Your homepage shows a street address 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: 8 customer or partner logos. 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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar and Meta Pixel (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 5 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.