1.7 sec in total
205 ms
1.2 sec
314 ms
Click here to check amazing Annex Journals content for India. Otherwise, check out these important facts you probably never knew about annexjournals.org
Annex Publishers is an interactive open access journal publisher for the communication of all scientific and medical research. Open Access Publisher in United States.
Visit annexjournals.orgWe analyzed Annexjournals.org page load time and found that the first response time was 205 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
annexjournals.org performance score
205 ms
315 ms
41 ms
73 ms
83 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Annexjournals.org, 90% (76 requests) were made to Annexpublishers.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (317 ms) relates to the external source Annexpublishers.com.
Page size can be reduced by 294.8 kB (26%)
1.1 MB
835.4 kB
In fact, the total size of Annexjournals.org main page is 1.1 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. 55% of websites need less resources to load. Images take 827.7 kB which makes up the majority of the site volume.
Potential reduce by 28 B
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 28 B or 21% of the original size.
Potential reduce by 94.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, Annex Journals needs image optimization as it can save up to 94.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 118.0 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 118.0 kB or 58% of the original size.
Potential reduce by 82.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. Annexjournals.org needs all CSS files to be minified and compressed as it can save up to 82.4 kB or 84% of the original size.
Number of requests can be reduced by 29 (35%)
82
53
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Annex Journals. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
annexjournals.org
205 ms
www.annexpublishers.com
315 ms
normalize.css
41 ms
style.css
73 ms
touchTouch.css
83 ms
media-queries.css
70 ms
1140.css
84 ms
styles.css
84 ms
css
24 ms
css
37 ms
jquery-1.7.2.min.js
112 ms
superfish.js
134 ms
jquery.mobilemenu.js
105 ms
si.files.js
107 ms
audio1.js
134 ms
jsfunctions.js
133 ms
jquery.mobile.customized.min.js
144 ms
tie-scripts.js
142 ms
generic.css
178 ms
js-image-slider.css
179 ms
slider.css
180 ms
js-image-slider.js
181 ms
ga.js
20 ms
counter.js
20 ms
bg-body.gif
121 ms
pubmed.png
120 ms
17jhome-icon.jpg
118 ms
9jhome-icon.jpg
121 ms
10jhome-icon.jpg
122 ms
11jhome-icon.jpg
118 ms
5jhome-icon.jpg
123 ms
20jhome-icon.jpg
123 ms
21jhome-icon.jpg
125 ms
22jhome-icon.jpg
123 ms
23jhome-icon.jpg
124 ms
24jhome-icon.jpg
126 ms
25jhome-icon.jpg
125 ms
26jhome-icon.jpg
127 ms
27jhome-icon.jpg
133 ms
28jhome-icon.jpg
149 ms
29jhome-icon.jpg
148 ms
30jhome-icon.jpg
148 ms
31jhome-icon.jpg
152 ms
32jhome-icon.jpg
150 ms
33jhome-icon.jpg
160 ms
34jhome-icon.jpg
176 ms
35jhome-icon.jpg
182 ms
36jhome-icon.jpg
179 ms
37jhome-icon.jpg
190 ms
38jhome-icon.jpg
189 ms
39jhome-icon.jpg
195 ms
40jhome-icon.jpg
216 ms
41jhome-icon.jpg
215 ms
42jhome-icon.jpg
217 ms
43jhome-icon.jpg
229 ms
44jhome-icon.jpg
228 ms
45jhome-icon.jpg
229 ms
46jhome-icon.jpg
248 ms
47jhome-icon.jpg
250 ms
why-with-us.jpg
289 ms
t.php
101 ms
__utm.gif
22 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
21 ms
openaccess-s.png
193 ms
67rh-image.jpg
176 ms
270rh-image.jpg
179 ms
453rh-image.jpg
187 ms
190rh-image.jpg
186 ms
cross.jpg
242 ms
googlescholar.jpg
239 ms
citefactor.jpg
227 ms
icmje.jpg
248 ms
in.png
226 ms
facebook.png
226 ms
twitter.png
264 ms
feed.png
263 ms
top-menu-marker.png
265 ms
Annex9-small.png
264 ms
menu-separator.png
250 ms
list-marker.png
269 ms
loading.gif
287 ms
main-menu-marker.png
276 ms
bg-menu.gif
281 ms
72jhome_image24.jpg
317 ms
annexjournals.org SEO score
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Annexjournals.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Annexjournals.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
annexjournals.org
Open Graph description is not detected on the main page of Annex Journals. 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: