Tools & Wizards About Us
prologin.org screenshot

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

prologin.org

Prologin, the French National Computer Science Contest

Page Load Speed

2.8 sec in total

First Response

213 ms

Resources Loaded

1.5 sec

Page Rendered

1.1 sec

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 213 ms and then it took 2.6 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

prologin.org performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

prologin.org

213 ms

prologin.org

486 ms

css

33 ms

bootstrap.min.css

163 ms

font-awesome.min.css

242 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 91% of them (32 requests) were addressed to the original Prologin.org, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (731 ms) belongs to the original domain Prologin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.7 kB (11%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 17.9 kB

  • Original 23.4 kB
  • After minification 20.4 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 13% 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.9 kB or 76% of the original size.

Image Optimization

-9%

Potential reduce by 90.9 kB

  • Original 1.0 MB
  • After minification 931.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. Prologin images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 6.9 kB

  • Original 47.2 kB
  • After minification 47.2 kB
  • After compression 40.4 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 6.9 kB or 15% of the original size.

CSS Optimization

-19%

Potential reduce by 8.0 kB

  • Original 41.8 kB
  • After minification 41.8 kB
  • After compression 33.8 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 8.0 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (13%)

Requests Now

30

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 30 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prologin.org

prologin.org

213 ms

prologin.org

prologin.org

486 ms

css

css

33 ms

bootstrap.min.css

bootstrap.min.css

163 ms

font-awesome.min.css

font-awesome.min.css

242 ms

prologin.css

prologin.css

244 ms

homepage.css

homepage.css

246 ms

jquery.min.js

jquery.min.js

377 ms

bootstrap.min.js

bootstrap.min.js

374 ms

logo_cube.png

logo_cube.png

375 ms

6dcdc6fd189045dd5265fbee127d9f5e5583d7c2.png

6dcdc6fd189045dd5265fbee127d9f5e5583d7c2.png

374 ms

1b22aaa0323f71dad8085540b96eceef2bcd8c45.jpg

1b22aaa0323f71dad8085540b96eceef2bcd8c45.jpg

403 ms

88e29051d73a14332ec3076764c4a49ade8fc085.png

88e29051d73a14332ec3076764c4a49ade8fc085.png

480 ms

a02386a0b2e6c239e9132eadf74cbff629443ffd.png

a02386a0b2e6c239e9132eadf74cbff629443ffd.png

511 ms

bfc2a81963e9ef43d7cb10d2ae30bd68b1c54b1f.png

bfc2a81963e9ef43d7cb10d2ae30bd68b1c54b1f.png

519 ms

2648282ace02ece35efabf006cb51a2f368c7b7b.png

2648282ace02ece35efabf006cb51a2f368c7b7b.png

403 ms

13204c3a38553464549ab1c9513cb6dd044aa4bf.png

13204c3a38553464549ab1c9513cb6dd044aa4bf.png

410 ms

6e074998eeab7ec921d3862dc87d0f754439dc5a.png

6e074998eeab7ec921d3862dc87d0f754439dc5a.png

484 ms

4b729dc96f98345e57266e7759d901aa2040222b.png

4b729dc96f98345e57266e7759d901aa2040222b.png

483 ms

b9683cc8552adaa8e28f6c64511a06552989313a.png

b9683cc8552adaa8e28f6c64511a06552989313a.png

492 ms

fcffa883e61093b11886614b3d45ed4a1e3fd035.png

fcffa883e61093b11886614b3d45ed4a1e3fd035.png

561 ms

7f1b55815807fbf43b1d308b15072fc5e9ff9f92.png

7f1b55815807fbf43b1d308b15072fc5e9ff9f92.png

646 ms

f4a5a1c3c1804e4be32077ace22f83612c149b18.jpg

f4a5a1c3c1804e4be32077ace22f83612c149b18.jpg

649 ms

0d3d30393dee3c8a6d38bed001e603bc8bba38e0.png

0d3d30393dee3c8a6d38bed001e603bc8bba38e0.png

731 ms

ee879479e66edc9f829f13f08a0593510f6c166a.png

ee879479e66edc9f829f13f08a0593510f6c166a.png

596 ms

f81f765dde8c6a0cca553a90498d5ab8c0b8aa63.png

f81f765dde8c6a0cca553a90498d5ab8c0b8aa63.png

689 ms

c81f5de8ef0c60884faf9e46473ef07fadcefe82.png

c81f5de8ef0c60884faf9e46473ef07fadcefe82.png

644 ms

2298e2b40353b5f057f9817733d20d187854deb6.png

2298e2b40353b5f057f9817733d20d187854deb6.png

683 ms

discord.svg

discord.svg

727 ms

tiktok.svg

tiktok.svg

726 ms

small_cube.png

small_cube.png

469 ms

footer.png

footer.png

508 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

19 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

27 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

390 ms

Accessibility Review

prologin.org accessibility score

65

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

Image elements do not have [alt] attributes

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

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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: