15.6 sec in total
2.6 sec
12.8 sec
205 ms
Click here to check amazing Wief content for Malaysia. Otherwise, check out these important facts you probably never knew about wief.org
The WIEF Foundation is the organising body of the Annual World Islamic Economic Forum (WIEF). The Foundation also undertakes various capacity building programmes under the WIEF initiatives of the Busi...
Visit wief.orgWe analyzed Wief.org page load time and found that the first response time was 2.6 sec and then it took 13 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wief.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value6.2 s
11/100
25%
Value15.2 s
1/100
10%
Value1,120 ms
23/100
30%
Value0.373
28/100
15%
Value18.9 s
3/100
10%
2633 ms
1771 ms
20 ms
511 ms
768 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 36% of them (58 requests) were addressed to the original Wief.org, 17% (27 requests) were made to Static.xx.fbcdn.net and 12% (19 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 1.2 MB (24%)
4.8 MB
3.6 MB
In fact, the total size of Wief.org main page is 4.8 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. 70% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 42.2 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 7.5 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 42.2 kB or 78% of the original size.
Potential reduce by 473.8 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. Obviously, Wief needs image optimization as it can save up to 473.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 397.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 397.1 kB or 72% of the original size.
Potential reduce by 243.6 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. Wief.org needs all CSS files to be minified and compressed as it can save up to 243.6 kB or 88% of the original size.
Number of requests can be reduced by 91 (58%)
156
65
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wief. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
wief.org
2633 ms
style.css
1771 ms
jsapi
20 ms
tabs.css
511 ms
jquery-ui-personalized-1.js
768 ms
general.js
766 ms
jquery.validate.js
1334 ms
smartpaginator.js
1109 ms
smartpaginator.css
774 ms
slashc.two-tier-menu.css
1021 ms
jquery.slashc.two-tier-menu.min.js
1059 ms
jquery.tipsy.js
1054 ms
CircularContentCarousel.css
1278 ms
jquery.jscrollpane.css
1316 ms
tooltips_main.css
1572 ms
tooltips_styles.css
2371 ms
quickAccess.css
1824 ms
easy-fancybox.css.php
1670 ms
jquery.js
2455 ms
jquery-migrate.min.js
1829 ms
include.js
1933 ms
jquery.fancybox-1.3.4.pack.js
2016 ms
buttons.js
11 ms
shailan-dropdown.css
2080 ms
hoverIntent.min.js
1581 ms
jquery.easing-1.3.pack.js
1721 ms
jquery.mousewheel-3.0.4.pack.js
1778 ms
jquery.metadata.js
1831 ms
jquery.min.js
6 ms
jquery.easing.1.3.js
1837 ms
jquery.contentcarousel.js
2001 ms
jquery.min.js
3 ms
bg.jpg
1852 ms
ga.js
11 ms
wp-emoji-release.min.js
588 ms
__utm.gif
12 ms
twitter-icon.png
375 ms
map.png
1593 ms
qrcode.png
603 ms
logo.png
351 ms
slider_54.jpg
1433 ms
slider_25.jpg
771 ms
slider_52.jpg
1486 ms
index.php
1020 ms
index.php
1247 ms
tunmusahitam.png
3166 ms
widgets.js
9 ms
fb-icon.png
1437 ms
all.js
161 ms
youtube-icon.png
1501 ms
flickr-icon.png
2045 ms
contact-icon.png
1690 ms
searach-icon-header.png
1841 ms
plus.png
1844 ms
cross.png
1841 ms
trnspant-bg.png
1939 ms
quote1.png
2094 ms
quote2.png
2099 ms
helvetica_neue_ce_35_thin-webfont.woff
2110 ms
youtube-footer.png
2232 ms
facebook-footer.png
2278 ms
twitter-footer.png
2329 ms
internship.png
2331 ms
wbn.png
2644 ms
9thwief.png
2581 ms
10thwief.png
2627 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
45 ms
getAllAppDefault.esi
106 ms
syndication
111 ms
345054548034994178
185 ms
128 ms
xd_arbiter.php
140 ms
xd_arbiter.php
286 ms
getSegment.php
145 ms
checkOAuth.esi
4 ms
proxy.jpg
41 ms
NuaFcE-0tjzXVzFy.jpg
212 ms
proxy.jpg
41 ms
proxy.jpg
40 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
8 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
26 ms
a4fa640a3c9d0e65fea3328e73907b6f_normal.png
260 ms
Mv4fgDci_normal.jpg
274 ms
Cdu0HiUW8AAb5Mm.jpg:small
393 ms
CdAIudTW0AAvfFj.jpg:small
311 ms
Ccnh0zbVIAA8wGv.jpg:small
307 ms
CbTeB3uUcAA92QX.jpg:small
404 ms
CUWBJe_WIAEewXe.jpg:small
568 ms
CUQ3tRSUEAESxzI.jpg:small
501 ms
CULuEhCVAAAqq9n.jpg:small
547 ms
CUGkOhtUYAAzzoJ.jpg:small
667 ms
CUBnLIlWoAE0mxE.jpg:small
524 ms
CdfAGzHUYAABS-q.jpg:small
470 ms
CdfAFNcUAAAM1jk.jpg:small
555 ms
CdJ9lHYUMAQIh3K.jpg:small
566 ms
CdJ9lT3UIAAyBl3.jpg:small
590 ms
Cc867_BVAAAWz3X.jpg:small
616 ms
Cc868DFUEAA8UXs.jpg:small
627 ms
Cc868QTUUAAeb6H.jpg:small
761 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
188 ms
t.dhj
16 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
212 ms
t.dhj
31 ms
cm
35 ms
x35248
156 ms
s-3271.xgi
9 ms
hbpix
179 ms
40 ms
41 ms
pixel
38 ms
xrefid.xgi
24 ms
pixel
27 ms
proxy.jpg
13 ms
2981
25 ms
jot.html
2 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
20 ms
buttons.ab966a004186897711de4a5ed256c924.css
19 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
5 ms
st.1188278743c14064d5e8ae56c8ada29c.js
9 ms
ping
43 ms
like_box.php
253 ms
kyEKgjk51ZE.css
175 ms
xgj7bXhJNEH.css
216 ms
Czh0gDTFcBt.css
257 ms
N-k91nHCZS2.css
342 ms
ZeuPykSxSED.css
329 ms
f3zkXvjB9aD.css
299 ms
XUOUvx124Lk.css
293 ms
q68gy-v_YMF.js
348 ms
FJmpeSpHpjS.js
372 ms
0wM5s1Khldu.js
359 ms
1bNoFZUdlYZ.js
360 ms
njO1TPvGzoR.js
367 ms
1QuX41zDRrx.js
368 ms
Oagsvfb4VWi.js
391 ms
LTv6ZK-5zxz.js
497 ms
1FCa-btixu2.js
413 ms
DVtj8v6ogQI.js
409 ms
IjqSyiwKeaX.js
411 ms
n6VgtouijQL.js
411 ms
10930165_10153323989093080_4262849156786460286_n.png
3814 ms
safe_image.php
3855 ms
safe_image.php
3930 ms
safe_image.php
4007 ms
safe_image.php
4010 ms
safe_image.php
4003 ms
399412_10150518147503080_1677301601_n.jpg
3881 ms
1934319_10153955287243080_962150629531549441_n.jpg
4021 ms
10325643_10153946099958080_5252828580962542782_n.jpg
3925 ms
12813974_10153946100203080_9149631037868967946_n.jpg
3966 ms
399412_10150518147503080_1677301601_n.jpg
3927 ms
wL6VQj7Ab77.png
3697 ms
s7jcwEQH7Sx.png
3699 ms
QDwYpIaRyfG.png
3697 ms
K00K-UgnsKu.png
3696 ms
bNvHN6v1NeH.png
3697 ms
b53Ajb4ihCP.gif
3698 ms
94 ms
I6-MnjEovm5.js
44 ms
pQrUxxo5oQp.js
82 ms
wief.org 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
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
wief.org 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wief.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Wief.org 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 Wief.org 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.
wief.org
Open Graph description is not detected on the main page of Wief. 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: