6.5 sec in total
1.2 sec
5.1 sec
249 ms
Welcome to weezzle.co.kr homepage info - get ready to check Weezzle best content for South Korea right away, or after learning these important things about weezzle.co.kr
방송,연예,유머,이슈,IT,갤러리,맛집,생활,리뷰 정보 제공 등을 제공합니다.
Visit weezzle.co.krWe analyzed Weezzle.co.kr page load time and found that the first response time was 1.2 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
weezzle.co.kr performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value5.5 s
19/100
25%
Value8.1 s
21/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value7.9 s
43/100
10%
1150 ms
798 ms
412 ms
75 ms
447 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Weezzle.co.kr, 51% (34 requests) were made to S1.daumcdn.net and 9% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Cfile24.uf.tistory.com.
Page size can be reduced by 744.4 kB (66%)
1.1 MB
382.0 kB
In fact, the total size of Weezzle.co.kr 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. 60% of websites need less resources to load. CSS take 580.1 kB which makes up the majority of the site volume.
Potential reduce by 39.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 39.1 kB or 78% of the original size.
Potential reduce by 1.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. Weezzle images are well optimized though.
Potential reduce by 177.7 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 177.7 kB or 52% of the original size.
Potential reduce by 525.7 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.co.kr needs all CSS files to be minified and compressed as it can save up to 525.7 kB or 91% of the original size.
Number of requests can be reduced by 44 (71%)
62
18
The browser has sent 62 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 12 to 1 for CSS and as a result speed up the page load time.
weezzle.co.kr
1150 ms
style.css
798 ms
font.css
412 ms
jquery.min.js
75 ms
shareEntryWithSNS.css
447 ms
shareEntryWithSNS.js
473 ms
lightbox.min.css
519 ms
style.css
519 ms
profile.js
814 ms
jigu-latest.min.js
1327 ms
T.js
708 ms
EAF2.js
1029 ms
common.js
1333 ms
gallery.js
940 ms
flash.js
982 ms
PHON.js
1012 ms
sha256.js
1175 ms
md5.min.js
1173 ms
swfobject.js
1214 ms
dialog.css
1279 ms
reset.css
1406 ms
tabloid.css
1562 ms
items.css
1617 ms
util.css
1534 ms
tistory-grid-min.css
1836 ms
items.js
1537 ms
menubar.css
1639 ms
429 ms
adsbygoogle.js
10 ms
script.js
1589 ms
functions.js
1554 ms
searchDragSelection.js
1547 ms
lightbox.min.js
1612 ms
td.min.js
862 ms
roosevelt_dk_bt.js
7 ms
check.php
267 ms
2114BC3956E92DB03420D5
1139 ms
new_ico_5.gif
474 ms
227C8A4F56EE5C6B349CA2
1573 ms
264FAC4056EDD1160FBD5D
2285 ms
243E404F56EE8ED613D2C8
2326 ms
1403F8164B8735F440D0AB
1229 ms
260CDF4756EB7E5805FD08
2125 ms
2172E63C56EE0C0F133960
2107 ms
close.png
275 ms
loading.gif
406 ms
prev.png
274 ms
next.png
234 ms
ico_skin.gif
267 ms
notokr-bold.woff
740 ms
notokr-regular.woff
408 ms
notokr-demilight.woff
527 ms
ca-pub-4548277674241774.js
152 ms
zrt_lookup.html
146 ms
show_ads_impl.js
74 ms
ads
240 ms
footsteps
1191 ms
expansion_embed.js
12 ms
osd.js
41 ms
m_js_controller.js
74 ms
abg.js
91 ms
favicon
172 ms
googlelogo_color_112x36dp.png
171 ms
nessie_icon_thin_arrow_big_white.png
48 ms
s
25 ms
x_button_blue2.svg
128 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
weezzle.co.kr 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
weezzle.co.kr 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
weezzle.co.kr 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weezzle.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Weezzle.co.kr 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.co.kr
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: