6.5 sec in total
1.6 sec
4.7 sec
209 ms
Click here to check amazing PR1MA content for Malaysia. Otherwise, check out these important facts you probably never knew about pr1ma.my
Develop high quality homes and shape integrated community facilities for middle-income Malaysians.
Visit pr1ma.myWe analyzed Pr1ma.my page load time and found that the first response time was 1.6 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pr1ma.my performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value17.6 s
0/100
25%
Value16.8 s
0/100
10%
Value4,400 ms
1/100
30%
Value0.001
100/100
15%
Value20.2 s
2/100
10%
1588 ms
652 ms
444 ms
920 ms
469 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 90% of them (38 requests) were addressed to the original Pr1ma.my, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Pr1ma.my.
Page size can be reduced by 297.2 kB (21%)
1.4 MB
1.1 MB
In fact, the total size of Pr1ma.my main page is 1.4 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. 25% of websites need less resources to load. Images take 979.4 kB which makes up the majority of the site volume.
Potential reduce by 12.9 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 4.3 kB, which is 25% 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 12.9 kB or 76% of the original size.
Potential reduce by 5.5 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. PR1MA images are well optimized though.
Potential reduce by 201.9 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 201.9 kB or 66% of the original size.
Potential reduce by 76.9 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. Pr1ma.my needs all CSS files to be minified and compressed as it can save up to 76.9 kB or 85% of the original size.
Number of requests can be reduced by 15 (41%)
37
22
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PR1MA. 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 from 6 to 1 for CSS and as a result speed up the page load time.
pr1ma.my
1588 ms
style.css
652 ms
nav.css
444 ms
jquery-1.8.2.min.js
920 ms
iview.css
469 ms
homeslide2.css
465 ms
raphael-min.js
946 ms
jquery.easing.js
668 ms
anythingslider.css
694 ms
jquery.anythingslider.js
952 ms
jquery.fancybox.js
868 ms
jquery.fancybox.css
894 ms
pr1ma-bm.png
228 ms
m-logo.png
220 ms
login-bg.png
237 ms
search-icon.png
231 ms
search-submit.png
236 ms
icon_youtube.png
232 ms
facebook.png
438 ms
ins.png
453 ms
home-icon.png
459 ms
carouselbanner-bm_revised2.jpg
1857 ms
websitebanner_of3_bm.jpg
1676 ms
rto_bm.jpg
1652 ms
quiclink_bg.png
646 ms
quicklink-1.png
671 ms
quicklink-2.png
680 ms
quicklink-3.png
863 ms
quicklink-4.png
899 ms
CenturyGothic-Bold.woff
956 ms
CenturyGothic.woff
1122 ms
analytics.js
49 ms
template_inc_bm.php
1105 ms
fancybox_overlay.png
1132 ms
fancybox_sprite.png
1349 ms
fancybox_loading.gif
1398 ms
bullets_2.png
1360 ms
collect
13 ms
collect
64 ms
ga-audiences
38 ms
CenturyGothic-Bold.ttf
1310 ms
CenturyGothic.ttf
1204 ms
pr1ma.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 IDs are not unique
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
pr1ma.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pr1ma.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pr1ma.my can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pr1ma.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.
pr1ma.my
Open Graph description is not detected on the main page of PR1MA. 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: