4.5 sec in total
199 ms
4 sec
220 ms
Click here to check amazing Caijournal content. Otherwise, check out these important facts you probably never knew about caijournal.com
Visit caijournal.comWe analyzed Caijournal.com page load time and found that the first response time was 199 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
caijournal.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value9.8 s
0/100
25%
Value7.1 s
31/100
10%
Value900 ms
31/100
30%
Value0.621
10/100
15%
Value9.4 s
31/100
10%
199 ms
1449 ms
31 ms
43 ms
102 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Caijournal.com, 72% (39 requests) were made to Hksmp.com and 7% (4 requests) were made to Mirrors.creativecommons.org. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Hksmp.com.
Page size can be reduced by 100.4 kB (19%)
526.6 kB
426.2 kB
In fact, the total size of Caijournal.com main page is 526.6 kB. 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 256.3 kB which makes up the majority of the site volume.
Potential reduce by 32.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. 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 32.6 kB or 76% of the original size.
Potential reduce by 2.7 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. Caijournal images are well optimized though.
Potential reduce by 54.1 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 54.1 kB or 27% of the original size.
Potential reduce by 10.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. Caijournal.com needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 37% of the original size.
Number of requests can be reduced by 30 (60%)
50
20
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Caijournal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
caijournal.com
199 ms
cai
1449 ms
widgets.js
31 ms
MathJax.js
43 ms
js
102 ms
css
356 ms
css
710 ms
fontawesome.css
629 ms
mmenu-light.css
651 ms
grid.min.css
652 ms
style.css
653 ms
responsive.css
656 ms
slick.min.css
837 ms
slick-theme.min.css
866 ms
animate.min.css
867 ms
modern_simple.css
871 ms
css
1013 ms
citations.css
919 ms
orcidProfile.css
1045 ms
styleSheet.css
1082 ms
pageHeaderLogoImage_en_US.png
1298 ms
cc.svg
61 ms
jquery.min.js
1301 ms
jquery-ui.min.js
1343 ms
popper.js
1447 ms
util.js
1251 ms
dropdown.js
1295 ms
main.js
1460 ms
mmenu-light.js
1512 ms
readmore.min.js
1513 ms
app.js
1517 ms
slick.min.js
1554 ms
d3.v4.js
93 ms
d3.layout.cloud.js
44 ms
1-9701734e93c63f2daf8546bd5028ace8.jpg
632 ms
eic.jpg
1665 ms
crossref-6496344d3558632e7b41632489b9ad96.jpg
1877 ms
cope.jpg
1943 ms
icmje-bfa1afa71a482ef505323897a31e7872.jpg
1943 ms
wame-e20d75086d045930b3878dbca8fd601e.jpg
1733 ms
ojs_brand.png
1765 ms
by.svg
90 ms
nc.svg
112 ms
sa.svg
113 ms
TeX-MML-AM_CHTML.js
23 ms
css2
30 ms
modern_simple.jpg
837 ms
DOI_logo.svg
864 ms
bar_artikel.jpg
972 ms
bar_galley.jpg
987 ms
KFOmCnqEu92Fr1Me5g.woff
22 ms
fontawesome-webfont.woff
1167 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
35 ms
settings
96 ms
caijournal.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
caijournal.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
caijournal.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Caijournal.com 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 Caijournal.com 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.
caijournal.com
Open Graph description is not detected on the main page of Caijournal. 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: