8.4 sec in total
768 ms
7.1 sec
520 ms
Click here to check amazing Jrd content. Otherwise, check out these important facts you probably never knew about jrd.or.kr
Journal of Rheumatic Diseases, J Rheum Dis, JRD
Visit jrd.or.krWe analyzed Jrd.or.kr page load time and found that the first response time was 768 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jrd.or.kr performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value12.6 s
0/100
25%
Value17.4 s
0/100
10%
Value340 ms
74/100
30%
Value0.434
21/100
15%
Value26.8 s
0/100
10%
768 ms
970 ms
73 ms
25 ms
188 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 60% of them (53 requests) were addressed to the original Jrd.or.kr, 15% (13 requests) were made to Pdf.medrang.co.kr and 13% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Pdf.medrang.co.kr.
Page size can be reduced by 2.2 MB (32%)
6.9 MB
4.7 MB
In fact, the total size of Jrd.or.kr main page is 6.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. Only a small number of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 71.6 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 10.7 kB, which is 12% 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 71.6 kB or 83% of the original size.
Potential reduce by 1.2 MB
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. Obviously, Jrd needs image optimization as it can save up to 1.2 MB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 868.7 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 868.7 kB or 75% of the original size.
Potential reduce by 128.6 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. Jrd.or.kr needs all CSS files to be minified and compressed as it can save up to 128.6 kB or 82% of the original size.
Number of requests can be reduced by 19 (26%)
74
55
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jrd. 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 from 9 to 1 for CSS and as a result speed up the page load time.
jrd.or.kr
768 ms
main.html
970 ms
js
73 ms
xeicon.min.css
25 ms
bootstrap.modal.css
188 ms
slick.css
376 ms
reset.css
564 ms
common.css
758 ms
sub.css
1033 ms
jquery-1.12.4.min.js
1029 ms
jqcloud.min.js
30 ms
bootstrap.modal.js
618 ms
slick.js
1031 ms
common.js
751 ms
sub.js
815 ms
MathJax.js
1181 ms
Chart.bundle.js
2770 ms
utils.js
1046 ms
jquery-ui-draggable-1.12.1.min.js
1146 ms
css2
32 ms
css2
50 ms
css2
54 ms
TeX-AMS-MML_HTMLorMML.js
1013 ms
header_bg.png
207 ms
jrd-31-3-151-f1.jpg
2833 ms
h1-logo.png
205 ms
open_access.png
204 ms
header_mark.png
204 ms
header_ESCI.png
204 ms
header_scopus.png
191 ms
top-ban03.png
364 ms
top-ban04.png
381 ms
qr.png
401 ms
highlight-bg.png
1819 ms
no_image.png
427 ms
JRD_031_03.png
402 ms
ic-tag-pmc.png
566 ms
ic-tag-cite.png
592 ms
share_icon.png
608 ms
main-longbanner.png
2402 ms
ic-edit-tel.png
645 ms
ic-edit-fax.png
771 ms
ic-edit-mail.png
810 ms
journal_info.png
831 ms
archive.png
861 ms
for_author.png
975 ms
ethical_policy.png
1024 ms
e-submission.png
1047 ms
contact_us.png
1076 ms
banner_01.png
1178 ms
banner_02.png
1220 ms
banner_03.png
1257 ms
banner_04.png
1293 ms
banner_05.png
1376 ms
banner_06.png
1417 ms
banner_07.png
1467 ms
banner_08.png
1499 ms
ic-sns01.png
1593 ms
ic-sns02.png
1655 ms
ic-sns04.png
1666 ms
jrd-31-3-160-f1.jpg
2648 ms
jrd-31-3-171-f1.jpg
2310 ms
jrd-31-3-178-f1.jpg
2303 ms
jrd-31-3-182-f1.jpg
2132 ms
jrd-31-3-188-f1.jpg
2928 ms
jrd-31-3-151-f1.jpg
2330 ms
jrd-29-3-140-f1.jpg
2514 ms
jrd-29-1-4-f1.jpg
2503 ms
jrd-30-2-116-f1.jpg
2529 ms
jrd-29-1-46-f1.jpg
2697 ms
jrd-29-1-14-f1.jpg
2707 ms
jrd-29-2-116-f1.jpg
2726 ms
ic-sns05.png
1512 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
61 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
72 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
71 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
73 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLQ.ttf
239 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLQ.ttf
163 ms
PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQyeLQ.ttf
262 ms
xeicon.ttf
12 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuyJG.ttf
97 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvCJG.ttf
95 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vCJG.ttf
97 ms
ic-edit-homepage.png
1581 ms
ic-rolling-prev.png
203 ms
ic-rolling-next.png
241 ms
jrd.or.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.
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
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>).
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.
jrd.or.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
Missing source maps for large first-party JavaScript
jrd.or.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 uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jrd.or.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Jrd.or.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.
jrd.or.kr
Open Graph description is not detected on the main page of Jrd. 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: