2.6 sec in total
382 ms
2.1 sec
151 ms
Visit davidegea.com now to see the best up-to-date David Egea content for Spain and also check out these interesting facts you probably never knew about davidegea.com
Blog personal davidegea.com
Visit davidegea.comWe analyzed Davidegea.com page load time and found that the first response time was 382 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
davidegea.com performance score
382 ms
371 ms
142 ms
207 ms
846 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 32% of them (19 requests) were addressed to the original Davidegea.com, 10% (6 requests) were made to Pbs.twimg.com and 10% (6 requests) were made to Bannersinferiors.davidegea.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Banners.davidegea.com.
Page size can be reduced by 818.5 kB (60%)
1.4 MB
536.2 kB
In fact, the total size of Davidegea.com main page is 1.4 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. 50% of websites need less resources to load. Javascripts take 655.7 kB which makes up the majority of the site volume.
Potential reduce by 13.3 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 13.3 kB or 71% of the original size.
Potential reduce by 32.5 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. Obviously, David Egea needs image optimization as it can save up to 32.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 426.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 426.7 kB or 65% of the original size.
Potential reduce by 346.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. Davidegea.com needs all CSS files to be minified and compressed as it can save up to 346.0 kB or 85% of the original size.
Number of requests can be reduced by 17 (31%)
55
38
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Egea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
davidegea.com
382 ms
www.davidegea.com
371 ms
general.css
142 ms
home.css
207 ms
jquery.min.js
846 ms
ga.js
30 ms
david_egea.jpg
1062 ms
futuroscracks_davidegea.png
709 ms
__utm.gif
23 ms
rockestatal_davidegea.png
772 ms
colleccio_davidegea_es.png
772 ms
paris2006_davidegea.png
842 ms
roma2009_davidegea.png
776 ms
wembley2011_davidegea.png
782 ms
twitter_banner_davidegea.png
231 ms
facebook_banner_davidegea.png
197 ms
rss_banner_davidegea.png
335 ms
campions-deuropa.jpg
386 ms
twitter-icon.png
336 ms
facebook-icon.png
343 ms
vimeo-icon.png
342 ms
linkedin-icon.png
385 ms
flickr-icon.png
393 ms
twitpic-icon.png
445 ms
foursquare-icon.png
439 ms
google-plus-icon.png
495 ms
rss-icon.png
497 ms
widgets.js
5 ms
33369118
129 ms
116vEYY58bo
90 ms
www-embed-player-vflRGs1ko.css
82 ms
www-embed-player.js
162 ms
player.js
82 ms
player.css
53 ms
ga.js
80 ms
vuid.min.js
62 ms
__utm.gif
79 ms
proxy.html
67 ms
226450864.jpg
162 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
29 ms
ad_status.js
53 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
78 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
89 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
13 ms
tabs.jpg
409 ms
syndication
84 ms
346947932827815938
228 ms
proxy.jpg
160 ms
proxy.jpg
185 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
4 ms
4e2109a0ccaffbbe9ad6352fa9476b18_normal.jpeg
129 ms
h7ozw78jezk4tx4cetad_normal.jpeg
154 ms
0uBBIizd_normal.jpg
156 ms
8405d91472c0e3fde243053bbd67bd0e_normal.png
154 ms
WcNKtAiq_normal.jpg
155 ms
e1BtVZI2_normal.jpeg
156 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
15 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
48 ms
davidegea.com SEO score
EN
ES
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Davidegea.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Davidegea.com main page’s claimed encoding is iso-8859-1. 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.
davidegea.com
Open Graph description is not detected on the main page of David Egea. 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: