10.4 sec in total
2.2 sec
8 sec
244 ms
Click here to check amazing Weddingparty content. Otherwise, check out these important facts you probably never knew about weddingparty.me
Visit weddingparty.meWe analyzed Weddingparty.me page load time and found that the first response time was 2.2 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
weddingparty.me performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.5 s
65/100
25%
Value3.0 s
94/100
10%
Value40 ms
100/100
30%
Value0.234
53/100
15%
Value3.3 s
93/100
10%
2164 ms
233 ms
12 ms
412 ms
239 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weddingparty.me, 20% (35 requests) were made to Blogimgs.naver.net and 20% (35 requests) were made to Blogthumb2.naver.net. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.5 MB (57%)
2.6 MB
1.1 MB
In fact, the total size of Weddingparty.me main page is 2.6 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 411 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 411 B or 46% of the original size.
Potential reduce by 402.4 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, Weddingparty needs image optimization as it can save up to 402.4 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 844.3 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 844.3 kB or 74% of the original size.
Potential reduce by 212.1 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. Weddingparty.me needs all CSS files to be minified and compressed as it can save up to 212.1 kB or 85% of the original size.
Number of requests can be reduced by 72 (40%)
178
106
The browser has sent 178 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weddingparty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
weddingparty.me
2164 ms
wedding0621
233 ms
Frameset-981964519.js
12 ms
PrologueList.nhn
412 ms
NBlogHidden.nhn
239 ms
Hidden-597428542.js
5 ms
MusicPlayer-449972894.js
14 ms
LayoutTopCommon-484882993.css
13 ms
player-846d457.css
21 ms
RemoveSubDomain-dea9950.js
21 ms
Jindo152-363950062.js
21 ms
LayoutTopCommon-730083628.js
26 ms
JindoComponent-318925938.js
29 ms
PrologueWebzine-71207160.css
35 ms
gnb_quirks_euckr.nhn
437 ms
allowSwfForChrome-7dd9772.js
52 ms
LayoutBottomCommon-902441421.js
51 ms
KakaoTalk_20151014_171313664.jpg
2639 ms
spc.gif
21 ms
513251807817f0db64975bbb0d1ed1f513bd_ugcvideo_270P_01_16x9_logo.jpg
1560 ms
%B1%EE%BB%E732_%2810%29.JPG
907 ms
btn_confirm2.gif
21 ms
%BF%FE%B5%F9%C6%C4%C6%BC.png
479 ms
1001_login.png
21 ms
blank.gif
30 ms
btn_thin_close.gif
19 ms
btn_close8.gif
19 ms
ico_file.gif
20 ms
btn_download2.gif
20 ms
btn_cancel3.gif
21 ms
btn_close3.gif
22 ms
btn_close5.gif
23 ms
btn_confirm.gif
22 ms
btn_cancel.gif
22 ms
btn_close_1.gif
22 ms
btn_viewexif.gif
23 ms
btn_originaldn.gif
23 ms
spc.gif
25 ms
tit_viewexif.gif
23 ms
ico_notice2.gif
23 ms
btn_close.gif
24 ms
btn_close3.gif
24 ms
btn_close.gif
25 ms
btn_ok.gif
25 ms
btn_close2.gif
25 ms
btn_confirm_pop2.gif
25 ms
btn_cancel_pop2.gif
25 ms
btn_close.gif
26 ms
ico_help.gif
19 ms
%BF%B9%B4%DC%C6%F7%C0%E5_%282%29.jpg
912 ms
%B0%B6%B7%AF%B8%AE%BF%FE%B5%F9_%285%29.JPG
910 ms
%BD%BA%B8%F4%BF%FE%B5%F9%C0%E5%BC%D2_%288%29.JPG
1018 ms
%BC%D2%B1%D4%B8%F0%BF%FE%B5%F9_%281%29.JPG
956 ms
%BE%DF%BF%DC%B0%E1%C8%A5%BD%C4%C0%E5%BC%D2_%281%29.JPG
966 ms
%BE%DF%BF%DC%B0%E1%C8%A5%BD%C4_%281%29.JPG
1435 ms
%C4%B3%BD%BD%BE%C6%BE%BE%BD%C3_%283%29.jpg
1448 ms
%BA%BD%B3%AF%C0%C7%C1%A4%BF%F8_%283%29.jpg
1424 ms
%BA%BD%B3%AF%C0%C7%C1%A4%BF%F8_%285%29.JPG
1498 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD_%284%29.jpg
1568 ms
%BD%BA%B8%F4%BF%FE%B5%F9_%284%29.JPG
1645 ms
%C6%AB%B8%B3%BA%CE%C4%C9_%286%29.jpg
1954 ms
%BC%BA%B4%E7%B0%E1%C8%A5%BD%C4_%289%29.JPG
1899 ms
%C1%D9%B8%AE%BF%A7%C4%AB%B6%F3%BA%CE%C4%C9_%284%29.JPG
1967 ms
%C4%B3%BD%BD%BE%C6%BE%BE%BD%C3_%282%29.JPG
2038 ms
%BD%BA%B8%F4%BF%FE%B5%F9_%289%29.jpg
2189 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD_%282%29.jpg
2309 ms
%B0%DC%BF%EF%BA%CE%C4%C9_%282%29.jpg
2428 ms
%BF%FE%B5%F9%C6%C4%C6%BC_%2825%29.JPG
2493 ms
%B0%DC%BF%EF%BA%CE%C4%C9_%286%29.JPG
2529 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD_%285%29.JPG
2598 ms
%BC%AD%BF%EF%BF%AC%B1%B8%BF%F8%B0%E1%C8%A5%BD%C4_%281%29.JPG
2720 ms
%C8%F7%BE%C6%BD%C5%BD%BA_%BA%CE%C4%C9_%282%29.JPG
2858 ms
%BE%C6%BD%BA%C6%BF%BA%A3_%281%29.JPG
2925 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD_%285%29.JPG
3006 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD_%281%29.jpg
3058 ms
20160312_221324.jpg
3109 ms
%B0%E1%C8%A5%BD%C4%BB%E7%C8%B8%C0%DA.JPG
3247 ms
%BD%BA%B3%C0%BB%E7%C1%F8.jpg
3625 ms
%BF%FE%B5%F9%B5%F0%B7%BA%C5%CD.JPG
3643 ms
%BC%BF%C7%C1%BF%FE%B5%F9%B5%E5%B7%B9%BD%BA.jpg
3644 ms
DSC00504.JPG
3627 ms
%BC%BF%C7%C1%BF%FE%B5%F9.JPG
3653 ms
%BC%BF%C7%C1%BF%FE%B5%F9.JPG
3774 ms
promo_npay.png
34 ms
0124_back1.gif
643 ms
ic_play.png
50 ms
WidgetView.nhn
274 ms
btn_blogsearch.gif
36 ms
shadow.png
36 ms
shadow02.png
36 ms
bg_not_available_word.gif
36 ms
0124_back2.gif
633 ms
0124_back3.gif
633 ms
0124_back4.gif
634 ms
0124_back6.gif
632 ms
0124_back7.gif
633 ms
0124_back8_1.gif
635 ms
0124_back9.gif
637 ms
0101_image.gif
639 ms
WidgetListAsync.nhn
318 ms
m
1046 ms
section_connect_widget2-413879d.css
405 ms
jindo.min-78c07e0.js
7 ms
agent.ie11-6694cec.js
8 ms
BuddyConnectWidget-242001126.js
7 ms
BuddyConnectBriefWidget-898830988.js
428 ms
%25BF%25FE%25B5%25F9%25C6%25C4%25C6%25BC.png
488 ms
3911478.gif
420 ms
btn_layer_close.gif
20 ms
0101_head_1.gif
264 ms
0101_body_1.gif
815 ms
0101_icon.gif
260 ms
0101_footer_1.gif
262 ms
ExternalWidgetRender.nhn
1431 ms
ExternalWidgetRender.nhn
1438 ms
ExternalWidgetRender.nhn
1444 ms
ExternalWidgetRender.nhn
1450 ms
ExternalWidgetRender.nhn
1452 ms
ExternalWidgetRender.nhn
1455 ms
ExternalWidgetRender.nhn
2018 ms
ExternalWidgetRender.nhn
2023 ms
ExternalWidgetRender.nhn
2028 ms
ExternalWidgetRender.nhn
2087 ms
ExternalWidgetRender.nhn
2083 ms
ExternalWidgetRender.nhn
2125 ms
ExternalWidgetRender.nhn
2636 ms
ExternalWidgetRender.nhn
2675 ms
ExternalWidgetRender.nhn
2671 ms
ExternalWidgetRender.nhn
2726 ms
ico_arr2.gif
18 ms
b.gif
17 ms
2016-01-18%2B12%253B29%253B20.PNG
546 ms
login_basic.gif
17 ms
KakaoTalk_20160313_172350053.jpg
481 ms
carolinesmode_com_20111113_081254.jpg
526 ms
profileimage.jpg
505 ms
profileimage.jpg
631 ms
DSC01047.png
827 ms
logo.jpg
530 ms
KakaoTalk_20140615_214153433.jpg
1056 ms
KakaoTalk_20150310_125405990+%281%29.jpg
1057 ms
%25B7%25CE%25B0%25ED%2B%25C8%25F2%25B9%25D9%25C5%25C1%2B%25C1%25A4%25BB%25E7%25B0%25A2.jpg
1046 ms
profileImage.jpg
1049 ms
2012-02-28%2B17.14.21.jpg
1133 ms
%C7%F6%C1%A4%B4%AB-6220-danibyeol7.jpg
1311 ms
pro.png
1540 ms
%B7%CE%B0%ED.jpg
1568 ms
inthegarden%2BNew.jpg
1527 ms
%B3%D7%C0%CC%B9%F6%BA%ED%B7%CE%B1%D7bkyung7%B4%EB%B9%AE-.jpg
1588 ms
22.gif
1654 ms
profileImage.jpg
1828 ms
%BD%BA%C4%B500~1.JPG
2172 ms
%C7%C1%B7%CE%C7%CA.jpg
1570 ms
%C1%A6%B8%F1+%BE%F8%C0%BD.png
2136 ms
IMG_3944.JPG
2110 ms
IMG_1440.JPG
2070 ms
20130517_084002%5B2%5D.jpg
1657 ms
Untitled-2+copy.JPG
1661 ms
%5B%C3%CA%B0%A3%B4%DC-%BC%D5%B1%D7%B8%B2-%B1%E2%BA%BB%C6%B2%5D.gif
1664 ms
half-life-2-874_jjy0501.jpg
1683 ms
%C7%C3%C7%CA%C0%DB%C0%BA%B0%C5.jpg
1687 ms
abs01_IMG_0352-5.jpg
1731 ms
line_skin20_v.gif
12 ms
ico_skin23_arr.gif
13 ms
ico_up.gif
12 ms
btn_skin20_pgn.gif
13 ms
btn_skin23_add_2.png
5 ms
btn_skin20_adm_2.png
5 ms
btn_skin20_dnld_2.png
4 ms
getLoginStatus.nhn
1220 ms
KakaoTalk_20150121_171720231.jpg
1201 ms
Untitled-6.png
1182 ms
Untitled-7.png
576 ms
promo_npay_1603.png
12 ms
clickcrD.js
12 ms
1001_menu.png
12 ms
%C5%F5%B8%ED.png
1389 ms
sp_gnb_v10.png
8 ms
%C5%F5%B8%ED.png
1370 ms
weddingparty.me 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
<frame> or <iframe> elements do not have a title
weddingparty.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
weddingparty.me 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weddingparty.me can be misinterpreted by Google and other search engines. Our service has detected that English 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 Weddingparty.me 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.
weddingparty.me
Open Graph description is not detected on the main page of Weddingparty. 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: