10.6 sec in total
68 ms
9 sec
1.6 sec
Click here to check amazing PitchIN content for Malaysia. Otherwise, check out these important facts you probably never knew about pitchin.my
Malaysia's Premier Equity Crowdfunding Platform
Visit pitchin.myWe analyzed Pitchin.my page load time and found that the first response time was 68 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pitchin.my performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value25.0 s
0/100
25%
Value15.9 s
0/100
10%
Value3,880 ms
1/100
30%
Value0.005
100/100
15%
Value22.3 s
1/100
10%
68 ms
2198 ms
1470 ms
52 ms
1345 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 96% of them (66 requests) were addressed to the original Pitchin.my, 3% (2 requests) were made to Storage.pitchin.my and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Pitchin.my.
Page size can be reduced by 668.4 kB (18%)
3.8 MB
3.1 MB
In fact, the total size of Pitchin.my main page is 3.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 191.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 191.5 kB or 78% of the original size.
Potential reduce by 476.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, PitchIN needs image optimization as it can save up to 476.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 17 B
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 11 (20%)
55
44
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PitchIN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
pitchin.my
68 ms
www.pitchin.my
2198 ms
font-awesome.min.css
1470 ms
styles.ca02d26f9ebb648c.css
52 ms
sprite.css.svg
1345 ms
landing-hero.png
1332 ms
1695120917_3390_0470094e-7cd9-4b0c-9ebe-eb024de29755.jpeg
1085 ms
1675485345_7625_Ascension-Logo.png
2921 ms
beyond4-logo.png
23 ms
mranti-logo.png
1369 ms
broku-logo.png
36 ms
check_icon_orange.svg
51 ms
padlock.svg
66 ms
investors-side-profiles.png
79 ms
arrow_down_orange.svg
98 ms
logo_square_chargehere.jpg
1644 ms
logo_square_commerce_asia.jpg
496 ms
logo_square_fundaztic.png
523 ms
logo_square_kakitangan.jpg
536 ms
logo_square_lapasar.png
557 ms
logo_square_moneymatch.png
571 ms
logo_square_newleaf_agro.jpg
603 ms
logo_square_nu_vending.jpg
626 ms
logo_square_oxwhite.png
642 ms
logo_square_policy_street.png
660 ms
logo_square_signature_market.jpeg
678 ms
logo_square_slurp.png
695 ms
logo_square_speedhome.jpg
714 ms
logo_square_superceed.jpg
735 ms
logo_square_the_lorry.png
757 ms
logo_square_union_chain.png
772 ms
commerce-asia-founder.jpeg
787 ms
kakitangan-founder.jpeg
802 ms
signature-market-founder.jpeg
572 ms
oxwhite-founder.jpeg
585 ms
logo_rectangle_commerce_dot_asia.png
602 ms
logo_rectangle_kakitangan.png
616 ms
logo_rectangle_signature_market.png
629 ms
logo_rectangle_oxwhite.png
643 ms
email-decode.min.js
646 ms
runtime.159d630833d93d80.js
1710 ms
polyfills.9e47aaca5961863b.js
2291 ms
scripts.f4562d1e9dd0f5ab.js
2146 ms
main.57196ca4298b90c0.js
6091 ms
pitchin_logo.svg
1447 ms
invest-ecf.png
659 ms
invest-ieo.png
673 ms
commerce-asia-banner-bg.png
3035 ms
quotation-marks.png
978 ms
kakitangan-banner-bg.png
995 ms
signature-market-banner-bg.png
1011 ms
oxwhite-banner-bg.png
1031 ms
academy-workshop.jpg
1047 ms
blob-random-green.svg
1068 ms
landing_register_footer_bg@2x.png
1089 ms
warning_icon_red@2x.png
1104 ms
pitchin_logo_white.svg
1117 ms
up_arrow_icon_red@2x.png
1134 ms
Inter-Regular.ttf
3429 ms
Inter-Medium.ttf
3344 ms
Inter-Light.ttf
3386 ms
Inter-Bold.ttf
3782 ms
Poppins-Bold.ttf
4749 ms
Poppins-Medium.ttf
5240 ms
Poppins-Regular.ttf
5260 ms
Poppins-Light.ttf
5228 ms
fontawesome-webfont.woff
4155 ms
gtm.js
72 ms
fontawesome-webfont.ttf
1919 ms
pitchin.my accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
pitchin.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pitchin.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pitchin.my can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pitchin.my main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
pitchin.my
Open Graph data is detected on the main page of PitchIN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: