7.2 sec in total
864 ms
6 sec
313 ms
Visit ekeleh.com now to see the best up-to-date Ekeleh content for Malaysia and also check out these interesting facts you probably never knew about ekeleh.com
Siasah, Sosial Semasa, Malaysia
Visit ekeleh.comWe analyzed Ekeleh.com page load time and found that the first response time was 864 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ekeleh.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.8 s
55/100
25%
Value4.3 s
76/100
10%
Value100 ms
98/100
30%
Value0.029
100/100
15%
Value7.8 s
44/100
10%
864 ms
25 ms
49 ms
92 ms
134 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 14% of them (27 requests) were addressed to the original Ekeleh.com, 10% (19 requests) were made to Um.simpli.fi and 7% (13 requests) were made to Cdn.flashtalking.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Optimize.innity.com.
Page size can be reduced by 578.2 kB (51%)
1.1 MB
545.5 kB
In fact, the total size of Ekeleh.com main page is 1.1 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 738.5 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.1 kB or 78% of the original size.
Potential reduce by 12.1 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. Ekeleh images are well optimized though.
Potential reduce by 455.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 455.1 kB or 62% of the original size.
Potential reduce by 72.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. Ekeleh.com needs all CSS files to be minified and compressed as it can save up to 72.9 kB or 89% of the original size.
Number of requests can be reduced by 122 (76%)
160
38
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ekeleh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.ekeleh.com
864 ms
css
25 ms
styles.css
49 ms
cmam.css
92 ms
style.css
134 ms
red-crunch.css
100 ms
tw-recent-posts-widget.css
89 ms
jquery.js
173 ms
jquery-migrate.min.js
89 ms
small-menu.js
140 ms
vertical-m.css
134 ms
admanager.js
29 ms
adsbygoogle.js
9 ms
ck-karma.js
134 ms
jquery.form.min.js
140 ms
scripts.js
254 ms
cmam-adscript.js
255 ms
wp-embed.min.js
256 ms
wp-emoji-release.min.js
231 ms
rta.js
47 ms
521 ms
getpr.v2.php
161 ms
cropped-Ekeleh_1.png
49 ms
facebook.png
73 ms
googleplus.png
74 ms
rss-feed.png
70 ms
rss-comments.png
71 ms
Scholarship_Azalina-200x114.jpg
69 ms
Christina_Arokiasamy_Food_Network_Channel_1-200x114.jpg
150 ms
PAS_Ikatan-200x132.jpg
156 ms
Dr_Zakir_Naik-200x129.jpg
153 ms
Eddie-Putera_car_600-200x114.jpg
154 ms
Cari_MH370-200x154.jpg
156 ms
ca-pub-1577396468054788.js
135 ms
zrt_lookup.html
56 ms
show_ads_impl.js
56 ms
BkZwJXYnumPMepfEA344yQ.ttf
36 ms
ads
153 ms
osd.js
9 ms
106 ms
adj
102 ms
beacon
93 ms
banner.jpg
395 ms
30 ms
0
104 ms
surly.js
48 ms
119 ms
verify_selector.js
193 ms
blank.gif
193 ms
ba.html
25 ms
pixel
43 ms
lidar.js
33 ms
sbhK2lTE.js
83 ms
4.gif
41 ms
4311.js
28 ms
pixel
77 ms
pixel
76 ms
proxy_154517.js
70 ms
cTrvNaRi.html
20 ms
j-1734608-1324497.js
95 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
632 ms
CB154517_1.jpg
39 ms
analytics.js
11 ms
small.js
9 ms
js15.js
6 ms
optimize.innity.com
3567 ms
sd
23 ms
896034.php
36 ms
37 ms
index.html
31 ms
dvtp_src.js
109 ms
verifyr.js
44 ms
ads
286 ms
style.css
14 ms
html5API.js
223 ms
library.js
76 ms
main.js
95 ms
526 ms
cc_137.js
55 ms
dpx.js
71 ms
css
211 ms
beacon.js
180 ms
0
43 ms
bg.png
67 ms
adchoices.en.png
236 ms
tpid=1DE704451B7BEE561B03413502BEE8DC
36 ms
p
30 ms
dvtp_src_internal26.js
39 ms
dpx
5 ms
aol
102 ms
t2tv7.html
176 ms
visit.js
170 ms
sc.bci
149 ms
i_btn_redeem.gif
77 ms
i_btn_zip.gif
34 ms
adj
48 ms
beacon
26 ms
manifest.js
38 ms
78 ms
i_bg.jpg
45 ms
i_discount.png
27 ms
i_logo.png
57 ms
i_separator.png
73 ms
1TiHc9yag0wq3lDO9cw0vqCWcynf_cDxXwCLxiixG1c.ttf
71 ms
kpI87QY2ce-mk2ZnKb-r0g.ttf
83 ms
mapuser
17 ms
5-300-250.jpg
128 ms
pixel
49 ms
1324497.json
81 ms
pixel
64 ms
pixel
78 ms
tc.js
71 ms
avs581.js
51 ms
event.gif
94 ms
y_match
33 ms
event.jpg
55 ms
sd
18 ms
storelocator.js
17 ms
p
71 ms
match_redirect
12 ms
list.js
6 ms
984.js
37 ms
163.js
50 ms
982.js
69 ms
811.js
67 ms
13.js
68 ms
249.js
68 ms
773.js
94 ms
222.js
92 ms
397.js
93 ms
366.js
92 ms
box_19_top-right.png
29 ms
ci.png
54 ms
29931
51 ms
proxy_154216.js
36 ms
524 ms
CB154216_1.jpg
32 ms
match_redirect
19 ms
v2
59 ms
container_549927e79bd1fa1a040041a9.js
16 ms
458 ms
optimize.innity.com
1422 ms
tpid=C629559E1C7BEE56E023D8AE0276FA4F
10 ms
dc.js
8 ms
lr
8 ms
661 ms
dpx
9 ms
ca.png
165 ms
lr.gif
22 ms
xrefid.xgi
19 ms
match_redirect
14 ms
sync
9 ms
match_redirect
5 ms
C629559E1C7BEE56E023D8AE0276FA4F
47 ms
match_redirect
3 ms
ProfilesEngineServlet
54 ms
52154.gif
7 ms
ProfilesEngineServlet
61 ms
tap.php
6 ms
exelate
3 ms
15 ms
23 ms
18 ms
spotx_match
3 ms
fb_match
3 ms
u.php
84 ms
584 ms
457 ms
optimize.innity.com
1137 ms
an
4 ms
lj_match
4 ms
cw_match
5 ms
rtset
33 ms
rb_match
4 ms
tap.php
8 ms
merge
14 ms
ox_match
11 ms
pm_match
15 ms
sd
14 ms
Pug
47 ms
g_match
7 ms
pixel
14 ms
aa_px
4 ms
optimize.innity.com
564 ms
activeview
12 ms
activeview
21 ms
activeview
20 ms
activeview
21 ms
ekeleh.com 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
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
ekeleh.com 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
Page has valid source maps
ekeleh.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekeleh.com 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 Ekeleh.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.
ekeleh.com
Open Graph description is not detected on the main page of Ekeleh. 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: