Tools & Wizards About Us
prologin.org screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

prologin.org

Prologin, the French National Computer Science Contest

Page Load Speed

2 sec in total

First Response

365 ms

Resources Loaded

1.4 sec

Page Rendered

176 ms

prologin.org screenshot

About Website

Click here to check amazing Prologin content for France. Otherwise, check out these important facts you probably never knew about prologin.org

Prologin is a computer science contest. Our goal is to introduce students to the world of programming and algorithms by subjecting them to several conventional problems and exciting challenges.

Visit prologin.org

Key Findings

We analyzed Prologin.org page load time and found that the first response time was 365 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

prologin.org performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

prologin.org

365 ms

prologin.org

499 ms

css

60 ms

bootstrap.min.css

167 ms

font-awesome.min.css

258 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Prologin.org, 12% (4 requests) were made to F.vimeocdn.com and 6% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (504 ms) belongs to the original domain Prologin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 580.8 kB (62%)

Content Size

935.3 kB

After Optimization

354.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prologin.org main page is 935.3 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. 40% of websites need less resources to load. Javascripts take 483.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.0 kB

  • Original 22.5 kB
  • After minification 18.9 kB
  • After compression 5.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.6 kB, which is 16% 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 17.0 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 6.4 kB

  • Original 143.0 kB
  • After minification 136.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. Prologin images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 314.8 kB

  • Original 483.5 kB
  • After minification 483.5 kB
  • After compression 168.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 314.8 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 242.6 kB

  • Original 286.3 kB
  • After minification 281.7 kB
  • After compression 43.7 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. Prologin.org needs all CSS files to be minified and compressed as it can save up to 242.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (34%)

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prologin.org

prologin.org

365 ms

prologin.org

prologin.org

499 ms

css

css

60 ms

bootstrap.min.css

bootstrap.min.css

167 ms

font-awesome.min.css

font-awesome.min.css

258 ms

prologin.css

prologin.css

263 ms

homepage.css

homepage.css

268 ms

logo_cube.png

logo_cube.png

326 ms

bdb3ff91f10a5be82af63aaab365651e971cfdf8.png

bdb3ff91f10a5be82af63aaab365651e971cfdf8.png

326 ms

155a81aaf6a7ef9dcc34bd8eb4fb9778d4960fe5.png

155a81aaf6a7ef9dcc34bd8eb4fb9778d4960fe5.png

324 ms

aa55f65d0bc0b6fd83c8c74e4143c94b436fea14.png

aa55f65d0bc0b6fd83c8c74e4143c94b436fea14.png

336 ms

69a602c21999907caccf2673c275170ea315c2ec.jpg

69a602c21999907caccf2673c275170ea315c2ec.jpg

413 ms

58f72c52277692bb0eea15a75929ffc3db3c92d4.png

58f72c52277692bb0eea15a75929ffc3db3c92d4.png

345 ms

57d0a283688c1208fcc924f2bd3cf672f37a98f1.jpg

57d0a283688c1208fcc924f2bd3cf672f37a98f1.jpg

401 ms

cc09ae6fd5567d3ee1675c375cd2a97762a2396b.jpg

cc09ae6fd5567d3ee1675c375cd2a97762a2396b.jpg

402 ms

cdc6e8a56aec347e819c57766654cd9a49b8f13d.png

cdc6e8a56aec347e819c57766654cd9a49b8f13d.png

482 ms

90b3d5a25d87f99cc93700fea2d3983c2b29dfda.png

90b3d5a25d87f99cc93700fea2d3983c2b29dfda.png

415 ms

134342417

134342417

72 ms

jquery.min.js

jquery.min.js

504 ms

bootstrap.min.js

bootstrap.min.js

478 ms

player.js

player.js

111 ms

player.css

player.css

97 ms

ga.js

ga.js

58 ms

vuid.min.js

vuid.min.js

95 ms

__utm.gif

__utm.gif

26 ms

proxy.html

proxy.html

51 ms

10479783_60x60.jpg

10479783_60x60.jpg

158 ms

small_cube.png

small_cube.png

207 ms

footer.png

footer.png

216 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

25 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

33 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

257 ms

analytics.js

analytics.js

26 ms

collect

collect

14 ms

Accessibility Review

prologin.org accessibility score

78

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

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

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

prologin.org SEO score

90

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

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

prologin.org

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