6.4 sec in total
1.3 sec
4.8 sec
310 ms
Visit jellzon.com now to see the best up-to-date Jellzon content and also check out these interesting facts you probably never knew about jellzon.com
Visit jellzon.comWe analyzed Jellzon.com page load time and found that the first response time was 1.3 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jellzon.com performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value13.9 s
0/100
25%
Value8.6 s
17/100
10%
Value730 ms
40/100
30%
Value0.092
91/100
15%
Value13.8 s
10/100
10%
1321 ms
598 ms
399 ms
1394 ms
640 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Jellzon.com, 7% (5 requests) were made to Img0001.echosting.cafe24.com and 1% (1 request) were made to Eclog2-021.cafe24.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Jellzon.com.
Page size can be reduced by 151.3 kB (39%)
387.8 kB
236.5 kB
In fact, the total size of Jellzon.com main page is 387.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 216.7 kB which makes up the majority of the site volume.
Potential reduce by 62.9 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 16.9 kB, which is 24% 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 62.9 kB or 91% of the original size.
Potential reduce by 5.3 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. Jellzon images are well optimized though.
Potential reduce by 73.4 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 73.4 kB or 81% of the original size.
Potential reduce by 9.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. Jellzon.com needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 88% of the original size.
Number of requests can be reduced by 21 (29%)
72
51
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jellzon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
jellzon.com
1321 ms
common.css
598 ms
common.js
399 ms
common_ro.js
1394 ms
AuthSSLManager.js
640 ms
AuthSSLManager.plugin.js
600 ms
ec_front_popup_opener.php
257 ms
bul_09.gif
627 ms
icon_22_01.gif
623 ms
icon_14_02.gif
625 ms
icon_19_01.gif
628 ms
body_back.gif
202 ms
logo.gif
201 ms
top_02.gif
202 ms
top_03.gif
203 ms
top_04.gif
204 ms
top_05.gif
398 ms
top_06.gif
400 ms
tmenu_01.gif
399 ms
tmenu_02.gif
401 ms
tmenu_03.gif
611 ms
tmenu_04.gif
446 ms
menu_top.gif
596 ms
category12_menu.gif
597 ms
category4_menu.gif
597 ms
category26_menu.gif
598 ms
category7_menu.gif
645 ms
menu_bottom.gif
795 ms
board_top.gif
796 ms
board_01.gif
793 ms
board_job.gif
796 ms
board_com.gif
812 ms
board_05.gif
843 ms
board_02.gif
992 ms
board_03.gif
992 ms
board_bottom.gif
993 ms
call.gif
995 ms
asas.jpg
1664 ms
mboard_title.gif
1041 ms
mboard_more.gif
1188 ms
m_bar01.gif
1189 ms
cerescnt_55.jpg
1191 ms
cerescnt_56.jpg
1192 ms
cerescnt_53.jpg
1238 ms
cerescnt_29.jpg
1582 ms
cerescnt_54.jpg
1371 ms
tle_bg.gif
573 ms
weblog.js
614 ms
cerescnt_59.jpg
1202 ms
cerescnt_37.jpg
1249 ms
cerescnt_57.jpg
1393 ms
cerescnt_58.jpg
1399 ms
cerescnt_35.jpg
1388 ms
cerescnt_30.jpg
1246 ms
cerescnt_60.jpg
1587 ms
cerescnt_52.jpg
1394 ms
cerescnt_36.jpg
1400 ms
cerescnt_38.jpg
1390 ms
cerescnt_13.jpg
1445 ms
cerescnt_20.jpg
1278 ms
cerescnt_21.jpg
1395 ms
cerescnt_33.jpg
1401 ms
cerescnt_24.jpg
1624 ms
cerescnt_27.jpg
1435 ms
cerescnt_39.jpg
1388 ms
cerescnt_48.jpg
1395 ms
cerescnt_42.jpg
1402 ms
cerescnt_41.jpg
1443 ms
cerescnt_49.jpg
1469 ms
cerescnt_40.jpg
1536 ms
bottom_menu.gif
1394 ms
bottom.gif
1403 ms
mbanner_back.gif
1436 ms
jellzon.com 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
jellzon.com 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
Missing source maps for large first-party JavaScript
jellzon.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jellzon.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Jellzon.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
jellzon.com
Open Graph description is not detected on the main page of Jellzon. 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: