14.4 sec in total
1.4 sec
12.8 sec
173 ms
Visit weezzle.net now to see the best up-to-date Weezzle content for South Korea and also check out these interesting facts you probably never knew about weezzle.net
각종생활 정보와 모든 분야의 상식을 모아모아 만든 블로그
Visit weezzle.netWe analyzed Weezzle.net page load time and found that the first response time was 1.4 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. This domain responded with an error, which can significantly jeopardize Weezzle.net rating and web reputation
weezzle.net performance score
1379 ms
1089 ms
820 ms
1227 ms
870 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Weezzle.net, 55% (61 requests) were made to S1.daumcdn.net and 10% (11 requests) were made to Rsense-ad.realclick.co.kr. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Cfile30.uf.tistory.com.
Page size can be reduced by 722.0 kB (32%)
2.2 MB
1.5 MB
In fact, the total size of Weezzle.net main page is 2.2 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 64.7 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 64.7 kB or 79% of the original size.
Potential reduce by 152.6 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, Weezzle needs image optimization as it can save up to 152.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 447.9 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 447.9 kB or 61% of the original size.
Potential reduce by 56.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. Weezzle.net needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 82% of the original size.
Number of requests can be reduced by 62 (61%)
102
40
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weezzle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
weezzle.net
1379 ms
style.css
1089 ms
shareEntryWithSNS.css
820 ms
shareEntryWithSNS.js
1227 ms
lightbox.min.css
870 ms
style.css
1273 ms
profile.js
1601 ms
jigu-latest.min.js
1632 ms
T.js
1170 ms
EAF2.js
1354 ms
common.js
2059 ms
gallery.js
1520 ms
flash.js
1664 ms
PHON.js
1617 ms
sha256.js
1789 ms
md5.min.js
1925 ms
swfobject.js
1884 ms
dialog.css
1901 ms
menubar.css
1991 ms
645 ms
rsense_ad.js
751 ms
rsense_ad.js
1447 ms
adsbygoogle.js
5 ms
show_ads.js
7 ms
rsense_ad.js
518 ms
functions.js
1617 ms
searchDragSelection.js
1721 ms
lightbox.min.js
1722 ms
td.min.js
1565 ms
roosevelt_dk_bt.js
56 ms
check.php
353 ms
025FF13B5111B9EC077DBF
3981 ms
035A663B5111B9F110B7F7
3482 ms
1752263B5111B9F71D7DAF
4536 ms
btn_track_white.gif
760 ms
135E69194CB63AEF2EE8CE
1115 ms
count.php
549 ms
close.png
347 ms
loading.gif
344 ms
prev.png
332 ms
next.png
344 ms
bg_header.gif
424 ms
menu_bg.gif
425 ms
menu_round.gif
555 ms
tab_bar.gif
609 ms
tab.gif
1016 ms
bg.jpg
1354 ms
layout_title.png
654 ms
layout_bg.gif
670 ms
wait.gif
1565 ms
criteo_rta.html
480 ms
ca-pub-5430869538526353.js
144 ms
zrt_lookup.html
172 ms
show_ads_impl.js
68 ms
409 ms
socialShare_big2.png
641 ms
ads
57 ms
osd.js
48 ms
ads
40 ms
ads
50 ms
txt_tag.gif
612 ms
line_dot.gif
699 ms
ads
86 ms
control.gif
697 ms
iconSecret.gif
708 ms
head.gif
865 ms
btn_write.gif
972 ms
ads
33 ms
layout_btm.png
974 ms
btn_paging.gif
934 ms
tistory.gif
1031 ms
rss.gif
1083 ms
bloger_round.gif
1222 ms
bloger_bg.gif
1225 ms
iconBy.gif
1255 ms
bg_search.gif
1368 ms
btn_search.gif
1372 ms
category_round.gif
1609 ms
category_bg.gif
1542 ms
iconDepth1.gif
1509 ms
iconDepth2.gif
1540 ms
iconDepth3.gif
1709 ms
sidebar_top.png
1716 ms
sidebar_bg.gif
1797 ms
stit.gif
1822 ms
bul.gif
1905 ms
sidebar_btm.png
1892 ms
ads
22 ms
jquery.min.js
20 ms
view_ad.html
1661 ms
view_ad_adcrm.html
481 ms
footsteps
2143 ms
rta.js
18 ms
rsense_ad.js
503 ms
jquery-1.11.0.min.js
2532 ms
uoclike.min.js
2199 ms
view_ad.html
574 ms
jquery-1.6.2.min.js
1625 ms
rclink.gif
656 ms
view_ad_adcrm.html
473 ms
pkg37052_150909142217_9.gif
2264 ms
adBanner
1678 ms
jquery-1.9.1.min.js
35 ms
uoclike.min-20150408-2.css
28 ms
649342_3587.json
726 ms
print.css
348 ms
view_ad_n2s.html
481 ms
_n2s_blogs_adinfo.php
4356 ms
img_empathy_141113.png
29 ms
view_ad.html
546 ms
pkg46858_150907100119_17.jpg
1295 ms
weezzle.net accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
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
weezzle.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
weezzle.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weezzle.net 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Weezzle.net 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.
weezzle.net
Open Graph data is detected on the main page of Weezzle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: