Website review, no card needed
cybersecurity.my website review
Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 71 checks
This review found 40 issues worth fixing on cybersecurity.my, 18 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 115 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 109 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 110 ms |
| Oct 24, 2026 | 112 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.7 s
3.4 s
5.2 s
6.9 s
8.6 s
10.3 s
12.1 s
13.8 s
Speed
Use efficient cache lifetimes
4.7 s · 1.6 MB90 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).
Render-blocking requests
4.7 s55 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Reduce initial server response time
3.6 sReduce initial server response time. Google estimates savings of 3.6 s on a phone.
Document request latency
3.5 sThe HTML itself could arrive about 3.5 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused JavaScript
2.1 s · 323 KiBAbout 323 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Font display
2.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.1 s).
Main-thread work: 9.0 s
A phone's processor spends 9.0 s on main-thread work while loading, 7.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 3.7 s
3.7 sYour server takes 3.7 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
550 ms · 659 KiB8 images could be 659 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
200 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
200 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 162 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (ShareThis, Google Tag Manager and Cloudflare CDN and others), adding 255 KiB and 85 ms of main-thread time.
Minify JavaScript
10 ms · 22 KiB22 KiB could be saved by minifying JavaScript.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
First Contentful Paint: 30.9 s
30.9 sThe first text or image appears after 30.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 40.1 s
40.1 sYour largest element takes 40.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 34.0 s
34.0 sVisually, the page fills in at 34.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.3 s
40.3 sThe page becomes fully interactive after 40.3 s. Good is under 3.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 115 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 662 ms
662 msReal visitors wait 662 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 107 ms
107 msScripts block the page for only 107 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 7.2 MB in 126 requests
7.2 MBYour homepage downloads 7.2 MB in 126 requests on a phone: HTML 5.3 MB (2), images 847 KiB (21) and scripts 736 KiB (23). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
2.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.04 g of CO₂e: 244.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
<html> element does not have a valid value for its [lang] attribute.
<html> element does not have a valid value for its [lang] attribute. (1 element).
1 link without text
1 link has no text or label, so screen readers cannot say where it goes.
Page language is “English”
The page declares lang=“English”, which is not a usable language code, so screen readers and translation tools guess.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (22 characters)
Your title is only 22 characters: “CyberSecurity Malaysia”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (22 characters)
Your meta description is only 22 characters: “CyberSecurity Malaysia”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.cybersecurity.my/sitemap.xml, so Google discovers your pages only by following links.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
14 internal links, 3 external
The homepage links to 14 pages on cybersecurity.my and 3 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
4 linked pages are broken
Your homepage links to https://www.cybersecurity.my/main, https://www.cybersecurity.my/portal-main/article/organization, https://www.cybersecurity.my/portal-main/events and https://www.cybersecurity.my/portal-main/career, which answer with an error. Visitors hit a dead end and search engines drop them.
10 pages share a title
/, https://www.cybersecurity.my/portal-main/article/public, https://www.cybersecurity.my/portal-main/article/academia, https://www.cybersecurity.my/portal-main/advisories, https://www.cybersecurity.my/portal-main/procurement and https://www.cybersecurity.my/portal-main/services/csu and 4 others all use the title “CyberSecurity Malaysia”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://www.cybersecurity.my/portal-main/article/public, https://www.cybersecurity.my/portal-main/article/academia, https://www.cybersecurity.my/portal-main/advisories, https://www.cybersecurity.my/portal-main/procurement, https://www.cybersecurity.my/portal-main/services/csu and https://www.cybersecurity.my/portal-main/article/contact-us and 3 others use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.cybersecurity.my/portal-main/procurement has no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 9 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 console error
1 error was logged to the browser console during Google's test (“Failed to load resource: net::ERR_CONNECTION_FAILED”).
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 99 words
The homepage has only about 99 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “CONTACT US”.
Analytics in place
Analytics detected: Google Analytics.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at cybersecurity.my, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malay
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on cybersecurity.my, including 18 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.