4.6 sec in total
387 ms
3.5 sec
730 ms
Visit putera.com now to see the best up-to-date Pu TeRA content for Malaysia and also check out these interesting facts you probably never knew about putera.com
Sumber rujukan ilmu teknologi maklumat, komputer dan perniagaan internet dalam bahasa Melayu dengan ruangan forum, blog, artikel, tutorial, ebook percuma, serta perbincangan mengenai buat duit online,...
Visit putera.comWe analyzed Putera.com page load time and found that the first response time was 387 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
putera.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value2.7 s
84/100
25%
Value2.2 s
99/100
10%
Value170 ms
93/100
30%
Value0.021
100/100
15%
Value3.3 s
93/100
10%
387 ms
42 ms
88 ms
131 ms
109 ms
Our browser made a total of 212 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Putera.com, 10% (21 requests) were made to Um.simpli.fi and 7% (15 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Angel.exabytes.com.my.
Page size can be reduced by 461.3 kB (32%)
1.5 MB
989.4 kB
In fact, the total size of Putera.com 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 655.1 kB which makes up the majority of the site volume.
Potential reduce by 172.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. 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 172.1 kB or 76% of the original size.
Potential reduce by 9.0 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. Pu TeRA images are well optimized though.
Potential reduce by 280.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 280.1 kB or 50% of the original size.
Potential reduce by 9 B
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. Putera.com has all CSS files already compressed.
Number of requests can be reduced by 103 (59%)
175
72
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pu TeRA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.putera.com
387 ms
css
42 ms
3645911276-widget_css_bundle.css
88 ms
authorization.css
131 ms
jquery.min.js
109 ms
plusone.js
72 ms
plusone.js
117 ms
adsbygoogle.js
36 ms
addthis_widget.js
57 ms
3731899860-widgets.js
109 ms
cb=gapi.loaded_0
190 ms
analytics.js
190 ms
bg12.png
190 ms
cb=gapi.loaded_1
182 ms
google_top_exp.js
176 ms
all.js
273 ms
bg12L2.jpg
181 ms
rss.png
176 ms
facebook.png
180 ms
icon18_wrench_allbkg.png
172 ms
logoR12.png
161 ms
social-connect-rss.png
158 ms
widget-title-bg.png
159 ms
whereiswalle.jpg
169 ms
digitalmalaysia.jpg
163 ms
NuffnangX-Interface1.jpg
165 ms
menu-primary-bg.png
155 ms
social-connect-twitter.png
156 ms
readmore-bg.png
158 ms
87679102_XS.jpg
163 ms
120186-apple-iphone-5-picture-large.jpg
165 ms
NuffnangX+Image.jpeg
161 ms
twitter.png
154 ms
logoL12.png
159 ms
social-connect-facebook.png
156 ms
vugar.jpg
160 ms
game-control.jpg
159 ms
galaxynote2.jpg
163 ms
Microsoft-Logo-Change-Timeline.jpg
161 ms
widget-list.png
156 ms
0+(1).jpg
160 ms
ebuzzzz-200x200.gif
1710 ms
300x250-animated.gif
315 ms
readmore-bg.png
86 ms
twitter.png
84 ms
0.jpg
90 ms
search.png
87 ms
facebook.png
84 ms
digg.png
159 ms
more.png
85 ms
120186-apple-iphone-5-picture-large.jpg
89 ms
stumbleupon.png
85 ms
favorites.png
85 ms
galaxynote2.jpg
89 ms
vugar.jpg
158 ms
delicious.png
85 ms
fanpage-putera.jpg
87 ms
0+(1).jpg
86 ms
2A---Create-a-Page.jpg
156 ms
111026-samsung-galaxy-w-malaysia.jpg
156 ms
iphone-stove.jpg
157 ms
ca-pub-0903892411565656.js
262 ms
zrt_lookup.html
259 ms
show_ads_impl.js
200 ms
cb=gapi.loaded_2
163 ms
fastbutton
153 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
184 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
183 ms
blank.html
176 ms
collect
138 ms
navbar.g
155 ms
tabs-bg.png
118 ms
cb=gapi.loaded_0
101 ms
cb=gapi.loaded_1
102 ms
ads
354 ms
119 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
484 ms
osd.js
104 ms
icons_orange.png
394 ms
platform:gapi.iframes.style.common.js
250 ms
arrows-blue.png
470 ms
postmessageRelay
381 ms
xd_arbiter.php
409 ms
xd_arbiter.php
623 ms
ads
436 ms
small.js
226 ms
footer-bg.png
225 ms
ads
404 ms
ga.js
199 ms
load
989 ms
300lo.json
194 ms
sh.07f0d9bf220d07a763adad1e.html
118 ms
graph.facebook.com
367 ms
cb=gapi.loaded_0
118 ms
cb=gapi.loaded_1
106 ms
fastbutton
219 ms
ga-audiences
232 ms
m_js_controller.js
227 ms
abg.js
256 ms
151 ms
like_box.php
510 ms
xd_arbiter.php
241 ms
3193398744-postmessagerelay.js
277 ms
rpc:shindig_random.js
157 ms
collect
124 ms
postmessageRelay
109 ms
cb=gapi.loaded_1
151 ms
dpx.js
110 ms
ga-audiences
123 ms
favicon
201 ms
googlelogo_color_112x36dp.png
193 ms
imgad
86 ms
nessie_icon_tiamat_white.png
121 ms
tpid=1DE7044581A1E9562903883602A69AC9
105 ms
s
91 ms
x_button_blue2.png
89 ms
p
73 ms
229 ms
cb=gapi.loaded_0
51 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
dpx
55 ms
aol
19 ms
mapuser
5 ms
tc.js
5 ms
y_match
5 ms
p
69 ms
match_redirect
3 ms
29931
76 ms
hDvwL1_H7g-.css
169 ms
udqjbTyb5Ue.css
206 ms
FAHeNGXgPup.js
304 ms
FJmpeSpHpjS.js
375 ms
0wM5s1Khldu.js
347 ms
1bNoFZUdlYZ.js
343 ms
match_redirect
5 ms
tpid=CD29559E81A1E956ADBF5A5902E55206
5 ms
lr
5 ms
v2
52 ms
lr.gif
14 ms
dpx
8 ms
27519
86 ms
match_redirect
7 ms
sync
84 ms
xrefid.xgi
7 ms
pixel
51 ms
generic
21 ms
i.match
266 ms
match_redirect
39 ms
generic
33 ms
1407
294 ms
2964
88 ms
2981
237 ms
5386
220 ms
CD29559E81A1E956ADBF5A5902E55206
70 ms
3085
215 ms
2831
68 ms
4470
74 ms
4448
151 ms
match_redirect
6 ms
ProfilesEngineServlet
137 ms
398493_10151182585377446_320713057_n.jpg
261 ms
424889_10150598747807446_1569068254_n.jpg
335 ms
10915225_853578338026929_8679795094899251810_n.jpg
367 ms
12321597_1667701150161041_8267940815264540642_n.jpg
426 ms
11219100_737897786354798_4092862314880143410_n.jpg
406 ms
10393799_662796453852451_9128620043828246384_n.jpg
409 ms
378961_488977064481078_1540271322_n.jpg
435 ms
12190952_10204133511891546_558877486751548542_n.jpg
370 ms
11180950_1098684896814350_9106557493785423889_n.jpg
401 ms
12743600_10201212750596881_677571954672993132_n.jpg
408 ms
1928860_477420242460739_3066676026422399360_n.jpg
481 ms
11949340_10207877517476224_1510002090003829004_n.jpg
443 ms
36686_126386790735153_2715313_n.jpg
479 ms
1527007_654913987896312_576035612_n.jpg
469 ms
10984462_10203417583799600_6709539700946103083_n.jpg
458 ms
wL6VQj7Ab77.png
79 ms
s7jcwEQH7Sx.png
80 ms
i.match
94 ms
52154.gif
44 ms
ProfilesEngineServlet
48 ms
event
35 ms
4229
34 ms
tap.php
602 ms
exelate
3 ms
match_redirect
4 ms
18 ms
23 ms
activeview
14 ms
activeview
20 ms
30 ms
I6-MnjEovm5.js
38 ms
pQrUxxo5oQp.js
40 ms
spotx_match
5 ms
engine
91 ms
fb_match
4 ms
u.php
13 ms
an
3 ms
lj_match
3 ms
merge
4 ms
cw_match
3 ms
rb_match
4 ms
rtset
19 ms
tap.php
546 ms
ox_match
3 ms
pm_match
7 ms
pixel
23 ms
sd
5 ms
Pug
46 ms
g_match
3 ms
match_redirect
3 ms
pixel
36 ms
aa_px
3 ms
putera.com 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.
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
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.
putera.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
putera.com SEO score
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
MS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Putera.com can be misinterpreted by Google and other search engines. Our service has detected that Malay 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 Putera.com 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.
putera.com
Open Graph description is not detected on the main page of Pu TeRA. 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: