Tools & Wizards About Us
en.geny.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

en.geny.com

GENY : rapports, résultats PMU et pronostics des courses

Page Load Speed

1.9 sec in total

First Response

163 ms

Resources Loaded

1.5 sec

Page Rendered

279 ms

en.geny.com screenshot

About Website

Visit en.geny.com now to see the best up-to-date En GENY content for France and also check out these interesting facts you probably never knew about en.geny.com

With GENYcourses prepare your bets, find the parties, pronostics, interviews, ratings PMU, the results of Quinte and the results and reports from all races, provincial and PMU.

Visit en.geny.com

Key Findings

We analyzed En.geny.com page load time and found that the first response time was 163 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

en.geny.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value17.5 s

0/100

10%

TBT (Total Blocking Time)

Value5,090 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value43.0 s

0/100

10%

Network Requests Diagram

en.geny.com

163 ms

reset-fonts-grids.css

165 ms

container.css

309 ms

geny.4.27.css

200 ms

diaporama.css

213 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original En.geny.com, 71% (47 requests) were made to Static.geny.com and 6% (4 requests) were made to Media.geny.com. The less responsive or slowest element that took the longest time to load (687 ms) relates to the external source Static.geny.com.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of En.geny.com main page is 2.9 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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 145.5 kB

  • Original 174.4 kB
  • After minification 164.4 kB
  • After compression 28.8 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 145.5 kB or 83% of the original size.

Image Optimization

-24%

Potential reduce by 534.6 kB

  • Original 2.2 MB
  • After minification 1.7 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. Obviously, En GENY needs image optimization as it can save up to 534.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 54.5 kB

  • Original 483.8 kB
  • After minification 479.0 kB
  • After compression 429.3 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 54.5 kB or 11% of the original size.

CSS Optimization

-81%

Potential reduce by 54.7 kB

  • Original 67.2 kB
  • After minification 54.7 kB
  • After compression 12.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. En.geny.com needs all CSS files to be minified and compressed as it can save up to 54.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (51%)

Requests Now

65

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.geny.com

en.geny.com

163 ms

reset-fonts-grids.css

reset-fonts-grids.css

165 ms

container.css

container.css

309 ms

geny.4.27.css

geny.4.27.css

200 ms

diaporama.css

diaporama.css

213 ms

akcelo.css

akcelo.css

316 ms

swiper-bundle.min.css

swiper-bundle.min.css

42 ms

calendar.js

calendar.js

314 ms

user.4.27.js

user.4.27.js

195 ms

diaporama.4.26.js

diaporama.4.26.js

332 ms

htmlParser.js

htmlParser.js

219 ms

postscribe.js

postscribe.js

234 ms

jquery.min.js

jquery.min.js

243 ms

swiper-bundle.min.js

swiper-bundle.min.js

50 ms

swiper.min.js

swiper.min.js

74 ms

outbrain.js

outbrain.js

158 ms

geny

geny

124 ms

slm.prebid.geny.js

slm.prebid.geny.js

645 ms

restpwd.css

restpwd.css

246 ms

loader.js

loader.js

289 ms

gtm.js

gtm.js

81 ms

photo_arrivee_small_1494206.jpg

photo_arrivee_small_1494206.jpg

194 ms

catalog-cover-icon.png

catalog-cover-icon.png

263 ms

prono_image_4568227.jpg

prono_image_4568227.jpg

223 ms

centpourcentquinte_1494255.png

centpourcentquinte_1494255.png

261 ms

photo_arrivee_small_1494204.jpg

photo_arrivee_small_1494204.jpg

246 ms

Geny_logo.svg

Geny_logo.svg

28 ms

search-icon.png

search-icon.png

29 ms

visible.png

visible.png

23 ms

font.gif

font.gif

29 ms

font-plus.gif

font-plus.gif

37 ms

print.gif

print.gif

40 ms

uk.gif

uk.gif

36 ms

fr.gif

fr.gif

44 ms

de.gif

de.gif

37 ms

sct2tqqm_01.gif

sct2tqqm_01.gif

166 ms

simple.svg

simple.svg

61 ms

couple.svg

couple.svg

53 ms

couple_ordre.svg

couple_ordre.svg

71 ms

2sur4.svg

2sur4.svg

73 ms

trio.svg

trio.svg

79 ms

trio_ordre.svg

trio_ordre.svg

195 ms

top4.svg

top4.svg

76 ms

super_top5.svg

super_top5.svg

219 ms

live.jpg

live.jpg

407 ms

hd-quintenet.gif

hd-quintenet.gif

248 ms

hd-course.gif

hd-course.gif

250 ms

feed-icon.gif

feed-icon.gif

306 ms

promo-genybet.webp

promo-genybet.webp

404 ms

logo-18.png

logo-18.png

260 ms

jeu_resp.png

jeu_resp.png

262 ms

entete_bg.gif

entete_bg.gif

257 ms

entete.gif

entete.gif

399 ms

background.gif

background.gif

262 ms

btnFB.svg

btnFB.svg

334 ms

btnX.svg

btnX.svg

411 ms

btnINSTA.svg

btnINSTA.svg

449 ms

btnTT.svg

btnTT.svg

412 ms

btnYT.svg

btnYT.svg

687 ms

iframe_api

iframe_api

62 ms

www-widgetapi.js

www-widgetapi.js

5 ms

rss.xml

rss.xml

188 ms

sdk.f9618f70abd5481bf060e9734fd600c29ee26e25.js

sdk.f9618f70abd5481bf060e9734fd600c29ee26e25.js

25 ms

ui-gdpr-en-web.f9618f70abd5481bf060e9734fd600c29ee26e25.js

ui-gdpr-en-web.f9618f70abd5481bf060e9734fd600c29ee26e25.js

241 ms

genyLarge.css

genyLarge.css

82 ms

logo.png

logo.png

42 ms

Accessibility Review

en.geny.com accessibility score

76

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

en.geny.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

en.geny.com 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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.geny.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that En.geny.com 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

en.geny.com

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