61.1 sec in total
15.7 sec
45.2 sec
194 ms
Visit ithinkso.co.kr now to see the best up-to-date Ithinkso content and also check out these interesting facts you probably never knew about ithinkso.co.kr
기분좋은 일상에서, 아이띵소
Visit ithinkso.co.krWe analyzed Ithinkso.co.kr page load time and found that the first response time was 15.7 sec and then it took 45.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ithinkso.co.kr performance score
name
value
score
weighting
Value11.7 s
0/100
10%
Value103.4 s
0/100
25%
Value19.0 s
0/100
10%
Value670 ms
44/100
30%
Value0.001
100/100
15%
Value79.8 s
0/100
10%
15720 ms
204 ms
4276 ms
1911 ms
1309 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 82% of them (61 requests) were addressed to the original Ithinkso.co.kr, 7% (5 requests) were made to Sntworks.speedgabia.com and 5% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Sntworks.speedgabia.com.
Page size can be reduced by 1.5 MB (33%)
4.6 MB
3.1 MB
In fact, the total size of Ithinkso.co.kr main page is 4.6 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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 84.7 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 84.7 kB or 81% of the original size.
Potential reduce by 5.4 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. Ithinkso images are well optimized though.
Potential reduce by 789.8 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 789.8 kB or 70% of the original size.
Potential reduce by 610.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. Ithinkso.co.kr needs all CSS files to be minified and compressed as it can save up to 610.1 kB or 85% of the original size.
Number of requests can be reduced by 50 (74%)
68
18
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ithinkso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
ithinkso.co.kr
15720 ms
analytics.js
204 ms
wp-emoji-release.min.js
4276 ms
layerslider.css
1911 ms
css
1309 ms
styles.css
1307 ms
settings.css
1196 ms
collect
44 ms
woocommerce-layout.css
1443 ms
woocommerce.css
1860 ms
prettyPhoto.css
1553 ms
jquery.selectBox.css
1882 ms
style.css
2131 ms
font-awesome.min.css
2473 ms
bootstrap.min.css
6423 ms
ss-gizmo.css
5866 ms
font-awesome.min.css
7053 ms
style.css
2934 ms
responsive.css
3760 ms
greensock.js
6464 ms
jquery.js
5902 ms
jquery-migrate.min.js
5774 ms
layerslider.kreaturamedia.jquery.js
7006 ms
layerslider.transitions.js
6672 ms
jquery.themepunch.tools.min.js
7789 ms
jquery.themepunch.revolution.min.js
7359 ms
style.css
11454 ms
jquery.form.min.js
2048 ms
scripts.js
2488 ms
add-to-cart.min.js
2480 ms
jquery.blockUI.min.js
2538 ms
woocommerce.min.js
2781 ms
jquery.cookie.min.js
2976 ms
cart-fragments.min.js
3000 ms
jquery.selectBox.min.js
3256 ms
jquery.yith-wcwl.js
3030 ms
bootstrap.min.js
3464 ms
jquery-ui-1.10.2.custom.min.js
3519 ms
jquery.flexslider-min.js
3767 ms
jquery.easing.js
3596 ms
owl.carousel.min.js
4242 ms
theme-scripts.js
13738 ms
ilightbox.min.js
5085 ms
js
120 ms
jquery.isotope.min.js
4620 ms
imagesloaded.js
4278 ms
jquery.infinitescroll.min.js
4956 ms
functions.js
6238 ms
wp-embed.min.js
5129 ms
home_01.jpg
5077 ms
ithinkso_weblogo.png
526 ms
home_02.jpg
20216 ms
home_03.jpg
8609 ms
home_04.jpg
5951 ms
home_05.jpg
5184 ms
mobil_ithinkso1.gif
663 ms
web_ithinkso.gif
956 ms
fontawesome-webfont.woff
2923 ms
fontawesome-webfont.woff
3317 ms
ss-gizmo.woff
3057 ms
revolution.extension.slideanims.min.js
463 ms
revolution.extension.actions.min.js
254 ms
revolution.extension.layeranimation.min.js
681 ms
revolution.extension.navigation.min.js
685 ms
ithinkso.co.kr
1246 ms
coloredbg.png
490 ms
loader.gif
489 ms
slider-nav.png
502 ms
revicons.woff
501 ms
woocommerce-smallscreen.css
545 ms
common.js
14 ms
util.js
34 ms
stats.js
35 ms
AuthenticationService.Authenticate
305 ms
ithinkso.co.kr accessibility score
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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
ithinkso.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
General
Impact
Issue
Detected JavaScript libraries
ithinkso.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ithinkso.co.kr 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), while the claimed language is Korean. Our system also found out that Ithinkso.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.
ithinkso.co.kr
Open Graph description is not detected on the main page of Ithinkso. 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: