Tools & Wizards About Us
pedroizquierdo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pedroizquierdo.com

Pedro Izquierdo, músico, profesor y timplista canario

Page Load Speed

5.8 sec in total

First Response

213 ms

Resources Loaded

5.4 sec

Page Rendered

230 ms

pedroizquierdo.com screenshot

About Website

Welcome to pedroizquierdo.com homepage info - get ready to check Pedro Izquierdo best content right away, or after learning these important things about pedroizquierdo.com

Pedro Izquierdo, músico, profesor, timplista canario. Clases de timple online. Partituras, tablaturas, tutoriales, discos... ✅ ✅ ✅

Visit pedroizquierdo.com

Key Findings

We analyzed Pedroizquierdo.com page load time and found that the first response time was 213 ms and then it took 5.6 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

pedroizquierdo.com performance score

0

Network Requests Diagram

pedroizquierdo.com

213 ms

www.pedroizquierdo.com

3779 ms

style.css

73 ms

styles.css

135 ms

reset.css

135 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 87% of them (67 requests) were addressed to the original Pedroizquierdo.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Pedroizquierdo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 362.2 kB (23%)

Content Size

1.6 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pedroizquierdo.com 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 39.7 kB

  • Original 50.9 kB
  • After minification 46.0 kB
  • After compression 11.2 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 39.7 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 23.6 kB

  • Original 1.1 MB
  • After minification 1.1 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. Pedro Izquierdo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 226.8 kB

  • Original 330.7 kB
  • After minification 303.9 kB
  • After compression 103.9 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 226.8 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 72.0 kB

  • Original 86.6 kB
  • After minification 64.9 kB
  • After compression 14.5 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. Pedroizquierdo.com needs all CSS files to be minified and compressed as it can save up to 72.0 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pedroizquierdo.com

pedroizquierdo.com

213 ms

www.pedroizquierdo.com

www.pedroizquierdo.com

3779 ms

style.css

style.css

73 ms

styles.css

styles.css

135 ms

reset.css

reset.css

135 ms

grid.css

grid.css

137 ms

fancybox.css

fancybox.css

138 ms

jplayer.css

jplayer.css

138 ms

theme.css

theme.css

140 ms

jquery.js

jquery.js

270 ms

jquery-migrate.min.js

jquery-migrate.min.js

203 ms

jquery-ui.min.js

jquery-ui.min.js

62 ms

fancybox.js

fancybox.js

204 ms

tooltipsy.js

tooltipsy.js

203 ms

slides.jquery.js

slides.jquery.js

204 ms

isotope.js

isotope.js

205 ms

script.js

script.js

300 ms

nivo-slider.css

nivo-slider.css

301 ms

nivoslider.js

nivoslider.js

302 ms

jplayer.css

jplayer.css

302 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

302 ms

jplayer.playlist.min.js

jplayer.playlist.min.js

336 ms

widgets.js

widgets.js

8 ms

jquery.form.min.js

jquery.form.min.js

355 ms

scripts.js

scripts.js

355 ms

comment-reply.min.js

comment-reply.min.js

357 ms

wp-embed.min.js

wp-embed.min.js

358 ms

quickstand.js

quickstand.js

357 ms

jquery.mousewheel.js

jquery.mousewheel.js

408 ms

bd-galleries.js

bd-galleries.js

408 ms

121021011019.jpg

121021011019.jpg

554 ms

120921030949.jpg

120921030949.jpg

624 ms

121023061034.jpg

121023061034.jpg

612 ms

121021011034.jpg

121021011034.jpg

555 ms

121021011010.jpg

121021011010.jpg

598 ms

121021011051.jpg

121021011051.jpg

820 ms

thumb_150817110832.jpg

thumb_150817110832.jpg

818 ms

thumb_150120110122.jpg

thumb_150120110122.jpg

818 ms

thumb_150120010120.jpg

thumb_150120010120.jpg

689 ms

facebook.png

facebook.png

678 ms

ga.js

ga.js

20 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

620 ms

__utm.gif

__utm.gif

12 ms

twitter.png

twitter.png

695 ms

googleplus.png

googleplus.png

696 ms

youtube.png

youtube.png

695 ms

feedburner.png

feedburner.png

694 ms

bg.jpg

bg.jpg

690 ms

plusone.js

plusone.js

73 ms

all.js

all.js

11 ms

facebook.png

facebook.png

462 ms

twitter.png

twitter.png

462 ms

googleplus.png

googleplus.png

464 ms

youtube.png

youtube.png

465 ms

rss.png

rss.png

469 ms

header_bg.png

header_bg.png

880 ms

mp_logo.png

mp_logo.png

508 ms

submenu-arrow.png

submenu-arrow.png

530 ms

loading.gif

loading.gif

537 ms

slide-shadow.png

slide-shadow.png

536 ms

timer.png

timer.png

549 ms

calendar.png

calendar.png

582 ms

jPlayer_bg.png

jPlayer_bg.png

613 ms

mp_jplayer_logo.png

mp_jplayer_logo.png

614 ms

jp_popup.png

jp_popup.png

613 ms

jPlayer_sprite.png

jPlayer_sprite.png

616 ms

shadow-300.png

shadow-300.png

650 ms

arrow_list.gif

arrow_list.gif

681 ms

CANDARA-webfont.woff

CANDARA-webfont.woff

728 ms

134 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

xd_arbiter.php

xd_arbiter.php

43 ms

xd_arbiter.php

xd_arbiter.php

60 ms

nivo-arrows.png

nivo-arrows.png

97 ms

black.png

black.png

87 ms

nav_active.png

nav_active.png

106 ms

nav.png

nav.png

104 ms

SEO Factors

pedroizquierdo.com SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

pedroizquierdo.com

Open Graph data is detected on the main page of Pedro Izquierdo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: