Tools & Wizards About Us
alphaville.github.io screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

alphaville.github.io

Pantelis Sopasakis: publications, teaching and more

Page Load Speed

2.5 sec in total

First Response

15 ms

Resources Loaded

1.5 sec

Page Rendered

1 sec

alphaville.github.io screenshot

About Website

Welcome to alphaville.github.io homepage info - get ready to check Alphaville Github best content for China right away, or after learning these important things about alphaville.github.io

Personal web page of Pantelis Sopasakis. I am a researcher in the field of applied mathematics, control theory, numerical optimisation and applications to next-generation autonomous cyberphysical syst...

Visit alphaville.github.io

Key Findings

We analyzed Alphaville.github.io page load time and found that the first response time was 15 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

alphaville.github.io performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value3,580 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

alphaville.github.io

15 ms

alphaville.github.io

40 ms

MathJax.js

54 ms

default.css

35 ms

layout.css

18 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 61% of them (44 requests) were addressed to the original Alphaville.github.io, 10% (7 requests) were made to Cdn.rawgit.com and 10% (7 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (643 ms) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.4 kB (8%)

Content Size

956.0 kB

After Optimization

883.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alphaville.github.io main page is 956.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 618.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 69.9 kB

  • Original 86.0 kB
  • After minification 57.8 kB
  • After compression 16.1 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 28.2 kB, which is 33% 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 69.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 618.9 kB
  • After minification 618.9 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. Alphaville Github images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.5 kB

  • Original 192.2 kB
  • After minification 192.2 kB
  • After compression 189.7 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 0 B

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 58.9 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. Alphaville.github.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (57%)

Requests Now

53

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alphaville 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 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

alphaville.github.io

alphaville.github.io

15 ms

alphaville.github.io

alphaville.github.io

40 ms

MathJax.js

MathJax.js

54 ms

default.css

default.css

35 ms

layout.css

layout.css

18 ms

media-queries.css

media-queries.css

17 ms

magnific-popup.css

magnific-popup.css

19 ms

vex.css

vex.css

18 ms

vex-theme-flat-attack.css

vex-theme-flat-attack.css

42 ms

vex.combined.min.js

vex.combined.min.js

26 ms

modernizr.js

modernizr.js

30 ms

bibtexParse.min.js

bibtexParse.min.js

42 ms

jquery.min.js

jquery.min.js

30 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

30 ms

jquery.flexslider.js

jquery.flexslider.js

50 ms

waypoints.js

waypoints.js

42 ms

jquery.fittext.js

jquery.fittext.js

38 ms

magnific-popup.js

magnific-popup.js

45 ms

init.min.js

init.min.js

59 ms

MathJax.js

MathJax.js

19 ms

fonts.css

fonts.css

25 ms

fontello.css

fontello.css

28 ms

font-awesome.min.css

font-awesome.min.css

25 ms

UlEj1UIEPnw

UlEj1UIEPnw

255 ms

E4vCSJw97FQ

E4vCSJw97FQ

643 ms

header-background.jpg

header-background.jpg

27 ms

p_sopasakis_900.png

p_sopasakis_900.png

23 ms

optimization.jpg

optimization.jpg

27 ms

mpc.jpg

mpc.jpg

53 ms

bio.jpg

bio.jpg

43 ms

applications.jpg

applications.jpg

22 ms

geometry.jpg

geometry.jpg

35 ms

overlay-bg.png

overlay-bg.png

34 ms

risk.jpg

risk.jpg

37 ms

GPU.jpg

GPU.jpg

43 ms

robo.jpg

robo.jpg

45 ms

signal.jpg

signal.jpg

47 ms

jaqpot.jpg

jaqpot.jpg

54 ms

water.jpg

water.jpg

55 ms

testimonials-bg.jpg

testimonials-bg.jpg

68 ms

config.js

config.js

43 ms

config.js

config.js

38 ms

tex2jax.js

tex2jax.js

41 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

64 ms

OpenSans-Bold-webfont.svg

OpenSans-Bold-webfont.svg

66 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

65 ms

librebaskerville-regular-webfont.woff

librebaskerville-regular-webfont.woff

77 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

76 ms

fontello.woff

fontello.woff

75 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

76 ms

OpenSans-Italic-webfont.woff

OpenSans-Italic-webfont.woff

77 ms

librebaskerville-italic-webfont.woff

librebaskerville-italic-webfont.woff

77 ms

config.js

config.js

6 ms

tex2jax.js

tex2jax.js

9 ms

config.js

config.js

10 ms

jax.js

jax.js

622 ms

jax.js

jax.js

624 ms

jax.js

jax.js

69 ms

www-player.css

www-player.css

18 ms

www-embed-player.js

www-embed-player.js

46 ms

base.js

base.js

84 ms

jax.js

jax.js

553 ms

ad_status.js

ad_status.js

372 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

251 ms

embed.js

embed.js

144 ms

jax.js

jax.js

324 ms

jax.js

jax.js

95 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

77 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

212 ms

id

id

50 ms

Create

Create

154 ms

Create

Create

156 ms

Accessibility Review

alphaville.github.io accessibility score

73

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-hidden="true"] elements contain focusable descendents

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.

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

<frame> or <iframe> elements do not have a title

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

alphaville.github.io SEO score

84

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

alphaville.github.io

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