Tools & Wizards About Us
pl4y.fr screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

pl4y.fr

Jeux vidéo : toute l'actualité en temps réel sur Pl4y.fr

Page Load Speed

2.6 sec in total

First Response

320 ms

Resources Loaded

2 sec

Page Rendered

332 ms

pl4y.fr screenshot

About Website

Visit pl4y.fr now to see the best up-to-date Pl4y content and also check out these interesting facts you probably never knew about pl4y.fr

L'actualité du jeu vidéo n'a plus aucun secret pour les joueurs que vous êtes grâce à Pl4y.fr, portail d'actu des jeux vidéo

Visit pl4y.fr

Key Findings

We analyzed Pl4y.fr page load time and found that the first response time was 320 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pl4y.fr performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

pl4y.fr

320 ms

www.pl4y.fr

456 ms

body.css

453 ms

plusone.js

52 ms

jsapi

18 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 60% of them (49 requests) were addressed to the original Pl4y.fr, 10% (8 requests) were made to Google.com and 7% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (653 ms) belongs to the original domain Pl4y.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.5 kB (30%)

Content Size

496.3 kB

After Optimization

347.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pl4y.fr main page is 496.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. 55% of websites need less resources to load. Images take 389.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 32.8 kB

  • Original 40.9 kB
  • After minification 37.0 kB
  • After compression 8.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. 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 32.8 kB or 80% of the original size.

Image Optimization

-23%

Potential reduce by 90.9 kB

  • Original 389.6 kB
  • After minification 298.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. Obviously, Pl4y needs image optimization as it can save up to 90.9 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 15.4 kB

  • Original 54.7 kB
  • After minification 52.6 kB
  • After compression 39.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 15.4 kB or 28% of the original size.

CSS Optimization

-84%

Potential reduce by 9.4 kB

  • Original 11.2 kB
  • After minification 9.1 kB
  • After compression 1.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. Pl4y.fr needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (22%)

Requests Now

77

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pl4y.fr

pl4y.fr

320 ms

www.pl4y.fr

www.pl4y.fr

456 ms

body.css

body.css

453 ms

plusone.js

plusone.js

52 ms

jsapi

jsapi

18 ms

t13n

t13n

28 ms

brand

brand

25 ms

show_ads.js

show_ads.js

8 ms

brand

brand

47 ms

t13n

t13n

41 ms

cookiechoices.js

cookiechoices.js

82 ms

bg.png

bg.png

112 ms

play-logo.png

play-logo.png

112 ms

connexion.png

connexion.png

204 ms

inscription.png

inscription.png

243 ms

rss.png

rss.png

244 ms

facebook.png

facebook.png

242 ms

twitter.png

twitter.png

241 ms

google+.png

google+.png

201 ms

youtube.png

youtube.png

282 ms

publier.png

publier.png

283 ms

hot.png

hot.png

283 ms

arrow.png

arrow.png

283 ms

2-1438191591.jpg

2-1438191591.jpg

282 ms

2-1434018084.jpg

2-1434018084.jpg

281 ms

2-1412111089.jpg

2-1412111089.jpg

352 ms

2-1411666242.jpg

2-1411666242.jpg

352 ms

2-1410205351.jpg

2-1410205351.jpg

353 ms

pub.jpg

pub.jpg

424 ms

logo_news.png

logo_news.png

353 ms

2-1408572024.jpg

2-1408572024.jpg

353 ms

2-1407680452.jpg

2-1407680452.jpg

423 ms

2-1407669845.jpg

2-1407669845.jpg

501 ms

2-1407157419.png

2-1407157419.png

424 ms

2-1407147407.jpg

2-1407147407.jpg

425 ms

2-1407146994.png

2-1407146994.png

426 ms

2-1405246423.jpg

2-1405246423.jpg

501 ms

56-1405192211.jpg

56-1405192211.jpg

499 ms

56-1405020739.jpg

56-1405020739.jpg

501 ms

2-1404153061.jpg

2-1404153061.jpg

502 ms

2-1404078044.jpg

2-1404078044.jpg

502 ms

2-1403724688.jpg

2-1403724688.jpg

588 ms

56-1403638231.jpg

56-1403638231.jpg

587 ms

2-1383685416.jpg

2-1383685416.jpg

653 ms

PS4.png

PS4.png

588 ms

XBONE.png

XBONE.png

587 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

PC.png

PC.png

573 ms

29 ms

transliteration.css

transliteration.css

2 ms

transliteration.I.js

transliteration.I.js

8 ms

27 ms

ca-pub-2536182992932364.js

ca-pub-2536182992932364.js

140 ms

zrt_lookup.html

zrt_lookup.html

141 ms

show_ads_impl.js

show_ads_impl.js

97 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

135 ms

PS3.png

PS3.png

560 ms

XB360.png

XB360.png

548 ms

inputtools.js

inputtools.js

14 ms

ga.js

ga.js

36 ms

__utm.gif

__utm.gif

59 ms

Wii.png

Wii.png

467 ms

ads

ads

178 ms

PSP.png

PSP.png

431 ms

DS.png

DS.png

429 ms

Mobile.png

Mobile.png

500 ms

Vita.png

Vita.png

502 ms

WiiU.png

WiiU.png

503 ms

osd.js

osd.js

13 ms

ads

ads

243 ms

ads

ads

209 ms

ads

ads

206 ms

boutique.jpg

boutique.jpg

537 ms

css

css

54 ms

m_js_controller.js

m_js_controller.js

24 ms

abg.js

abg.js

30 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

33 ms

s

s

23 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

30 ms

x_button_blue2.png

x_button_blue2.png

7 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

16 ms

Accessibility Review

pl4y.fr accessibility score

60

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-*] attributes do not match their roles

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

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

pl4y.fr best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

pl4y.fr SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pl4y.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Pl4y.fr main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pl4y.fr

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