14.9 sec in total
577 ms
13.8 sec
447 ms
Welcome to iwedding.com.my homepage info - get ready to check Iwedding best content for Malaysia right away, or after learning these important things about iwedding.com.my
提供全马(Malaysia)最全面、最时尚、最优惠的婚嫁服务信息和资料. 让新人省时、省力、省钱,轻松愉悦地筹备幸福婚礼。
Visit iwedding.com.myWe analyzed Iwedding.com.my page load time and found that the first response time was 577 ms and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
iwedding.com.my performance score
577 ms
642 ms
4059 ms
506 ms
529 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 64% of them (80 requests) were addressed to the original Iwedding.com.my, 16% (20 requests) were made to Static.xx.fbcdn.net and 7% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Iwedding.com.my.
Page size can be reduced by 455.6 kB (22%)
2.1 MB
1.6 MB
In fact, the total size of Iwedding.com.my main page is 2.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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 66.0 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 17.1 kB, which is 23% 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 66.0 kB or 87% of the original size.
Potential reduce by 9.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. Iwedding images are well optimized though.
Potential reduce by 240.0 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 240.0 kB or 67% of the original size.
Potential reduce by 139.8 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. Iwedding.com.my needs all CSS files to be minified and compressed as it can save up to 139.8 kB or 81% of the original size.
Number of requests can be reduced by 68 (58%)
118
50
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iwedding. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
iwedding.com.my
577 ms
cn
642 ms
4059 ms
facebook-like-responsive.css
506 ms
widget.css
529 ms
jquery-ui.theme.min.css
493 ms
minimalist.css
19 ms
gsc.css
497 ms
style.css
523 ms
css
50 ms
style.css
513 ms
layout.css
1272 ms
background.css
786 ms
mobile.css
992 ms
icons.css
1015 ms
lightbox.css
1009 ms
1024.css
1023 ms
fonts.php
1178 ms
dynamic-css.php
1654 ms
style.css
1507 ms
default.min.css
1500 ms
jquery.js
1760 ms
jquery-migrate.min.js
1666 ms
gsc.js
1749 ms
jsapi
44 ms
html5.js
42 ms
jquery.flickr.js
2006 ms
jquery.fitvids.js
1994 ms
jquery.ui.js
2197 ms
functions.js
2150 ms
core.min.js
2275 ms
widget.min.js
2276 ms
mouse.min.js
2495 ms
resizable.min.js
2275 ms
draggable.min.js
2651 ms
button.min.js
2717 ms
position.min.js
2732 ms
dialog.min.js
2873 ms
jquery.adrotate.dyngroup.js
2756 ms
jquery.adrotate.clicktracker.js
2995 ms
jquery.sonar.min.js
3135 ms
lazy-load.js
3188 ms
tabs.min.js
3221 ms
minimalist.css
45 ms
jquery.c00kie.js
2772 ms
jquery.easing.js
2878 ms
jquery.menu.js
3016 ms
jquery.bxslider.js
3178 ms
jquery.lightbox.js
3239 ms
jquery.customselect.js
3216 ms
jquery.custom.js
2977 ms
yaaburnee.js
2867 ms
scripts.php
2837 ms
wpsite_clickable.js
3171 ms
analytics.js
67 ms
branding.css
55 ms
logo-retina2.png
2490 ms
unique-new-ads.jpg
2295 ms
loading.gif
2054 ms
04_11_yuhsin_seah_tinydotphotography-041112214124-550x400_c.jpg
2832 ms
1444182758779563-550x400_c.jpg
2376 ms
uhhuadha-550x400_c.jpg
2702 ms
weds-logo-550x400_c.jpg
2550 ms
04_11_yuhsin_seah_tinydotphotography-041112214124-400x400_c.jpg
3287 ms
1444182758779563-400x400_c.jpg
3102 ms
uhhuadha-400x400_c.jpg
3215 ms
imges-400x400_c.jpg
3559 ms
fengsui-400x400_c.jpg
3190 ms
a01624cc-ee99-4a0f-8739-636244a86a21-400x400_c.jpg
3580 ms
branding.css
43 ms
6413720111017162114-1-400x400_c.jpg
3814 ms
1797548_227743044076600_82855137_n-400x400_c.jpg
3871 ms
y7lebkjgREBJK96VQi37ZobN6UDyHWBl620a-IRfuBk.woff
47 ms
fontawesome-webfont.woff
4133 ms
collect
49 ms
collect
60 ms
all.js
163 ms
weds-logo-400x400_c.jpg
3520 ms
72 ms
xd_arbiter.php
145 ms
xd_arbiter.php
269 ms
song-pic-400x400_c.jpg
3894 ms
unnamed-400x400_c.jpg
3882 ms
CgoB91FGsN-AfHGSAADeFGNSteg68-400x400_c.jpeg
4105 ms
1d752739-5433-bced-0a76-5c27915b9950-400x400_c.jpg
4075 ms
N+C-ll-161-400x400_c.jpg
4275 ms
3nov08dd-400x400_c.jpg
4160 ms
gownschart-160x160_c.jpg
3905 ms
singapore-wedding-photography-gardenasia-bittersweet-1006-160x160_c.jpg
3897 ms
bittersweet-photography-singapore-wedding-actual-day-st-georges-1005-160x160_c.jpg
3867 ms
4d157d662de912f3c7b23dd925b3b9e4-160x160_c.jpg
4149 ms
333-160x160_c.jpg
4172 ms
300banner-ads2015-2.jpg
4550 ms
2015-bg-ads.jpg
4869 ms
admin-ajax.php
3638 ms
like_box.php
211 ms
ebiMDO3r-8l.css
183 ms
jGc-59L_9lo.css
223 ms
k5BhlqovqZn.css
263 ms
1kPfZUdGrka.js
379 ms
Yuj_Y8xNH2C.js
402 ms
Mpe38fuBVZ2.js
305 ms
n8qIhCw3vMx.js
303 ms
d20DxWMAn1e.js
305 ms
qcMicXoOToy.js
464 ms
57RpJa05x58.js
417 ms
7B-2ZS3Qt8r.js
416 ms
pf3FNnit_ev.js
416 ms
BmFj6FmaQGO.js
418 ms
hGrOQrzI1QD.js
417 ms
qf1RiuO5N-I.js
670 ms
10417473_356436437873926_6091914984652364836_n.png
298 ms
11329972_385843318266571_264882295662769987_n.png
341 ms
1918035_10207003139414519_5696379570244756376_n.jpg
382 ms
12321566_10153427037123318_7971549460101655566_n.jpg
455 ms
12794517_10154036187749529_2141480048520059722_n.jpg
466 ms
10414601_1786206774940348_2636733358939788422_n.jpg
430 ms
1623524_10153360868839352_8940255426810977569_n.jpg
430 ms
10995620_680324805402119_4230831497047190196_n.jpg
428 ms
12376809_196284187380278_609736204236539463_n.jpg
470 ms
wL6VQj7Ab77.png
106 ms
s7jcwEQH7Sx.png
105 ms
gxbPuQdXIZP.png
44 ms
VXcANLwwL5J.js
45 ms
AmlxWlqMvlv.js
82 ms
iwedding.com.my SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iwedding.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), while the claimed language is English. Our system also found out that Iwedding.com.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.
iwedding.com.my
Open Graph description is not detected on the main page of Iwedding. 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: