Tools & Wizards About Us
velho.palcomp3.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

velho.palcomp3.com

Velho James - Palco MP3

Page Load Speed

2.8 sec in total

First Response

98 ms

Resources Loaded

2.4 sec

Page Rendered

300 ms

velho.palcomp3.com screenshot

About Website

Click here to check amazing Velho Palco MP3 content for Brazil. Otherwise, check out these important facts you probably never knew about velho.palcomp3.com

Velho James oferece 8 músicas para ouvir no Palco MP3.

Visit velho.palcomp3.com

Key Findings

We analyzed Velho.palcomp3.com page load time and found that the first response time was 98 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

velho.palcomp3.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value2,430 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

velho.palcomp3.com

98 ms

palcomp3.com

289 ms

palcomp3.com

747 ms

fe670.css.css

29 ms

barra.css

169 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Velho.palcomp3.com, 29% (21 requests) were made to Studiosol-a.akamaihd.net and 10% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (747 ms) relates to the external source Palcomp3.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (58%)

Content Size

1.8 MB

After Optimization

746.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Velho.palcomp3.com main page is 1.8 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 160.5 kB

  • Original 213.2 kB
  • After minification 211.7 kB
  • After compression 52.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 160.5 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 5.1 kB

  • Original 305.5 kB
  • After minification 300.3 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. Velho Palco MP3 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 743.8 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 357.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 743.8 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 139.2 kB

  • Original 174.7 kB
  • After minification 174.6 kB
  • After compression 35.4 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. Velho.palcomp3.com needs all CSS files to be minified and compressed as it can save up to 139.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (58%)

Requests Now

67

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

velho.palcomp3.com

velho.palcomp3.com

98 ms

palcomp3.com

palcomp3.com

289 ms

palcomp3.com

palcomp3.com

747 ms

fe670.css.css

fe670.css.css

29 ms

barra.css

barra.css

169 ms

lab.js

lab.js

201 ms

pql

pql

121 ms

00004.sprite_gradientes.png

00004.sprite_gradientes.png

33 ms

00008.sprite_geral.png

00008.sprite_geral.png

12 ms

vazio.gif

vazio.gif

17 ms

00009.sprite_player.png

00009.sprite_player.png

19 ms

1456418623_202482_sp.jpg

1456418623_202482_sp.jpg

44 ms

145681020963.jpg

145681020963.jpg

152 ms

grey.gif

grey.gif

99 ms

145382526521.jpg

145382526521.jpg

100 ms

00004.sprite_icones.png

00004.sprite_icones.png

31 ms

145389672316.jpg

145389672316.jpg

97 ms

00005.sprite_home.png

00005.sprite_home.png

44 ms

145672744418.jpg

145672744418.jpg

152 ms

loading_cinza.gif

loading_cinza.gif

46 ms

gpt.js

gpt.js

44 ms

gw.js

gw.js

393 ms

dc.js

dc.js

146 ms

t3m.js

t3m.js

88 ms

bt_twitter.gif

bt_twitter.gif

85 ms

e1fd5.plugins.js

e1fd5.plugins.js

85 ms

1374a.SS.palco.js

1374a.SS.palco.js

140 ms

SS.ccidbar.js

SS.ccidbar.js

664 ms

pubads_impl_81.js

pubads_impl_81.js

144 ms

cabin-regular.woff

cabin-regular.woff

52 ms

player_api

player_api

53 ms

all.js

all.js

290 ms

ads

ads

229 ms

container.html

container.html

56 ms

www-widgetapi.js

www-widgetapi.js

36 ms

expansion_embed.js

expansion_embed.js

127 ms

ads

ads

239 ms

m_js_controller.js

m_js_controller.js

31 ms

favicon

favicon

98 ms

abg.js

abg.js

57 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

131 ms

osd.js

osd.js

124 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

77 ms

101 ms

xd_arbiter.php

xd_arbiter.php

337 ms

s

s

67 ms

x_button_blue2.png

x_button_blue2.png

29 ms

localizacao.json

localizacao.json

207 ms

1456418405_350532_sp.jpg

1456418405_350532_sp.jpg

35 ms

sprite_geral.png

sprite_geral.png

58 ms

client:plusone.js

client:plusone.js

78 ms

ads

ads

37 ms

1456518802_75077_sp.jpg

1456518802_75077_sp.jpg

20 ms

ads

ads

176 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

fastbutton

fastbutton

85 ms

393278854.js

393278854.js

128 ms

postmessageRelay

postmessageRelay

46 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

14 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

10 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

57 ms

api.js

api.js

45 ms

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

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

44 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

53 ms

base.js

base.js

55 ms

ajax-loader.gif

ajax-loader.gif

28 ms

ping

ping

36 ms

auth

auth

53 ms

b

b

24 ms

b

b

8 ms

2637085964-postmessage.js

2637085964-postmessage.js

3 ms

Accessibility Review

velho.palcomp3.com accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

velho.palcomp3.com best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

velho.palcomp3.com SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Velho.palcomp3.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Velho.palcomp3.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

velho.palcomp3.com

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