5.9 sec in total
346 ms
3.5 sec
2 sec
Click here to check amazing JCI content for China. Otherwise, check out these important facts you probably never knew about jci.org
Visit jci.orgWe analyzed Jci.org page load time and found that the first response time was 346 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
jci.org performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value7.3 s
5/100
25%
Value6.4 s
40/100
10%
Value4,580 ms
0/100
30%
Value0.409
24/100
15%
Value22.2 s
1/100
10%
346 ms
28 ms
16 ms
694 ms
21 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 27% of them (12 requests) were addressed to the original Jci.org, 27% (12 requests) were made to Dm5migu4zj3pb.cloudfront.net and 7% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Youtube.com.
Page size can be reduced by 1.8 MB (64%)
2.7 MB
970.1 kB
In fact, the total size of Jci.org main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 135.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 135.9 kB or 75% of the original size.
Potential reduce by 31.3 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. Obviously, JCI needs image optimization as it can save up to 31.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.2 MB
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 1.2 MB or 67% of the original size.
Potential reduce by 396.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. Jci.org needs all CSS files to be minified and compressed as it can save up to 396.4 kB or 84% of the original size.
Number of requests can be reduced by 14 (35%)
40
26
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JCI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
jci.org
346 ms
application-bea95c173355d1cd0b2c7ef990df35f1a68bf37486e819f5a98b1102522833dc.css
28 ms
modernizr-8930220bcb710b239a9d4f592dd8d69ac02ed88ca245dc1a59caa99aaa6ec6ed.js
16 ms
application-0b5d1d31e184c9d62cb27677fb13b77d46cc484692d05ca2ab70cecb428eb29b.js
694 ms
addthis_widget.js
21 ms
analytics.js
457 ms
gpt.js
454 ms
thumb_Insight-green-text.png
409 ms
jci-spelled-out-white-on-transparent.20160208-f0c39cd1eaee455c46365719769dc2f4859d68368cfa219e5e491c77d472c0f4.png
319 ms
search-black-867f68b5b717d00fb9c106b8c637cfd33ea8ee8b2ff37a9eaf8cc675abe2fc86.png
314 ms
jci-only-white-8a7e75c924e8f4e2d61f98952aa688ca36f76c9e55ac7fa58f3a9a33a8cb4236.png
313 ms
search-white-cc4a29c31d1a1a75e19da4c773d8175e78de1ac330be7aa089e7212ec0a7b49e.png
313 ms
facebook_logo_white-8549cbbdd5755c8d81d1ab2fdea8326c3ec2963a83ad22b73dff80d93b500a47.png
322 ms
twitter_logo_v2-60ea0c72387950663c0b04fc251455a5a04ed832e9291810914f0d9257b5f597.png
310 ms
google_plus_logo-3a331066b223833927394a4d047a7fbc634a756f0cb6024dd9d74351f0b36717.png
323 ms
rss_icon-cd21b1126f247087e91b0bc6c9d4acc3968c4ecb46461efba523e501876818ba.png
322 ms
JCI79196.f1.gif
322 ms
JCI82978.f1.gif
322 ms
JCI83470.f1.gif
318 ms
JCI84505.f1.gif
330 ms
JCI85271.f1.gif
331 ms
thumb_JCI_Scientific_Show_Stopper_CD37_staining_DLBCL.jpg
327 ms
thumb_Slide1.jpg
320 ms
126-2-cover.jpg
322 ms
jci_tm_2016_02.png
323 ms
KlavikaWebBasicBold.woff
60 ms
linkid.js
35 ms
pubads_impl_80.js
25 ms
rlBlw8kGlnA
1068 ms
yCi0bUDR7KA
1146 ms
collect
931 ms
ads
838 ms
container.html
750 ms
foundation-icons.woff
194 ms
www-embed-player-vfltSWGRn.css
152 ms
www-embed-player.js
202 ms
AUrdvhejKSJD2XN0WEoLkNJn8VW-ISfFFTHwdQR0Ws4.js
53 ms
ad_status.js
198 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
176 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
175 ms
nr-852.min.js
71 ms
300lo.json
27 ms
sh.62b8d491a8960808f9c01d9c.html
136 ms
27b438aa5b
136 ms
layers.405050a634a82f4714cf.js
27 ms
jci.org 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
jci.org 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
jci.org 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
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 Jci.org 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 Jci.org 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.
jci.org
Open Graph description is not detected on the main page of JCI. 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: