Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 58

    SEO

    Google-friendlier than
    30% of websites

pepere.org

Flash games - Java games

Page Load Speed

33.6 sec in total

First Response

1.5 sec

Resources Loaded

18.3 sec

Page Rendered

13.9 sec

pepere.org screenshot

About Website

Visit pepere.org now to see the best up-to-date Pepere content for Russia and also check out these interesting facts you probably never knew about pepere.org

Welcome to «Annuaire pépère». This is a directory of online flash games selected by Pépère for their quality and their simplicity. It is translated in many languages owing to many net surfers who like...

Visit pepere.org

Key Findings

We analyzed Pepere.org page load time and found that the first response time was 1.5 sec and then it took 32.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

pepere.org performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value1.874

0/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

1457 ms

pepere.css

354 ms

urchin.js

327 ms

brand

1240 ms

show_ads.js

265 ms

Our browser made a total of 224 requests to load all elements on the main page. We found that 93% of them (209 requests) were addressed to the original Pepere.org, 2% (4 requests) were made to Pagead2.googlesyndication.com and 2% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 535.6 kB (59%)

Content Size

905.2 kB

After Optimization

369.5 kB

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

HTML Optimization

-82%

Potential reduce by 49.3 kB

  • Original 60.0 kB
  • After minification 59.7 kB
  • After compression 10.7 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 49.3 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 8.8 kB

  • Original 148.7 kB
  • After minification 139.8 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. Pepere images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 471.8 kB

  • Original 689.5 kB
  • After minification 685.2 kB
  • After compression 217.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 471.8 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 5.7 kB

  • Original 7.0 kB
  • After minification 6.1 kB
  • After compression 1.3 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. Pepere.org needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

93

After Optimization

42

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

Accessibility Review

pepere.org accessibility score

61

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

pepere.org best practices score

75

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

SEO Factors

pepere.org SEO score

58

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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