Tools & Wizards About Us
peerj.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

peerj.com

PeerJ

Page Load Speed

2.3 sec in total

First Response

101 ms

Resources Loaded

818 ms

Page Rendered

1.4 sec

peerj.com screenshot

About Website

Welcome to peerj.com homepage info - get ready to check PeerJ best content for United States right away, or after learning these important things about peerj.com

Award-winning Open Access publisher for the biomedical sciences.

Visit peerj.com

Key Findings

We analyzed Peerj.com page load time and found that the first response time was 101 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.

Performance Metrics

peerj.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value21.5 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value6,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

peerj.com

101 ms

01e6f72-493e78b.css

12 ms

d1cbeec-708a291.css

27 ms

jquery.min.js

66 ms

jquery-migrate.min.js

30 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 17% of them (11 requests) were addressed to the original Peerj.com, 47% (31 requests) were made to D2pdyyx74uypu5.cloudfront.net and 21% (14 requests) were made to Dfzljdn9uc3pi.cloudfront.net. The less responsive or slowest element that took the longest time to load (451 ms) relates to the external source D2pdyyx74uypu5.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.7 kB (26%)

Content Size

1.4 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peerj.com main page is 1.4 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. 50% of websites need less resources to load. Images take 904.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 57.1 kB

  • Original 73.1 kB
  • After minification 60.6 kB
  • After compression 16.0 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 12.5 kB, which is 17% 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 57.1 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 32.8 kB

  • Original 904.9 kB
  • After minification 872.1 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. PeerJ images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 100.1 kB

  • Original 209.5 kB
  • After minification 209.5 kB
  • After compression 109.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 100.1 kB or 48% of the original size.

CSS Optimization

-82%

Potential reduce by 172.6 kB

  • Original 211.3 kB
  • After minification 211.1 kB
  • After compression 38.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. Peerj.com needs all CSS files to be minified and compressed as it can save up to 172.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (26%)

Requests Now

57

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PeerJ. 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 as a result speed up the page load time.

Network Requests Diagram

peerj.com

peerj.com

101 ms

01e6f72-493e78b.css

01e6f72-493e78b.css

12 ms

d1cbeec-708a291.css

d1cbeec-708a291.css

27 ms

jquery.min.js

jquery.min.js

66 ms

jquery-migrate.min.js

jquery-migrate.min.js

30 ms

4449d57-e18c583.js

4449d57-e18c583.js

7 ms

73eacb4-ab1eb45.js

73eacb4-ab1eb45.js

6 ms

2f4878c-1a84baf.js

2f4878c-1a84baf.js

9 ms

analytics.js

analytics.js

249 ms

peerj-1719-huntsman-spider-2.jpg

peerj-1719-huntsman-spider-2.jpg

369 ms

video-thumb.png

video-thumb.png

321 ms

widgets.js

widgets.js

382 ms

fig-1-small.jpg

fig-1-small.jpg

344 ms

logo.png

logo.png

201 ms

editors.png

editors.png

202 ms

editors-hover.png

editors-hover.png

201 ms

widely-read.png

widely-read.png

310 ms

widely-read-hover.png

widely-read-hover.png

207 ms

fast.png

fast.png

211 ms

fast-hover.png

fast-hover.png

210 ms

low-cost.png

low-cost.png

211 ms

low-cost-hover.png

low-cost-hover.png

214 ms

open-access.png

open-access.png

217 ms

open-access-hover.png

open-access-hover.png

218 ms

video-thumb-play-icon.png

video-thumb-play-icon.png

218 ms

hausen.png

hausen.png

229 ms

award.png

award.png

228 ms

institution.png

institution.png

225 ms

twitter.png

twitter.png

226 ms

carousel-arrow-left.png

carousel-arrow-left.png

451 ms

JackieThai130.jpg

JackieThai130.jpg

235 ms

jason_130.jpg

jason_130.jpg

239 ms

Pete.jpg

Pete.jpg

262 ms

sophie_130.jpg

sophie_130.jpg

237 ms

ali-130.jpg

ali-130.jpg

261 ms

chris-130.jpg

chris-130.jpg

260 ms

alf_sq.jpg

alf_sq.jpg

260 ms

carousel-arrow-right.png

carousel-arrow-right.png

262 ms

blog.png

blog.png

260 ms

peerj-1707-western-scrub-jay-ccby4-corina-logan-2016.jpg

peerj-1707-western-scrub-jay-ccby4-corina-logan-2016.jpg

263 ms

oreilly.png

oreilly.png

263 ms

sage.png

sage.png

264 ms

logo-usenix-grey-footer.png

logo-usenix-grey-footer.png

264 ms

fig-1-small.jpg

fig-1-small.jpg

205 ms

fig-1-small.jpg

fig-1-small.jpg

203 ms

fig-1-small.jpg

fig-1-small.jpg

202 ms

fig-1-small.jpg

fig-1-small.jpg

208 ms

fig-2-small.jpg

fig-2-small.jpg

213 ms

fig-5-small.jpg

fig-5-small.jpg

210 ms

fig-5-small.jpg

fig-5-small.jpg

220 ms

fig-2-small.jpg

fig-2-small.jpg

210 ms

fig-3-small.jpg

fig-3-small.jpg

211 ms

fig-4-small.jpg

fig-4-small.jpg

219 ms

fig-2-small.jpg

fig-2-small.jpg

226 ms

32.jpg

32.jpg

227 ms

31.jpg

31.jpg

229 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

134 ms

icomoon.woff

icomoon.woff

84 ms

152 ms

load

load

142 ms

83 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

32 ms

syndication

syndication

115 ms

313290186018668544

313290186018668544

137 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

31 ms

nr-852.min.js

nr-852.min.js

55 ms

Accessibility Review

peerj.com accessibility score

87

Accessibility Issues

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

High

ARIA progressbar elements do not have accessible names.

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

peerj.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

peerj.com SEO score

92

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peerj.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Peerj.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.

Social Sharing Optimization

peerj.com

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