2.5 sec in total
292 ms
1.8 sec
401 ms
Click here to check amazing F1000Research content for Malaysia. Otherwise, check out these important facts you probably never knew about f1000research.com
F1000Research is an innovative open access publishing platform offering rapid publication and open peer review, whilst supporting data deposition and sharing.
Visit f1000research.comWe analyzed F1000research.com page load time and found that the first response time was 292 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
f1000research.com performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value9.5 s
0/100
25%
Value10.8 s
7/100
10%
Value1,830 ms
9/100
30%
Value0.105
88/100
15%
Value21.2 s
1/100
10%
292 ms
501 ms
169 ms
165 ms
59 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 81% of them (59 requests) were addressed to the original F1000research.com, 5% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain F1000research.com.
Page size can be reduced by 1.5 MB (67%)
2.3 MB
755.3 kB
In fact, the total size of F1000research.com main page is 2.3 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. 45% of websites need less resources to load. CSS take 884.9 kB which makes up the majority of the site volume.
Potential reduce by 61.2 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 13.8 kB, which is 18% 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 61.2 kB or 81% of the original size.
Potential reduce by 68.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. Obviously, F1000Research needs image optimization as it can save up to 68.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 619.4 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 619.4 kB or 75% of the original size.
Potential reduce by 761.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. F1000research.com needs all CSS files to be minified and compressed as it can save up to 761.6 kB or 86% of the original size.
Number of requests can be reduced by 38 (53%)
72
34
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F1000Research. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
f1000research.com
292 ms
main.css
501 ms
F1000ResearchFontIcons.css
169 ms
animation.css
165 ms
jquery.min.js
59 ms
modernizr-2.6.1-respond-1.1.0.min.js
241 ms
underscore-1.4.2.js
328 ms
plugins.js
645 ms
research.js
243 ms
research.ui.js
423 ms
login.js
323 ms
main.js
487 ms
js-date-format.min.js
490 ms
search.js
410 ms
cookies_warning.js
492 ms
MathJax.js
30 ms
research.home.js
536 ms
research.videos.js
570 ms
back_to_top_helper.js
573 ms
sticky-footer.js
501 ms
research.analytics.js
503 ms
jquery.cleditor.css
99 ms
jquery-ui-1.8.24.custom.css
155 ms
TeX-AMS-MML_HTMLorMML.js
67 ms
fbds.js
63 ms
F1000Prime_logo_header.png
159 ms
F1000Workspace_logo_header.png
155 ms
header_dropshadow.png
156 ms
F1000R_logo_header.png
148 ms
home_mainpic_black.jpg
648 ms
padlock_icon_white.png
148 ms
license_icon_CC.png
186 ms
license_icon_BY.png
186 ms
license_icon_PD0.png
191 ms
F1000R_logo_home.png
187 ms
Proxima_Nova_Sbold-webfont.woff
190 ms
ap_CtWNF_normal.png
189 ms
Fs8pS-KI_normal.jpg
237 ms
_fMPwwQw_normal.png
248 ms
biosharing_grey.png
246 ms
biosharing.png
246 ms
cope_grey_text.png
268 ms
cope_text.png
273 ms
DOAJ_logo_gray.png
267 ms
DOAJ_logo.png
318 ms
resource_initiative_grey.png
319 ms
resource_initiative.png
350 ms
oaspa_logo_grey.png
350 ms
oaspa_logo.png
359 ms
orcid_logo_grey.png
399 ms
orcid_logo.png
404 ms
romeo_shaded_grey.png
432 ms
romeo_shaded.png
432 ms
icon_quote.png
578 ms
video_01.jpg
442 ms
button_play_big_default.png
444 ms
video_02.jpg
553 ms
video_03.jpg
473 ms
video_04.jpg
603 ms
illustration_shareposters_slides.png
528 ms
f1000research-footer.png
554 ms
F1000ResearchFontIcons.woff
608 ms
Proxima_Nova_Reg-webfont.woff
714 ms
analytics.js
102 ms
confirm-msg-modal.gif
544 ms
cookie-warning-close.png
570 ms
91 ms
Proxima_Nova_Bold-webfont.woff
547 ms
collect
17 ms
collect
57 ms
collect
19 ms
collect
26 ms
31 ms
f1000research.com 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 input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
f1000research.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
f1000research.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
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise F1000research.com 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 F1000research.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.
f1000research.com
Open Graph description is not detected on the main page of F1000Research. 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: