5.6 sec in total
1.2 sec
3.7 sec
714 ms
Visit rorymccauley.com now to see the best up-to-date Rorymccauley content and also check out these interesting facts you probably never knew about rorymccauley.com
Dublin marathon 2013 training blog
Visit rorymccauley.comWe analyzed Rorymccauley.com page load time and found that the first response time was 1.2 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rorymccauley.com performance score
1223 ms
84 ms
98 ms
124 ms
161 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 71% of them (39 requests) were addressed to the original Rorymccauley.com, 5% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Rorymccauley.com.
Page size can be reduced by 590.2 kB (68%)
869.8 kB
279.6 kB
In fact, the total size of Rorymccauley.com main page is 869.8 kB. 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 379.9 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.2 kB or 76% of the original size.
Potential reduce by 7.2 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. Rorymccauley images are well optimized though.
Potential reduce by 243.6 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 243.6 kB or 64% of the original size.
Potential reduce by 299.2 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. Rorymccauley.com needs all CSS files to be minified and compressed as it can save up to 299.2 kB or 83% of the original size.
Number of requests can be reduced by 32 (63%)
51
19
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rorymccauley. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.rorymccauley.com
1223 ms
style.css
84 ms
custom.css
98 ms
prettyPhoto.css
124 ms
styles.css
161 ms
wp-email-subscription-popup.css
161 ms
subscribe-popup.css
158 ms
jetpack.css
206 ms
wtc-styles.css
152 ms
wp-wtc-ajax.js
186 ms
jquery.min.js
7 ms
jquery-ui.min.js
10 ms
contact-form.js
216 ms
custom.js
215 ms
jquery.easing.js
219 ms
jquery.prettyPhoto.js
226 ms
wp-email-subscription-popup-js.js
284 ms
subscribe-popup.js
288 ms
open_in_new_window_no.js
295 ms
open_in_new_window.js
272 ms
wp-emoji-release.min.js
207 ms
google_analytics_auto.js
200 ms
jquery.form.min.js
175 ms
scripts.js
173 ms
devicepx-jetpack.js
5 ms
gprofiles.js
57 ms
wpgroho.js
171 ms
wp-embed.min.js
169 ms
e-201611.js
5 ms
ga.js
58 ms
1421241_451628034954159_2108705351_o-225x300.jpg
455 ms
me-n-eims-168x300.jpg
455 ms
boston-192x168-custom.jpeg
454 ms
born-to-run.jpeg
454 ms
search.png
453 ms
social_1.png
452 ms
social_2.png
495 ms
social_3.png
543 ms
social_4.png
513 ms
social_5.png
495 ms
social_11.png
505 ms
AjaxLoader.gif
540 ms
1378845578_Error.png
567 ms
1378845314_001_06.gif
568 ms
KEMEBBwO6J8
449 ms
League_Gothic-webfont.woff
622 ms
__utm.gif
383 ms
g.gif
8 ms
www-embed-player-vflfNyN_r.css
27 ms
www-embed-player.js
53 ms
base.js
79 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
59 ms
ad_status.js
58 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
52 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
rorymccauley.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rorymccauley.com 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 Rorymccauley.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.
rorymccauley.com
Open Graph description is not detected on the main page of Rorymccauley. 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: