7.1 sec in total
1.3 sec
5.4 sec
400 ms
Welcome to jellypop.kr homepage info - get ready to check Jellypop best content right away, or after learning these important things about jellypop.kr
가치와 정성을 담은 프리미엄 유아브랜드 젤리팝입니다.
Visit jellypop.krWe analyzed Jellypop.kr page load time and found that the first response time was 1.3 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
jellypop.kr performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value17.9 s
0/100
25%
Value11.8 s
4/100
10%
Value1,390 ms
16/100
30%
Value0.842
4/100
15%
Value15.1 s
7/100
10%
1328 ms
575 ms
577 ms
1351 ms
587 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 74% of them (58 requests) were addressed to the original Jellypop.kr, 13% (10 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Jellypop.kr.
Page size can be reduced by 256.3 kB (14%)
1.9 MB
1.6 MB
In fact, the total size of Jellypop.kr main page is 1.9 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 92.8 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 32.0 kB, which is 32% 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 92.8 kB or 93% of the original size.
Potential reduce by 62.9 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. Jellypop images are well optimized though.
Potential reduce by 90.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 90.3 kB or 78% of the original size.
Potential reduce by 10.4 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. Jellypop.kr needs all CSS files to be minified and compressed as it can save up to 10.4 kB or 88% of the original size.
Number of requests can be reduced by 22 (29%)
76
54
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jellypop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
jellypop.kr
1328 ms
common.css
575 ms
common.js
577 ms
common_ro.js
1351 ms
AuthSSLManager.js
587 ms
AuthSSLManager.plugin.js
401 ms
wcslog.js
6 ms
ec_front_popup_opener.php
262 ms
btn_prd_zoom.gif
593 ms
ec_top_logo_img
767 ms
login_01.gif
194 ms
join_us_01.gif
193 ms
bag_01.gif
195 ms
order_01.gif
196 ms
mypage_01.gif
395 ms
bbs_01.gif
395 ms
bbs_r04.gif
393 ms
top_cs.gif
393 ms
pillowbaby_01.jpg
634 ms
pillowkids_01.jpg
774 ms
seatkids_01.jpg
771 ms
atopillow_01.jpg
583 ms
heatpack_01.jpg
776 ms
news&event.jpg
776 ms
main_img01.jpg
2730 ms
main_cenba-1.jpg
1721 ms
more-1.JPG
1342 ms
dot.gif
963 ms
bestitems-2.gif
968 ms
jellypop_68.jpg
1162 ms
jellypop_70.jpg
1729 ms
jellypop_66.jpg
1739 ms
jellypop_67.jpg
1546 ms
jellypop_69.jpg
1758 ms
jellypop_71.jpg
1932 ms
jellypop_99.jpg
1911 ms
jellypop_100.jpg
2111 ms
jellypop_77.jpg
2127 ms
jellypop_78.jpg
1948 ms
jellypop_79.jpg
2103 ms
jellypop_80.jpg
2125 ms
jellypop_81.jpg
2329 ms
jellypop_82.jpg
2294 ms
jellypop_83.jpg
2276 ms
weblog.js
606 ms
likebox.php
207 ms
jellypop_76.jpg
2135 ms
jellypop_84.jpg
2300 ms
jellypop_85.jpg
2307 ms
jellypop_86.jpg
2458 ms
kyEKgjk51ZE.css
36 ms
xgj7bXhJNEH.css
38 ms
q68gy-v_YMF.js
44 ms
FJmpeSpHpjS.js
57 ms
0wM5s1Khldu.js
41 ms
1bNoFZUdlYZ.js
40 ms
1513289_223496024499968_1322754517_n.jpg
91 ms
1488123_216613988521505_1766994015_n.jpg
208 ms
1379841_10150004552801901_469209496895221757_n.jpg
22 ms
12400955_472121769633732_643103346488554236_n.jpg
33 ms
12715500_574721322676612_1760950839296229200_n.jpg
23 ms
wL6VQj7Ab77.png
13 ms
s7jcwEQH7Sx.png
7 ms
jellypop_87.jpg
2325 ms
jellypop_88.jpg
2380 ms
jellypop_89.jpg
2293 ms
jellypop_90.jpg
2491 ms
jellypop_91.jpg
2294 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
4 ms
jellypop_95.jpg
2273 ms
m
490 ms
jellypop_96.jpg
2143 ms
jellypop_97.jpg
2152 ms
jellypop_98.jpg
2194 ms
ad022.jpg
2294 ms
ec_bottom_logo_img.jpg
2298 ms
escrowba.gif
2135 ms
jellypop.kr 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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
jellypop.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
Missing source maps for large first-party JavaScript
jellypop.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jellypop.kr 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 Jellypop.kr 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.
jellypop.kr
Open Graph description is not detected on the main page of Jellypop. 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: