Access rolandgarros.com. Roland-Garros

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value15.6 s

0/100

10%

TBT (Total Blocking Time)

Value17,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value30.6 s

0/100

10%

rolandgarros.com

248 ms

www.rolandgarros.com

287 ms

index.html

1136 ms

jquery.js

675 ms

eventsCore-min.js

1242 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 87% of them (104 requests) were addressed to the original Rolandgarros.com, 3% (3 requests) were made to Staticxx.facebook.com and 2% (2 requests) were made to Aka-cdn-ns.adtech.de. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Rolandgarros.com.

Content Size

8.0 MB

After Optimization

6.3 MB

In fact, the total size of Rolandgarros.com main page is 8.0 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. 85% 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 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 106.9 kB

Original 127.4 kB
After minification 127.4 kB
After compression 20.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. 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 106.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 252.9 kB

Original 6.1 MB
After minification 5.8 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. Roland Garros images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 884.8 kB

Original 1.3 MB
After minification 1.2 MB
After compression 379.9 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 884.8 kB or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 443.2 kB

Original 502.3 kB
After minification 459.5 kB
After compression 59.2 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. Rolandgarros.com needs all CSS files to be minified and compressed as it can save up to 443.2 kB or 88% of the original size.

Requests Now

110

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

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

High

[lang] attributes do not have a valid value

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links do not have descriptive text

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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 Rolandgarros.com 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 Rolandgarros.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

rolandgarros.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Roland-Garros - The official site

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

rolandgarros.com

www.rolandgarros.com

index.html

jquery.js

eventsCore-min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

rolandgarros.com

www.rolandgarros.com

index.html

jquery.js

eventsCore-min.js

eventsCorePlayer.js

RGCore.js

jquery-ui.js

global.js

jquery.cookie.js

rg.js

globalConfig.js

masonry.pkgd.min.js

mosaic.js

CSSpie.js

jquery.carouFredSel.js

jquery.nicescroll.min.js

jquery.throttle_debounce.min.js

jquery.mousewheel.js

jquery.touchSwipe.js

translation_en_FR.js

jquery.unveil.min.js

live_blog.js

shop.js

header_poc.js

bannerTitleController.js

related_content.js

AppMeasurement.js

globalMeasure.js

videoPreroll_videos_en.js

videoOverlay2.js

modernizr-1.7.min.js

html5inlineVideo.js

inlineVideo.js

swfobject.js

flashdetect.js

videoSub.js

DACLoader.js

global.css

rg.css

overlayHeader.css

videoCarouselFormatting.css

videoOverlayFormatting.css