Tools & Wizards About Us
jthort.org screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

jthort.org

Journal of Tropical Horticulture

Page Load Speed

6.3 sec in total

First Response

719 ms

Resources Loaded

5.2 sec

Page Rendered

373 ms

jthort.org screenshot

About Website

Click here to check amazing Jthort content. Otherwise, check out these important facts you probably never knew about jthort.org

Journal of Tropical Horticulture with initials JTHORT and abbreviation J. Trop. Hort is a peer-reviewed open-access international journal who aims to the sharing, dissemination, and discussion of curr...

Visit jthort.org

Key Findings

We analyzed Jthort.org page load time and found that the first response time was 719 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

jthort.org performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

jthort

719 ms

pkp.css

236 ms

common.css

482 ms

common.css

503 ms

compiled.css

508 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 70% of them (49 requests) were addressed to the original Jthort.org, 9% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Ijain.org. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Ijain.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.0 kB (13%)

Content Size

816.2 kB

After Optimization

711.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jthort.org main page is 816.2 kB. 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 610.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 20.6 kB

  • Original 27.9 kB
  • After minification 26.9 kB
  • After compression 7.3 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 20.6 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 46.2 kB

  • Original 610.3 kB
  • After minification 564.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. Jthort images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 33.3 kB

  • Original 155.4 kB
  • After minification 153.6 kB
  • After compression 122.2 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 33.3 kB or 21% of the original size.

CSS Optimization

-22%

Potential reduce by 5.0 kB

  • Original 22.6 kB
  • After minification 22.2 kB
  • After compression 17.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. Jthort.org needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (64%)

Requests Now

61

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jthort

jthort

719 ms

pkp.css

pkp.css

236 ms

common.css

common.css

482 ms

common.css

common.css

503 ms

compiled.css

compiled.css

508 ms

jsapi

jsapi

7 ms

sidebar.css

sidebar.css

513 ms

rightSidebar.css

rightSidebar.css

519 ms

journalStyleSheet.css

journalStyleSheet.css

520 ms

jquery.tag-it.js

jquery.tag-it.js

772 ms

jquery.cookie.js

jquery.cookie.js

736 ms

fontController.js

fontController.js

752 ms

general.js

general.js

758 ms

jqueryValidatorI18n.js

jqueryValidatorI18n.js

778 ms

Helper.js

Helper.js

785 ms

ObjectProxy.js

ObjectProxy.js

978 ms

Handler.js

Handler.js

992 ms

LinkActionRequest.js

LinkActionRequest.js

1003 ms

Feature.js

Feature.js

1004 ms

SiteHandler.js

SiteHandler.js

1029 ms

UrlInDivHandler.js

UrlInDivHandler.js

1030 ms

AutocompleteHandler.js

AutocompleteHandler.js

1221 ms

ExtrasOnDemandHandler.js

ExtrasOnDemandHandler.js

1257 ms

FormHandler.js

FormHandler.js

1277 ms

AjaxFormHandler.js

AjaxFormHandler.js

1262 ms

ClientFormHandler.js

ClientFormHandler.js

1270 ms

GridHandler.js

GridHandler.js

1280 ms

LinkActionHandler.js

LinkActionHandler.js

1454 ms

SearchFormHandler.js

SearchFormHandler.js

1512 ms

ReportGeneratorFormHandler.js

ReportGeneratorFormHandler.js

1496 ms

LuceneAutocompleteHandler.js

LuceneAutocompleteHandler.js

1511 ms

jquery.pkp.js

jquery.pkp.js

1517 ms

jquery.validate.js

jquery.validate.js

1540 ms

loader.js

loader.js

27 ms

jqueryUi.css

jqueryUi.css

1459 ms

jquery.pnotify.default.css

jquery.pnotify.default.css

1499 ms

pnotify.css

pnotify.css

1254 ms

notificationIcons.css

notificationIcons.css

1251 ms

jquery.min.js

jquery.min.js

31 ms

jquery-ui.min.js

jquery-ui.min.js

41 ms

css

css

69 ms

css

css

84 ms

batik-BC-Rev.png

batik-BC-Rev.png

77 ms

homeHeaderTitleImage_en_US.jpg

homeHeaderTitleImage_en_US.jpg

479 ms

ebsco.png

ebsco.png

978 ms

673 ms

88x31.png

88x31.png

105 ms

proquest.png

proquest.png

1220 ms

Crossref_Logo_Stacked_RGB_SMALL.png

Crossref_Logo_Stacked_RGB_SMALL.png

1701 ms

template.jpg

template.jpg

251 ms

mendeley.png

mendeley.png

474 ms

ithenticate.jpg

ithenticate.jpg

493 ms

grammarly.jpg

grammarly.jpg

490 ms

turnitin.jpg

turnitin.jpg

489 ms

copernicus.png

copernicus.png

731 ms

googlescholar.png

googlescholar.png

699 ms

garuda.png

garuda.png

708 ms

crossref.png

crossref.png

730 ms

worldcat.png

worldcat.png

731 ms

scilit.png

scilit.png

740 ms

homepageImage_en_US.jpg

homepageImage_en_US.jpg

1170 ms

counter.js

counter.js

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

34 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

50 ms

t.php

t.php

75 ms

dg45_pLmvrkcOkBnKsOzXyGWTBcmgwL9VjvYIg.ttf

dg45_pLmvrkcOkBnKsOzXyGWTBcmgwL9VjvYIg.ttf

9 ms

dg45_pLmvrkcOkBnKsOzXyGWTBcmg-X6VjvYIg.ttf

dg45_pLmvrkcOkBnKsOzXyGWTBcmg-X6VjvYIg.ttf

21 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

17 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

20 ms

88x31.png

88x31.png

52 ms

Accessibility Review

jthort.org accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

jthort.org best practices score

58

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

SEO Factors

jthort.org SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Jthort.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 Jthort.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

jthort.org

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