7.3 sec in total
784 ms
5.9 sec
663 ms
Welcome to ineltree.co.kr homepage info - get ready to check Ineltree best content right away, or after learning these important things about ineltree.co.kr
Make you more chic, IPKN 프로페셔널 여성을 위한 코스메틱 입큰 뉴욕
Visit ineltree.co.krWe analyzed Ineltree.co.kr page load time and found that the first response time was 784 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ineltree.co.kr performance score
name
value
score
weighting
Value14.4 s
0/100
10%
Value64.7 s
0/100
25%
Value56.5 s
0/100
10%
Value9,040 ms
0/100
30%
Value0.202
61/100
15%
Value66.0 s
0/100
10%
784 ms
1511 ms
1425 ms
1616 ms
930 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 24% of them (16 requests) were addressed to the original Ineltree.co.kr, 69% (47 requests) were made to M.ipkn.co.kr and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ineltree.co.kr.
Page size can be reduced by 301.2 kB (18%)
1.7 MB
1.4 MB
In fact, the total size of Ineltree.co.kr main page is 1.7 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. 15% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 19.4 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 3.3 kB, which is 14% 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 19.4 kB or 81% of the original size.
Potential reduce by 64.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. Ineltree images are well optimized though.
Potential reduce by 165.2 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 165.2 kB or 69% of the original size.
Potential reduce by 52.1 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. Ineltree.co.kr needs all CSS files to be minified and compressed as it can save up to 52.1 kB or 86% of the original size.
Number of requests can be reduced by 7 (11%)
66
59
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ineltree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
ineltree.co.kr
784 ms
m.ipkn.co.kr
1511 ms
ui.css
1425 ms
jquery-1.7.2.min.js
1616 ms
swipe.js
930 ms
ui.js
709 ms
w2fn.js
1046 ms
link.js
1200 ms
common.js
1177 ms
wcslog.js
11 ms
analytics.js
39 ms
INEL150407001_main_280.jpg
1542 ms
INEL140828002_main_280.jpg
1570 ms
INEL140407005_main_280.jpg
1689 ms
INEL140307009_main_280.jpg
1765 ms
INEL140226001_main_280.jpg
1774 ms
INEL100521004_main_280.jpg
1882 ms
INEL140919005_main_280.jpg
1758 ms
INEL110209001_main_280.jpg
2022 ms
INEL150421019_main_280.jpg
2157 ms
INEL100604042_main_280.jpg
2179 ms
INEL100604046_main_280.jpg
2266 ms
INEL120316001_main_280.jpg
2027 ms
INEL100604008_main_280.jpg
2410 ms
INEL160314001_main_280.jpg
2565 ms
INEL160303001_main_280.jpg
2625 ms
header_top_SearchArrow.gif
359 ms
h1_logo.gif
303 ms
header_top_Search.gif
250 ms
header_top_Cart.gif
236 ms
header_top_myIPKN.gif
279 ms
gnbMenu1.gif
357 ms
gnbMenu2.gif
471 ms
gnbMenu3.gif
487 ms
gnbMenu4.gif
541 ms
gnbMenu5.gif
530 ms
160308_mobile_top.png
1090 ms
mb_20160308_banner_01.jpg
843 ms
mb_20160308_banner_02.jpg
956 ms
mb_20160308_banner_03.jpg
1228 ms
mb_20160314_banner_04.jpg
1585 ms
mainMenuList2.gif
828 ms
mainMenuList5.gif
1105 ms
mainMenuList6.gif
1073 ms
mainMenuList7.gif
1184 ms
title_newproduct.gif
1319 ms
btn_more.gif
1334 ms
btn_prev.gif
1366 ms
btn_next.gif
1413 ms
title_bestproduct.gif
1467 ms
title_photoreview.gif
1575 ms
title_sampleshop.gif
1575 ms
main_sample0408.jpg
2257 ms
main_menu1.gif
1650 ms
main_menu2.gif
1705 ms
main_menu3.gif
1807 ms
main_menu4.gif
1816 ms
main_menu5.gif
1831 ms
main_menu6.gif
1877 ms
footer_link1.gif
1947 ms
footer_link2.gif
2049 ms
footer_link3.gif
2035 ms
collect
55 ms
collect
50 ms
m
675 ms
footer_link5.gif
1922 ms
footer_link4.gif
2010 ms
footer_copy.gif
1967 ms
ineltree.co.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible 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.
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
ineltree.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
Displays images with incorrect aspect ratio
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
ineltree.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 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 Ineltree.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 Ineltree.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.
ineltree.co.kr
Open Graph description is not detected on the main page of Ineltree. 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: