Tools & Wizards About Us
player.ru screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

player.ru

Интернет-магазин, форум и барахолка по телефонам, планшетам, ноутбукам, плеерам, цифровым фотоаппаратам, автомобильным устройствам

Page Load Speed

6.8 sec in total

First Response

1.1 sec

Resources Loaded

3.3 sec

Page Rendered

2.4 sec

player.ru screenshot

About Website

Click here to check amazing Player content for Russia. Otherwise, check out these important facts you probably never knew about player.ru

Pleer.Ru - Плеер.Ру - Интернет-магазин, форум и барахолка по MP3 плеерам и цифровым фотоаппаратам

Visit player.ru

Key Findings

We analyzed Player.ru page load time and found that the first response time was 1.1 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

player.ru performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

player.ru

1053 ms

yuiloader-dom-event.js

30 ms

connection-min.js

20 ms

vbulletin-core.js

246 ms

css.php

575 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 90% of them (55 requests) were addressed to the original Player.ru, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Player.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.6 kB (31%)

Content Size

768.7 kB

After Optimization

529.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Player.ru main page is 768.7 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. 45% of websites need less resources to load. Images take 505.7 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 135.8 kB

  • Original 148.9 kB
  • After minification 111.7 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 37.2 kB, which is 25% 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 135.8 kB or 91% of the original size.

Image Optimization

-6%

Potential reduce by 28.9 kB

  • Original 505.7 kB
  • After minification 476.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. Player images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 74.9 kB

  • Original 114.0 kB
  • After minification 113.0 kB
  • After compression 39.1 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 74.9 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (63%)

Requests Now

60

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

player.ru

player.ru

1053 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

30 ms

connection-min.js

connection-min.js

20 ms

vbulletin-core.js

vbulletin-core.js

246 ms

css.php

css.php

575 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

241 ms

css.php

css.php

328 ms

css.php

css.php

452 ms

css.php

css.php

458 ms

vbulletin_md5.js

vbulletin_md5.js

361 ms

pagebg.gif

pagebg.gif

156 ms

logo.gif

logo.gif

262 ms

search.png

search.png

154 ms

navbit-home.png

navbit-home.png

133 ms

vkontakte.png

vkontakte.png

444 ms

facebook.png

facebook.png

444 ms

twitter.png

twitter.png

715 ms

googleplus.png

googleplus.png

523 ms

youtube.png

youtube.png

765 ms

livejour.png

livejour.png

869 ms

instagram.png

instagram.png

846 ms

collapse_40b.png

collapse_40b.png

525 ms

cat_description.gif

cat_description.gif

638 ms

forum_old_lock-48.png

forum_old_lock-48.png

639 ms

rss_40b.png

rss_40b.png

757 ms

icon6.png

icon6.png

761 ms

lastpost-right.png

lastpost-right.png

827 ms

profile.png

profile.png

869 ms

forum.png

forum.png

873 ms

icon1.png

icon1.png

876 ms

icon14.png

icon14.png

934 ms

icon3.png

icon3.png

949 ms

icon5.png

icon5.png

976 ms

subforum_old-48.png

subforum_old-48.png

983 ms

homepage.png

homepage.png

990 ms

poll_posticon.gif

poll_posticon.gif

994 ms

forum_link-48.png

forum_link-48.png

1050 ms

collapse_thead.png

collapse_thead.png

1069 ms

whos_online.gif

whos_online.gif

1100 ms

forum_new-48.png

forum_new-48.png

1102 ms

forum_old-48.png

forum_old-48.png

1110 ms

category_forum_old.png

category_forum_old.png

1115 ms

all.js

all.js

305 ms

header_bg.gif

header_bg.gif

1166 ms

gradient_tcat.gif

gradient_tcat.gif

1077 ms

menu_open.gif

menu_open.gif

1090 ms

bottom1.gif

bottom1.gif

1087 ms

blc1.gif

blc1.gif

1097 ms

brc1.gif

brc1.gif

1103 ms

gradient_thead.gif

gradient_thead.gif

1071 ms

analytics.js

analytics.js

22 ms

top_center.gif

top_center.gif

1047 ms

collect

collect

119 ms

top_left.gif

top_left.gif

916 ms

top_right.gif

top_right.gif

907 ms

xd_arbiter.php

xd_arbiter.php

220 ms

top_bg.gif

top_bg.gif

846 ms

top_end.gif

top_end.gif

853 ms

bottom.gif

bottom.gif

778 ms

blc.gif

blc.gif

804 ms

brc.gif

brc.gif

762 ms

Accessibility Review

player.ru accessibility score

65

Accessibility Issues

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

High

Some elements have a [tabindex] value greater than 0

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

<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

Best Practices

player.ru 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

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

player.ru SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Player.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Player.ru main page’s claimed encoding is windows-1251. 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

player.ru

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