Tools & Wizards About Us
playcds.com.br screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

playcds.com.br

playcds.com.br – Just another WordPress site

Page Load Speed

4.2 sec in total

First Response

283 ms

Resources Loaded

3.7 sec

Page Rendered

228 ms

playcds.com.br screenshot

About Website

Click here to check amazing Playcds content for Brazil. Otherwise, check out these important facts you probably never knew about playcds.com.br

Visit playcds.com.br

Key Findings

We analyzed Playcds.com.br page load time and found that the first response time was 283 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

playcds.com.br performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

playcds.com.br

283 ms

all.js

350 ms

adsbygoogle.js

12 ms

widgets.js

133 ms

backlogo.jpg

132 ms

Our browser made a total of 200 requests to load all elements on the main page. We found that 40% of them (79 requests) were addressed to the original Playcds.com.br, 12% (24 requests) were made to I1.ytimg.com and 10% (19 requests) were made to Um.simpli.fi. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Sync1.intentiq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 396.7 kB (24%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-82%

Potential reduce by 54.8 kB

  • Original 66.6 kB
  • After minification 65.1 kB
  • After compression 11.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 54.8 kB or 82% of the original size.

Image Optimization

-21%

Potential reduce by 328.2 kB

  • Original 1.6 MB
  • After minification 1.2 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, Playcds needs image optimization as it can save up to 328.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 13.6 kB

  • Original 26.0 kB
  • After minification 25.9 kB
  • After compression 12.5 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 13.6 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (31%)

Requests Now

168

After Optimization

116

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

playcds.com.br

playcds.com.br

283 ms

all.js

all.js

350 ms

adsbygoogle.js

adsbygoogle.js

12 ms

widgets.js

widgets.js

133 ms

backlogo.jpg

backlogo.jpg

132 ms

logo.png

logo.png

177 ms

plusone.js

plusone.js

140 ms

thumb.php

thumb.php

400 ms

thumb.php

thumb.php

396 ms

thumb.php

thumb.php

424 ms

thumb.php

thumb.php

425 ms

thumb.php

thumb.php

395 ms

thumb.php

thumb.php

423 ms

thumb.php

thumb.php

470 ms

thumb.php

thumb.php

464 ms

thumb.php

thumb.php

472 ms

thumb.php

thumb.php

464 ms

thumb.php

thumb.php

484 ms

thumb.php

thumb.php

470 ms

thumb.php

thumb.php

511 ms

thumb.php

thumb.php

518 ms

thumb.php

thumb.php

525 ms

thumb.php

thumb.php

511 ms

thumb.php

thumb.php

526 ms

atual.jpg

atual.jpg

119 ms

ca-pub-6947229958070047.js

ca-pub-6947229958070047.js

114 ms

zrt_lookup.html

zrt_lookup.html

106 ms

show_ads_impl.js

show_ads_impl.js

56 ms

thumb.php

thumb.php

531 ms

thumb.php

thumb.php

542 ms

thumb.php

thumb.php

546 ms

thumb.php

thumb.php

535 ms

thumb.php

thumb.php

553 ms

thumb.php

thumb.php

555 ms

thumb.php

thumb.php

587 ms

thumb.php

thumb.php

608 ms

thumb.php

thumb.php

601 ms

thumb.php

thumb.php

605 ms

thumb.php

thumb.php

610 ms

thumb.php

thumb.php

616 ms

thumb.php

thumb.php

653 ms

thumb.php

thumb.php

692 ms

thumb.php

thumb.php

688 ms

thumb.php

thumb.php

693 ms

thumb.php

thumb.php

691 ms

thumb.php

thumb.php

699 ms

thumb.php

thumb.php

715 ms

topartistas.jpg

topartistas.jpg

74 ms

cdsmais.jpg

cdsmais.jpg

78 ms

ultimosvideos.jpg

ultimosvideos.jpg

118 ms

default.jpg

default.jpg

74 ms

button.php

button.php

281 ms

small.js

small.js

175 ms

default.jpg

default.jpg

69 ms

default.jpg

default.jpg

72 ms

default.jpg

default.jpg

70 ms

default.jpg

default.jpg

73 ms

default.jpg

default.jpg

73 ms

default.jpg

default.jpg

71 ms

default.jpg

default.jpg

74 ms

default.jpg

default.jpg

75 ms

default.jpg

default.jpg

75 ms

default.jpg

default.jpg

76 ms

default.jpg

default.jpg

77 ms

default.jpg

default.jpg

77 ms

default.jpg

default.jpg

78 ms

default.jpg

default.jpg

108 ms

default.jpg

default.jpg

108 ms

default.jpg

default.jpg

109 ms

default.jpg

default.jpg

111 ms

default.jpg

default.jpg

111 ms

default.jpg

default.jpg

109 ms

default.jpg

default.jpg

111 ms

default.jpg

default.jpg

111 ms

default.jpg

default.jpg

112 ms

default.jpg

default.jpg

112 ms

ads

ads

284 ms

osd.js

osd.js

38 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

71 ms

fastbutton

fastbutton

160 ms

ads

ads

280 ms

78 ms

104 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

235 ms

postmessageRelay

postmessageRelay

155 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

111 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

106 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

174 ms

dpx.js

dpx.js

72 ms

tc.js

tc.js

74 ms

thumb.php

thumb.php

409 ms

thumb.php

thumb.php

415 ms

thumb.php

thumb.php

384 ms

thumb.php

thumb.php

385 ms

thumb.php

thumb.php

386 ms

api.js

api.js

80 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

127 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

98 ms

thumb.php

thumb.php

395 ms

tpid=1DE7044557F7D4561B034135021AF5D9

tpid=1DE7044557F7D4561B034135021AF5D9

54 ms

82 ms

p

p

65 ms

p

p

118 ms

thumb.php

thumb.php

404 ms

thumb.php

thumb.php

417 ms

thumb.php

thumb.php

417 ms

thumb.php

thumb.php

404 ms

xd_arbiter.php

xd_arbiter.php

227 ms

xd_arbiter.php

xd_arbiter.php

435 ms

thumb.php

thumb.php

404 ms

thumb.php

thumb.php

403 ms

tweet_button.6a78875565a912489e9aef879c881358.pt.html

tweet_button.6a78875565a912489e9aef879c881358.pt.html

49 ms

dpx

dpx

5 ms

thumb.php

thumb.php

436 ms

thumb.php

thumb.php

432 ms

match_redirect

match_redirect

6 ms

thumb.php

thumb.php

489 ms

thumb.php

thumb.php

533 ms

thumb.php

thumb.php

450 ms

29931

29931

19 ms

thumb.php

thumb.php

390 ms

match_redirect

match_redirect

3 ms

tpid=CE29559E57F7D456A223203802EEC27B

tpid=CE29559E57F7D456A223203802EEC27B

5 ms

thumb.php

thumb.php

435 ms

lr

lr

4 ms

thumb.php

thumb.php

431 ms

thumb.php

thumb.php

461 ms

thumb.php

thumb.php

453 ms

thumb.php

thumb.php

503 ms

v2

v2

54 ms

thumb.php

thumb.php

453 ms

thumb.php

thumb.php

430 ms

thumb.php

thumb.php

464 ms

thumb.php

thumb.php

531 ms

thumb.php

thumb.php

484 ms

thumb.php

thumb.php

486 ms

jot

jot

105 ms

dpx

dpx

5 ms

27519

27519

43 ms

thumb.php

thumb.php

443 ms

lr.gif

lr.gif

25 ms

pixel

pixel

44 ms

generic

generic

35 ms

i.match

i.match

180 ms

xrefid.xgi

xrefid.xgi

13 ms

match_redirect

match_redirect

9 ms

thumb.php

thumb.php

429 ms

thumb.php

thumb.php

498 ms

thumb.php

thumb.php

465 ms

thumb.php

thumb.php

466 ms

sync

sync

11 ms

generic

generic

9 ms

2964

2964

21 ms

1407

1407

118 ms

thumb.php

thumb.php

466 ms

2981

2981

90 ms

5386

5386

19 ms

match_redirect

match_redirect

11 ms

2831

2831

112 ms

thumb.php

thumb.php

476 ms

CE29559E57F7D456A223203802EEC27B

CE29559E57F7D456A223203802EEC27B

37 ms

3085

3085

12 ms

4448

4448

18 ms

match_redirect

match_redirect

3 ms

ProfilesEngineServlet

ProfilesEngineServlet

60 ms

event

event

6 ms

1.png

1.png

31 ms

4470

4470

16 ms

52154.gif

52154.gif

7 ms

1.png

1.png

53 ms

ProfilesEngineServlet

ProfilesEngineServlet

2242 ms

i.match

i.match

95 ms

4229

4229

15 ms

match_redirect

match_redirect

4 ms

16 ms

27 ms

spotx_match

spotx_match

4 ms

19 ms

engine

engine

88 ms

fb_match

fb_match

4 ms

u.php

u.php

27 ms

an

an

4 ms

lj_match

lj_match

6 ms

cw_match

cw_match

6 ms

rtset

rtset

201 ms

rb_match

rb_match

3 ms

merge

merge

37 ms

ox_match

ox_match

3 ms

exelate

exelate

3 ms

sd

sd

5 ms

pm_match

pm_match

4 ms

Pug

Pug

45 ms

pixel

pixel

14 ms

g_match

g_match

4 ms

match_redirect

match_redirect

4 ms

pixel

pixel

37 ms

aa_px

aa_px

3 ms

tap.php

tap.php

266 ms

tap.php

tap.php

311 ms

Accessibility Review

playcds.com.br accessibility score

100

Accessibility Issues

Best Practices

playcds.com.br best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

playcds.com.br SEO score

92

Search Engine Optimization Advices

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 uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Playcds.com.br can be misinterpreted by Google and other search engines. Our service has detected that English 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 Playcds.com.br 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

playcds.com.br

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