9.6 sec in total
536 ms
8 sec
991 ms
Visit pedrogaspar.net now to see the best up-to-date Pedro Gaspar content and also check out these interesting facts you probably never knew about pedrogaspar.net
This website is presented as a personal and professional portfolio of Pedro Gaspar, and becomes the main vehicle publisher of the work i've done.
Visit pedrogaspar.netWe analyzed Pedrogaspar.net page load time and found that the first response time was 536 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pedrogaspar.net performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value11.1 s
0/100
25%
Value8.9 s
15/100
10%
Value200 ms
89/100
30%
Value0.785
5/100
15%
Value8.5 s
38/100
10%
536 ms
153 ms
299 ms
372 ms
425 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 84% of them (47 requests) were addressed to the original Pedrogaspar.net, 7% (4 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Pedrogaspar.net.
Page size can be reduced by 1.2 MB (39%)
3.1 MB
1.9 MB
In fact, the total size of Pedrogaspar.net main page is 3.1 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 49.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 49.2 kB or 83% of the original size.
Potential reduce by 24.0 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. Pedro Gaspar images are well optimized though.
Potential reduce by 730.4 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 730.4 kB or 77% of the original size.
Potential reduce by 427.0 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. Pedrogaspar.net needs all CSS files to be minified and compressed as it can save up to 427.0 kB or 86% of the original size.
Number of requests can be reduced by 26 (53%)
49
23
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pedro Gaspar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pedrogaspar.net
536 ms
js_composer_front.css
153 ms
css
299 ms
css
372 ms
css
425 ms
css
482 ms
styles.css
320 ms
rgs.css
317 ms
font-awesome.min.css
323 ms
style.css
624 ms
responsive.css
347 ms
mediaelementplayer.min.css
355 ms
wp-mediaelement.css
467 ms
ascend.css
468 ms
jquery.js
663 ms
jquery-migrate.min.js
471 ms
modernizr.js
472 ms
jquery.form.min.js
615 ms
scripts.js
796 ms
superfish.js
794 ms
respond.js
849 ms
sticky.js
852 ms
prettyPhoto.js
853 ms
isotope.min.js
853 ms
init.js
2159 ms
nectar-slider.js
911 ms
ajaxify.js
908 ms
js_composer_front.js
908 ms
logo_black.png
146 ms
logo_black2x.png
138 ms
logo_white.png
278 ms
logo_white2x.png
280 ms
thumb_moody3-1000x1000.jpg
2613 ms
thumb_rcz-1000x1000.jpg
1047 ms
thumb_carris21-500x1000.jpg
2159 ms
thumb_cmc2-500x500.jpg
601 ms
thumb_super_especial-1000x1000.jpg
2622 ms
thumb_gti2-500x500.jpg
899 ms
thumb_super_bock2-500x500.jpg
1308 ms
thumb5082-500x500.jpg
1193 ms
thumb_descubrasse-500x500.jpg
1306 ms
thumb_gti_project-900x500.jpg
2159 ms
thumb_delta2-500x500.jpg
2156 ms
edp_thumb-900x500.jpg
2163 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
268 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
311 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
372 ms
icomoon.woff
2092 ms
OpenSans-Light-webfont.woff
2092 ms
fontawesome-webfont.svg
2093 ms
analytics.js
96 ms
collect
60 ms
pedrogaspar.net
143 ms
diagonal_line.png
138 ms
Imagem_hp21.jpg
4496 ms
fontawesome-webfont.woff
597 ms
pedrogaspar.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pedrogaspar.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
pedrogaspar.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pedrogaspar.net 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 Pedrogaspar.net 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.
pedrogaspar.net
Open Graph data is detected on the main page of Pedro Gaspar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: