Tools & Wizards About Us
jspp.org screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

jspp.org

日本植物生理学会

Page Load Speed

6.2 sec in total

First Response

672 ms

Resources Loaded

5.3 sec

Page Rendered

248 ms

jspp.org screenshot

About Website

Click here to check amazing Jspp content for Japan. Otherwise, check out these important facts you probably never knew about jspp.org

一般社団法人日本植物生理学会の公式ウェブサイトです。当会の活動、年会、学術誌PCP、出版物、植物QandA、研究室紹介などの情報・コンテンツを発信しています。

Visit jspp.org

Key Findings

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

jspp.org performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

jspp.org

672 ms

jspp.org

1500 ms

font-awesome.min.css

500 ms

style.css

669 ms

top.css

842 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 95% of them (40 requests) were addressed to the original Jspp.org, 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Jspp.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.1 kB (10%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jspp.org main page is 1.6 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. 15% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.2 kB

  • Original 25.7 kB
  • After minification 23.5 kB
  • After compression 6.5 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 19.2 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 17.5 kB

  • Original 1.4 MB
  • After minification 1.3 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. Jspp images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 77.6 kB

  • Original 132.6 kB
  • After minification 123.6 kB
  • After compression 54.9 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 77.6 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 46.8 kB

  • Original 57.3 kB
  • After minification 50.0 kB
  • After compression 10.5 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. Jspp.org needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (45%)

Requests Now

40

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jspp.org

jspp.org

672 ms

jspp.org

jspp.org

1500 ms

font-awesome.min.css

font-awesome.min.css

500 ms

style.css

style.css

669 ms

top.css

top.css

842 ms

jquery.js

jquery.js

1346 ms

lib.js

lib.js

1249 ms

common.js

common.js

1055 ms

top.js

top.js

1175 ms

ga.js

ga.js

1274 ms

ga.js

ga.js

129 ms

bg_white.png

bg_white.png

183 ms

ajax-loader-top.gif

ajax-loader-top.gif

185 ms

khc6845y3.jpg

khc6845y3.jpg

1391 ms

new_bg_gradation_white.png

new_bg_gradation_white.png

181 ms

new_bg_line_x.png

new_bg_line_x.png

186 ms

bg_header_shadow.png

bg_header_shadow.png

199 ms

icon_logo.png

icon_logo.png

346 ms

btn_public_student.png

btn_public_student.png

347 ms

new_bg_line_y.png

new_bg_line_y.png

355 ms

text_top_title.png

text_top_title.png

710 ms

bg_top_banner_area_repeat_x.png

bg_top_banner_area_repeat_x.png

389 ms

banner_pcp.png

banner_pcp.png

516 ms

12j4tb5g5b.jpg

12j4tb5g5b.jpg

2025 ms

banner_jspp_nenkai57.png

banner_jspp_nenkai57.png

697 ms

banner_awards.png

banner_awards.png

954 ms

icon_information.png

icon_information.png

686 ms

qa_search.png

qa_search.png

1187 ms

icon_good.png

icon_good.png

871 ms

icon_gold.png

icon_gold.png

885 ms

icon_silver.png

icon_silver.png

1044 ms

icon_bronze.png

icon_bronze.png

1062 ms

icon_other.png

icon_other.png

1143 ms

twitter_hiroba.png

twitter_hiroba.png

1216 ms

bg_footer_shadow.png

bg_footer_shadow.png

1237 ms

footer_about_us.png

footer_about_us.png

1332 ms

footer_contents.png

footer_contents.png

1358 ms

banner_application.png

banner_application.png

1409 ms

banner_twitter.png

banner_twitter.png

1422 ms

banner_facebook.png

banner_facebook.png

1520 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1858 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

jspp.org accessibility score

69

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

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.

Best Practices

jspp.org 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

SEO Factors

jspp.org SEO score

82

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jspp.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Jspp.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

jspp.org

Open Graph data is detected on the main page of Jspp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: