Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

jlesc.github.io

JLESC — Joint Laboratory on Extreme Scale Computing

Page Load Speed

516 ms in total

First Response

14 ms

Resources Loaded

274 ms

Page Rendered

228 ms

jlesc.github.io screenshot

About Website

Click here to check amazing JLESC Github content for China. Otherwise, check out these important facts you probably never knew about jlesc.github.io

Advance is a multi-purpose premium Jekyll theme. Modern design, clean code and highly configurable.

Visit jlesc.github.io

Key Findings

We analyzed Jlesc.github.io page load time and found that the first response time was 14 ms and then it took 502 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

jlesc.github.io performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

jlesc.github.io

14 ms

jlesc.github.io

32 ms

main.css

22 ms

css2

43 ms

popper.min.js

63 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 71% of them (20 requests) were addressed to the original Jlesc.github.io, 21% (6 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (113 ms) belongs to the original domain Jlesc.github.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.5 kB (27%)

Content Size

412.8 kB

After Optimization

303.3 kB

In fact, the total size of Jlesc.github.io main page is 412.8 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. 60% of websites need less resources to load. Images take 395.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 14.1 kB

  • Original 17.7 kB
  • After minification 14.1 kB
  • After compression 3.6 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 3.7 kB, which is 21% 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 14.1 kB or 79% of the original size.

Image Optimization

-24%

Potential reduce by 95.4 kB

  • Original 395.1 kB
  • After minification 299.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, JLESC Github needs image optimization as it can save up to 95.4 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

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

Accessibility Review

jlesc.github.io accessibility score

100

Accessibility Issues

Best Practices

jlesc.github.io best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jlesc.github.io SEO score

92

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

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 Jlesc.github.io 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 Jlesc.github.io 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

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