8.5 sec in total
1.4 sec
5.5 sec
1.7 sec
Visit zizel.net now to see the best up-to-date Zizel content and also check out these interesting facts you probably never knew about zizel.net
Visit zizel.netWe analyzed Zizel.net page load time and found that the first response time was 1.4 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zizel.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.6 s
17/100
25%
Value8.1 s
20/100
10%
Value1,480 ms
14/100
30%
Value0.153
75/100
15%
Value15.4 s
7/100
10%
1404 ms
224 ms
14 ms
300 ms
219 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zizel.net, 35% (44 requests) were made to Blogimgs.naver.net and 13% (16 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Postfiles15.naver.net.
Page size can be reduced by 1.2 MB (35%)
3.4 MB
2.2 MB
In fact, the total size of Zizel.net main page is 3.4 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.9 MB which makes up the majority of the site volume.
Potential reduce by 376 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 376 B or 44% of the original size.
Potential reduce by 22.5 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. Zizel images are well optimized though.
Potential reduce by 930.6 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 930.6 kB or 74% of the original size.
Potential reduce by 261.2 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. Zizel.net needs all CSS files to be minified and compressed as it can save up to 261.2 kB or 84% of the original size.
Number of requests can be reduced by 75 (60%)
124
49
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zizel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
zizel.net
1404 ms
biozizel
224 ms
Frameset-981964519.js
14 ms
PostList.nhn
300 ms
NBlogHidden.nhn
219 ms
Hidden-597428542.js
4 ms
MusicPlayer-449972894.js
18 ms
LayoutTopCommon-484882993.css
13 ms
player-846d457.css
19 ms
RemoveSubDomain-dea9950.js
20 ms
Jindo152-363950062.js
24 ms
LayoutTopCommon-730083628.js
22 ms
JindoComponent-318925938.js
23 ms
PostList-1027637939.css
22 ms
gnb_quirks_euckr.nhn
103 ms
likeit_blog.css
99 ms
likeit.css
99 ms
SeViewerBlog-165931490.css
21 ms
PostTopCommon-327917359.js
19 ms
splugin.js
97 ms
PostBottomCommon-1023812380.js
92 ms
PostBottomCommon_utf8-169531666.js
92 ms
likeIt.list.js
94 ms
allowSwfForChrome-7dd9772.js
90 ms
LayoutBottomCommon-902441421.js
92 ms
spc.gif
153 ms
PostList.nhn
276 ms
blank.gif
155 ms
NaverBlog_20160317_172313_01.jpg
1915 ms
NaverBlog_20160317_172316_02.jpg
1205 ms
NaverBlog_20160317_172521_04.jpg
1442 ms
NaverBlog_20160317_172527_06.jpg
1443 ms
NaverBlog_20160317_172536_08.jpg
1189 ms
NaverBlog_20160317_172540_10.jpg
1127 ms
NaverBlog_20160317_172541_12.jpg
1322 ms
NaverBlog_20160317_172638_16.jpg
1383 ms
NaverBlog_20160317_173109_24.jpg
1291 ms
20090116%C0%CF%BA%BB%BE%EE.jpg
2041 ms
btn_confirm2.gif
153 ms
01-6539-biozizel.jpg
646 ms
0027_login.png
474 ms
btn_qk_set.gif
144 ms
btn_what2.gif
144 ms
btn_clse_ly2.gif
145 ms
spc.gif
145 ms
icon_mobile_F.gif
147 ms
btn_urlcopy.gif
145 ms
blank.gif
145 ms
ico_new.gif
146 ms
btn_thin_close.gif
146 ms
btn_close8.gif
142 ms
ico_file.gif
143 ms
btn_download2.gif
143 ms
btn_cancel3.gif
141 ms
btn_close3.gif
141 ms
btn_close5.gif
142 ms
btn_confirm.gif
143 ms
btn_cancel.gif
142 ms
btn_close_1.gif
142 ms
btn_viewexif.gif
141 ms
btn_originaldn.gif
141 ms
tit_viewexif.gif
142 ms
ico_notice2.gif
141 ms
btn_close.gif
143 ms
btn_close3.gif
142 ms
btn_close.gif
143 ms
btn_ok.gif
185 ms
btn_close2.gif
186 ms
btn_confirm_pop2.gif
186 ms
btn_cancel_pop2.gif
187 ms
btn_close.gif
186 ms
NaverBlog_20160317_172759_18.jpg
1449 ms
NaverBlog_20160317_173101_20.jpg
1238 ms
ico_help.gif
134 ms
NaverBlog_20160317_172542_14.jpg
1971 ms
NaverBlog_20160317_173105_22.jpg
1638 ms
zizelnet.jpg
513 ms
0141_966.gif
148 ms
WidgetListAsync.nhn
306 ms
bg_qk_ly2.gif
65 ms
sp_post_btn.png
65 ms
spr_blogapp_2014_v1.png
65 ms
ico_post_sccl-by-nc-nd.png
67 ms
promo_npay.png
67 ms
ico_tag.gif
66 ms
sp_arr1.gif
67 ms
bg_likeit2.gif
67 ms
sp_likeit_pc3.png
67 ms
lg_photoviewer.gif
68 ms
btn_left.gif
70 ms
btn_right.gif
71 ms
btn_original2.png
72 ms
btn_close.gif
71 ms
0102_image.gif
72 ms
0114_back.gif
72 ms
btn_blogsearch.gif
66 ms
shadow.png
65 ms
shadow02.png
65 ms
bg_not_available_word.gif
66 ms
968665.gif
784 ms
0159_icon.gif
53 ms
1.jpg
548 ms
btn_rst_clse.gif
18 ms
ico_n_photo.gif
18 ms
01-6539-biozizel.jpg
600 ms
0155_arw.gif
19 ms
ExternalWidgetRender.nhn
846 ms
ExternalWidgetRender.nhn
946 ms
wiget.gif
542 ms
getLoginStatus.nhn
652 ms
Untitled-2.jpg
1181 ms
promo_npay_1603.png
6 ms
clickcrD.js
6 ms
0027_menu.png
468 ms
sp_gnb_v10.png
4 ms
spi_standard_20160222.css
32 ms
BlogTagListInfo.nhn
257 ms
index.html
220 ms
icon_set.gif
29 ms
m
646 ms
likeIt.list.main.js
19 ms
sp_spi_pc.png
10 ms
likeit.css
3 ms
likeit_blog.css
3 ms
likeItServiceContentList.jsonp
205 ms
zizel.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
zizel.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
zizel.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zizel.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 Zizel.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.
zizel.net
Open Graph description is not detected on the main page of Zizel. 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: