7.4 sec in total
1.2 sec
4.2 sec
1.9 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 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pitchin.my performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value4.9 s
28/100
25%
Value4.3 s
76/100
10%
Value240 ms
85/100
30%
Value0.001
100/100
15%
Value4.2 s
85/100
10%
1240 ms
438 ms
437 ms
450 ms
448 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 62% of them (50 requests) were addressed to the original Pitchin.my, 17% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to I.imgur.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Pitchin.my.
Page size can be reduced by 892.0 kB (60%)
1.5 MB
597.8 kB
In fact, the total size of Pitchin.my main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 821.4 kB which makes up the majority of the site volume.
Potential reduce by 210.1 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. This page needs HTML code to be minified as it can gain 33.3 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 210.1 kB or 91% of the original size.
Potential reduce by 1.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. PitchIN images are well optimized though.
Potential reduce by 554.1 kB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 554.1 kB or 67% of the original size.
Potential reduce by 126.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pitchin.my needs all CSS files to be minified and compressed as it can save up to 126.0 kB or 84% of the original size.
Number of requests can be reduced by 42 (64%)
66
24
The browser has sent 66 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 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pitchin.my
1240 ms
bootstrap.min.css
438 ms
isotope.css
437 ms
application.css
450 ms
owl.carousel.min.css
448 ms
owl.theme.min.css
448 ms
owl.transitions.min.css
466 ms
jquery.min.js
1104 ms
jquery.ui.widget.min.js
660 ms
jquery.form.min.js
657 ms
jquery.transport.min.js
657 ms
jquery.bxslider.min.js
658 ms
jquery.isotope.min.js
661 ms
jquery.fileupload.min.js
870 ms
underscore.min.js
872 ms
ckeditor.min.js
1972 ms
backbone.min.js
876 ms
backbone.storage.min.js
882 ms
bootstrap.min.js
1095 ms
countdown.min.js
1095 ms
sugar.edge.min.js
1174 ms
blazy.min.js
1175 ms
jquery.jeditable.min.js
1307 ms
moment.min.js
17 ms
core.js
1307 ms
owl.carousel.min.js
1305 ms
application.min.js
1113 ms
webfont.js
40 ms
logo.png
167 ms
body.png
453 ms
logo_partner_madinc.png
237 ms
logo_partner_startupmy.png
235 ms
logo_partner_itrain.png
229 ms
logo_partner_salty.png
227 ms
logo_partner_bizspace.png
227 ms
logo_partner_venture_sense.png
440 ms
all.js
22 ms
piM2D76l.jpg
105 ms
wall.png
738 ms
banner-text.jpg
423 ms
slider.png
424 ms
slider_inner.png
424 ms
slider_red.png
633 ms
slider_inner_red.png
646 ms
fabric.png
735 ms
connect_facebook.png
736 ms
projects_bg.png
737 ms
wpv5Ftql.png
100 ms
xkp6SLFl.jpg
98 ms
css
59 ms
ajax-loader.gif
741 ms
tagging_location.png
742 ms
193 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
70 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
69 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
70 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
70 ms
xd_arbiter.php
44 ms
xd_arbiter.php
78 ms
LKf8nhXsWg5ybwEGXk8UBQ.woff
43 ms
0XxGQsSc1g4rdRdjJKZrNBsxEYwM7FgeyaSgU71cLG0.woff
44 ms
OXYTDOzBcXU8MTNBvBHeSQRW432DtwGNER78eOJ0i0s.woff
65 ms
Q-gJrFokeE7JydPpxASt2w9wu1CdFtjuMIsaFqyYbWg.woff
68 ms
UyYrYy3ltEffJV9QueSi4RdbPw3QSf9R-kE0EsQUn2A.woff
68 ms
Q_pTky3Sc3ubRibGToTAYiylde52zikAzebNtJS89aM.woff
73 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
67 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
66 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
67 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
72 ms
footer.png
272 ms
footer_badge_twitter.png
273 ms
footer_badge_fb.png
271 ms
footer_badge_blog.png
271 ms
bx-next.png
413 ms
bx-prev.png
415 ms
ga.js
77 ms
__utm.gif
23 ms
xd_arbiter.php
16 ms
like.php
116 ms
lP-FnQU1M58.js
29 ms
LVx-xkvaJ0b.png
20 ms
pitchin.my accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pitchin.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
pitchin.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 description is not detected on the main page of PitchIN. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: