16.9 sec in total
4.5 sec
11.6 sec
898 ms
Visit researcher.co.kr now to see the best up-to-date Research Er content and also check out these interesting facts you probably never knew about researcher.co.kr
IT, E-business, SNS, E-Commerce, Professional
Visit researcher.co.krWe analyzed Researcher.co.kr page load time and found that the first response time was 4.5 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
researcher.co.kr performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value5.0 s
26/100
25%
Value10.4 s
8/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value6.3 s
60/100
10%
4481 ms
722 ms
479 ms
728 ms
986 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Researcher.co.kr, 69% (51 requests) were made to S1.daumcdn.net and 5% (4 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Cfile26.uf.tistory.com.
Page size can be reduced by 402.3 kB (15%)
2.6 MB
2.2 MB
In fact, the total size of Researcher.co.kr main page is 2.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. 25% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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. 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 55.9 kB or 76% of the original size.
Potential reduce by 47.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. Research Er images are well optimized though.
Potential reduce by 237.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 237.2 kB or 70% of the original size.
Potential reduce by 61.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. Researcher.co.kr needs all CSS files to be minified and compressed as it can save up to 61.4 kB or 83% of the original size.
Number of requests can be reduced by 54 (74%)
73
19
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Research Er. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
researcher.co.kr
4481 ms
style.css
722 ms
style.css
479 ms
profile.js
728 ms
jigu-latest.min.js
986 ms
T.js
504 ms
EAF2.js
759 ms
common.js
1228 ms
gallery.js
755 ms
flash.js
954 ms
PHON.js
969 ms
sha256.js
1007 ms
md5.min.js
1011 ms
swfobject.js
1189 ms
dialog.css
1210 ms
menubar.css
1238 ms
470 ms
searchDragSelection.js
875 ms
td.min.js
271 ms
roosevelt_dk_bt.js
7 ms
check.php
269 ms
23664E4955F023611767CD
1425 ms
250A253D55F02407320EF5
2029 ms
ccl_black01.png
25 ms
195C4C274CE680D40264A8
1036 ms
1651F8274CE6879837EEEC
1503 ms
14489A254CD97B40182213
2510 ms
2041C3024CE68A9D44D8D5
6215 ms
1531EC0C4CE65D7335E875
2513 ms
ccl_black02.png
24 ms
btn_track_white.gif
23 ms
207B7B324CE643884964FA
3913 ms
bg_con_left.png
285 ms
bg_con_right.gif
288 ms
bg_content.gif
284 ms
desc_line.gif
295 ms
ico_tag.gif
277 ms
track_line.gif
265 ms
bg_bottom_left.gif
505 ms
bg_bottom_right.gif
500 ms
410 ms
405 ms
ico_prev.png
456 ms
line_paging.gif
458 ms
ico_next.png
471 ms
title.png
485 ms
bg_side_line.gif
697 ms
bg_search.gif
712 ms
line_sidebar.gif
717 ms
tit_category.png
704 ms
bar_category.gif
731 ms
tit_tag.png
743 ms
tit_recent_post.png
940 ms
tit_recent_comment.png
947 ms
tit_trackback.png
968 ms
tit_link.png
983 ms
tit_archive.png
990 ms
tit_notice.png
1007 ms
tit_calendar.png
1204 ms
cal_pre.png
1212 ms
cal_next.png
1228 ms
tit_total.png
1236 ms
tit_today.png
1279 ms
tit_yesterday.png
1271 ms
tistory.png
1450 ms
rss.png
1455 ms
footsteps
1168 ms
jquery-1.11.0.min.js
2085 ms
uoclike.min.js
1127 ms
uoclike.min-20150408-2.css
23 ms
523680_21.json
723 ms
523680_22.json
699 ms
print.css
265 ms
img_empathy_141113.png
7 ms
researcher.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
researcher.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
Page has valid source maps
researcher.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
Links do not have descriptive text
Image elements do not have [alt] attributes
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
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Researcher.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 Researcher.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.
researcher.co.kr
Open Graph data is detected on the main page of Research Er. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: