Tools & Wizards About Us
preprints.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

preprints.org

Preprints.org - The Multidisciplinary Preprint Platform

Page Load Speed

1.5 sec in total

First Response

47 ms

Resources Loaded

1.2 sec

Page Rendered

221 ms

preprints.org screenshot

About Website

Visit preprints.org now to see the best up-to-date Preprints content for United States and also check out these interesting facts you probably never knew about preprints.org

Preprints is a multidisciplinary preprint platform that accepts articles from all fields of science and technology, given that the preprint is scientifically sound and can be considered part of academ...

Visit preprints.org

Key Findings

We analyzed Preprints.org page load time and found that the first response time was 47 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.

Performance Metrics

preprints.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value26.2 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

preprints.org

47 ms

preprints.org

327 ms

www.preprints.org

208 ms

4951.js

56 ms

normalize.css

18 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 91% of them (48 requests) were addressed to the original Preprints.org, 4% (2 requests) were made to Cdnjs.cloudflare.com and 2% (1 request) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (559 ms) relates to the external source Widget.usersnap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (45%)

Content Size

4.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Preprints.org main page is 4.5 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 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 56.5 kB

  • Original 98.8 kB
  • After minification 98.6 kB
  • After compression 42.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. 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 56.5 kB or 57% of the original size.

Image Optimization

-52%

Potential reduce by 2.0 MB

  • Original 3.8 MB
  • After minification 1.8 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, Preprints needs image optimization as it can save up to 2.0 MB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 9.8 kB

  • Original 581.8 kB
  • After minification 581.8 kB
  • After compression 572.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 108 B

  • Original 58.2 kB
  • After minification 58.1 kB
  • After compression 58.1 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. Preprints.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (70%)

Requests Now

46

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Preprints. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

preprints.org

preprints.org

47 ms

preprints.org

preprints.org

327 ms

www.preprints.org

www.preprints.org

208 ms

4951.js

4951.js

56 ms

normalize.css

normalize.css

18 ms

foundation.css

foundation.css

34 ms

jquery-ui.min.css

jquery-ui.min.css

31 ms

font-awesome.min.css

font-awesome.min.css

47 ms

select2.min.css

select2.min.css

49 ms

jquery.tag-editor.css

jquery.tag-editor.css

51 ms

addon.css

addon.css

53 ms

main.css

main.css

55 ms

uc.js

uc.js

48 ms

MathJax.js

MathJax.js

52 ms

email-decode.min.js

email-decode.min.js

50 ms

clipboard.min.js

clipboard.min.js

123 ms

js.cookie.min.js

js.cookie.min.js

143 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

126 ms

modernizr.js

modernizr.js

126 ms

foundation.min.js

foundation.min.js

132 ms

foundation.dropdown.js

foundation.dropdown.js

134 ms

jquery.browser.min.js

jquery.browser.min.js

133 ms

jquery-ui.min.js

jquery-ui.min.js

134 ms

ajaxupload.js

ajaxupload.js

135 ms

jquery.caret.min.js

jquery.caret.min.js

135 ms

jquery.tag-editor.min.js

jquery.tag-editor.min.js

137 ms

feeds_runtime.js

feeds_runtime.js

136 ms

select2.min.js

select2.min.js

137 ms

jquery.collection.js

jquery.collection.js

138 ms

layer.js

layer.js

140 ms

jquery.validate.min.js

jquery.validate.min.js

139 ms

icon.js

icon.js

345 ms

base.js

base.js

347 ms

tex-chtml-full.js

tex-chtml-full.js

351 ms

fingerprint2.min.js

fingerprint2.min.js

348 ms

TeX-AMS-MML_HTMLorMML.js

TeX-AMS-MML_HTMLorMML.js

271 ms

169c7bab-0f94-4f76-877c-d8bf64ad7240

169c7bab-0f94-4f76-877c-d8bf64ad7240

559 ms

sciprints_Logo.png

sciprints_Logo.png

235 ms

Homepage_small3.png

Homepage_small3.png

337 ms

award_announcement_badge.png

award_announcement_badge.png

322 ms

all_research_fields.svg

all_research_fields.svg

322 ms

high_visibility.svg

high_visibility.svg

324 ms

permanent_archiving.svg

permanent_archiving.svg

326 ms

article_level_metrics.svg

article_level_metrics.svg

330 ms

citable.svg

citable.svg

327 ms

bg.png

bg.png

330 ms

new

new

344 ms

paste.svg

paste.svg

339 ms

award_announcement_badge_small.png

award_announcement_badge_small.png

338 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

332 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

333 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

332 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

184 ms

Accessibility Review

preprints.org accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

preprints.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

preprints.org SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Preprints.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 Preprints.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.

Social Sharing Optimization

preprints.org

Open Graph description is not detected on the main page of Preprints. 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: