12.4 sec in total
1.3 sec
10.8 sec
378 ms
Welcome to perhentian.com.my homepage info - get ready to check Perhentian best content for Malaysia right away, or after learning these important things about perhentian.com.my
Visit perhentian.com.myWe analyzed Perhentian.com.my page load time and found that the first response time was 1.3 sec and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
perhentian.com.my performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.1 s
96/100
25%
Value3.4 s
90/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.1 s
99/100
10%
1250 ms
657 ms
490 ms
480 ms
747 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Perhentian.com.my, 76% (65 requests) were made to Myoutdoor.com and 8% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Myoutdoor.com.
Page size can be reduced by 550.2 kB (7%)
7.4 MB
6.9 MB
In fact, the total size of Perhentian.com.my main page is 7.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. 50% of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 32 B
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 32 B or 25% of the original size.
Potential reduce by 521.7 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. Perhentian images are well optimized though.
Potential reduce by 27.5 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 27.5 kB or 72% of the original size.
Potential reduce by 1.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. Perhentian.com.my needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 71% of the original size.
Number of requests can be reduced by 27 (33%)
82
55
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perhentian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
perhentian.com.my
1250 ms
perhentian
657 ms
490 ms
perhentian.css
480 ms
swfobject_modified.js
747 ms
show_ads.js
8 ms
get_flash_player.gif
69 ms
top_title.gif
247 ms
link_01.gif
260 ms
link_02.gif
252 ms
link_03.gif
531 ms
link_04.gif
531 ms
link_05.gif
532 ms
link_06.gif
533 ms
link_07.gif
676 ms
img_home.jpg
1227 ms
title_welcome.gif
730 ms
perhentian_Map.jpg
1958 ms
line.gif
774 ms
videoGallery.gif
782 ms
diving-promo.png
1746 ms
left_deco1.jpg
1454 ms
SupportedLogo.jpg
1022 ms
ca-pub-2447665320117703.js
75 ms
zrt_lookup.html
66 ms
show_ads_impl.js
65 ms
index.html
1007 ms
ads
299 ms
osd.js
23 ms
ads
253 ms
m_js_controller.js
29 ms
abg.js
47 ms
favicon
99 ms
googlelogo_color_112x36dp.png
91 ms
nessie_icon_tiamat_white.png
37 ms
s
28 ms
x_button_blue2.png
15 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
galleryCSS.css
260 ms
gal_01.jpg
996 ms
gal_02.jpg
2628 ms
gal_03.jpg
3587 ms
gal_04.jpg
3052 ms
gal_05.jpg
2036 ms
gal_06.jpg
1641 ms
gal_07.jpg
1988 ms
gal_08.jpg
2133 ms
gal_09.jpg
2488 ms
gal_10.jpg
2839 ms
gal_11.jpg
2623 ms
gal_12.jpg
3235 ms
gal_13.jpg
2871 ms
gal_14.jpg
4532 ms
gal_15.jpg
3376 ms
gal_16.jpg
3119 ms
gal_17.jpg
4494 ms
gal_18.jpg
3368 ms
gal_19.jpg
3732 ms
gal_20.jpg
3858 ms
gal_21.jpg
4447 ms
gal_22.jpg
5632 ms
gal_23.jpg
4231 ms
gal_24.jpg
4107 ms
gal_25.jpg
4599 ms
gal_26.jpg
4730 ms
gal_27.jpg
4984 ms
gal_28.jpg
5938 ms
gal_29.jpg
6163 ms
gal_30.jpg
5091 ms
gal_31.jpg
4981 ms
gal_32.jpg
5318 ms
gal_33.jpg
5541 ms
gal_34.jpg
5192 ms
gal_35.jpg
5297 ms
gal_36.jpg
5425 ms
link_01_ov.gif
252 ms
link_02_ov.gif
259 ms
link_03_ov.gif
252 ms
link_04_ov.gif
248 ms
link_05_ov.gif
271 ms
link_06_ov.gif
275 ms
link_07_ov.gif
493 ms
ui
23 ms
activeview
13 ms
activeview
16 ms
perhentian.com.my accessibility score
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
Document doesn't have a <title> element
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
perhentian.com.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
perhentian.com.my SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perhentian.com.my can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Perhentian.com.my main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
perhentian.com.my
Open Graph description is not detected on the main page of Perhentian. 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: