10.2 sec in total
2.2 sec
7.4 sec
503 ms
Welcome to eara.co.kr homepage info - get ready to check Eara best content for South Korea right away, or after learning these important things about eara.co.kr
castpd@nate.com
Visit eara.co.krWe analyzed Eara.co.kr page load time and found that the first response time was 2.2 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Eara.co.kr rating and web reputation
eara.co.kr performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value8.8 s
1/100
25%
Value7.5 s
27/100
10%
Value60 ms
100/100
30%
Value0.018
100/100
15%
Value7.1 s
52/100
10%
2230 ms
655 ms
688 ms
424 ms
425 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Eara.co.kr, 33% (38 requests) were made to S1.daumcdn.net and 5% (6 requests) were made to Cfile2.uf.tistory.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Cfile29.uf.tistory.com.
Page size can be reduced by 821.2 kB (26%)
3.2 MB
2.4 MB
In fact, the total size of Eara.co.kr main page is 3.2 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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 93.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. This page needs HTML code to be minified as it can gain 12.5 kB, which is 11% 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 93.7 kB or 83% of the original size.
Potential reduce by 35.1 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. Eara images are well optimized though.
Potential reduce by 182.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 182.4 kB or 57% of the original size.
Potential reduce by 509.9 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. Eara.co.kr needs all CSS files to be minified and compressed as it can save up to 509.9 kB or 91% of the original size.
Number of requests can be reduced by 43 (38%)
114
71
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eara. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
eara.co.kr
2230 ms
style.css
655 ms
util.js
688 ms
lightbox.min.css
424 ms
style.css
425 ms
profile.js
683 ms
jigu-latest.min.js
972 ms
T.js
340 ms
EAF2.js
631 ms
common.js
870 ms
gallery.js
551 ms
flash.js
572 ms
PHON.js
604 ms
sha256.js
762 ms
md5.min.js
788 ms
swfobject.js
829 ms
dialog.css
841 ms
reset.css
984 ms
tabloid.css
1435 ms
items.css
1277 ms
util.css
1050 ms
tistory-grid-min.css
1308 ms
items.js
1179 ms
mapSidebar.css
1182 ms
menubar.css
1260 ms
rainbow.js
1389 ms
1428 ms
ga.js
6 ms
__utm.gif
11 ms
show_ads.js
5 ms
functions.js
782 ms
searchDragSelection.js
1807 ms
lightbox.min.js
993 ms
td.min.js
802 ms
roosevelt_dk_bt.js
59 ms
check.php
386 ms
25023A44567ED4A80EB531
2499 ms
2177113E567DD47D06E6DA
2497 ms
253FDA42567A4F9726B5C9
2782 ms
2169234656684E193E9882
2605 ms
2145D14256676B0504CB99
2225 ms
2140EF4D564D06C2182868
2744 ms
277480375632A4D814B1E8
2532 ms
214D5C3556017A7A0CE942
2360 ms
2528804C55DE6B450EF598
1557 ms
265D944B55CD47C6200ADF
1895 ms
2430A64E55C941A71CD7F8
2390 ms
220D335053734E51254C07
1626 ms
2225FB3752AC93DC3337AD
2093 ms
245DF54752AC3F240F94CB
2240 ms
150BA833513730432FD4D4
1204 ms
2179B73C51372F0D203674
1983 ms
2242CD3653798F6D183A71
2874 ms
250F564652BA5ACE336F7B
2516 ms
2455313454932C440B618D
2260 ms
252C0850540E6B9B301802
2256 ms
count.php
419 ms
2376DE505329CE492BDF19
3129 ms
2227373351E5D47918DD09
2516 ms
215DDA4D565354AF034681
2834 ms
21245646547C0D8809B2BF
2219 ms
2121784553E3F1BD10EE98
2820 ms
175F5B3C513728C130ABB0
1242 ms
close.png
991 ms
loading.gif
262 ms
prev.png
261 ms
next.png
985 ms
rss1.png
288 ms
21351F4052072B1B322230
1554 ms
2663304E5373974E207DA1
1947 ms
171CCD35515053481F49A8
2870 ms
1403F8164B8735F440D0AB
1563 ms
2435493753CC8C6F2BDC0C
2648 ms
2122DE3853D6F7EA1C6997
2637 ms
25023A44567ED4A80EB531
1812 ms
2428E54D537367BA39B86F
1614 ms
2767DD3A53726B0931560F
1628 ms
2103553D53E3F232282C4E
1874 ms
21596A3E549E3EEA086163
2836 ms
2154254F53E92870198704
3166 ms
2177113E567DD47D06E6DA
1593 ms
254A2134538B5186232C5F
1273 ms
2323163552ACB3722EE713
933 ms
22570749529C3AB90F4B23
1245 ms
2409E14554794A851397BD
2178 ms
253FDA42567A4F9726B5C9
1861 ms
2169234656684E193E9882
1546 ms
21246A3C562F14402AF437
1572 ms
266FBE4C565355A004A966
2364 ms
21504549537392AE2BEB4D
4363 ms
2629BD4A54A740A52263E1
2101 ms
231DED3552616F6B011A8F
2205 ms
27757433514B3D0704D5F4
2219 ms
27426C4E5490B9FE0B2406
971 ms
2664F44D54860EF932C12F
1199 ms
215E213C5536188229D71D
2439 ms
red-menutops.png
610 ms
red-search1.png
395 ms
folder-horizontal.png
471 ms
mapSidebar.js
498 ms
zrt_lookup.html
29 ms
show_ads_impl.js
39 ms
ads
283 ms
areas.png
495 ms
osd.js
18 ms
10506357133778047580
49 ms
abg.js
51 ms
m_js_controller.js
61 ms
googlelogo_color_112x36dp.png
35 ms
s
27 ms
x_button_blue2.png
27 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
3 ms
swfobject.js
216 ms
searchMapSidebarCount.php
396 ms
jquery.min.js
29 ms
footsteps
1609 ms
eara.co.kr 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
Image elements do not have [alt] attributes
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.
eara.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
eara.co.kr 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
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
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eara.co.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 Eara.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.
eara.co.kr
Open Graph data is detected on the main page of Eara. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: