12.4 sec in total
4.9 sec
7 sec
455 ms
Click here to check amazing Sebastiangomezblog content. Otherwise, check out these important facts you probably never knew about sebastiangomezblog.com
Visit sebastiangomezblog.comWe analyzed Sebastiangomezblog.com page load time and found that the first response time was 4.9 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sebastiangomezblog.com performance score
4885 ms
219 ms
266 ms
28 ms
270 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 75% of them (38 requests) were addressed to the original Sebastiangomezblog.com, 12% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Sebastiangomezblog.com.
Page size can be reduced by 2.2 MB (47%)
4.6 MB
2.4 MB
In fact, the total size of Sebastiangomezblog.com main page is 4.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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 183.1 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 183.1 kB or 85% of the original size.
Potential reduce by 386.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. Obviously, Sebastiangomezblog needs image optimization as it can save up to 386.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 790.0 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 790.0 kB or 63% of the original size.
Potential reduce by 839.6 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. Sebastiangomezblog.com needs all CSS files to be minified and compressed as it can save up to 839.6 kB or 87% of the original size.
Number of requests can be reduced by 28 (64%)
44
16
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sebastiangomezblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
sebastiangomezblog.com
4885 ms
wp-emoji-release.min.js
219 ms
layerslider.css
266 ms
css
28 ms
settings.css
270 ms
css
42 ms
style.css
377 ms
font-awesome.css
206 ms
ilightbox.css
222 ms
animations.css
304 ms
woocommerce.css
765 ms
default.min.css
552 ms
jquery.js
529 ms
jquery-migrate.min.js
402 ms
op-jquery-base-all.min.js
834 ms
form.js
757 ms
q2w3-fixed-widget.min.js
1181 ms
greensock.js
864 ms
layerslider.kreaturamedia.jquery.js
752 ms
layerslider.transitions.js
888 ms
jquery.themepunch.tools.min.js
1040 ms
jquery.themepunch.revolution.min.js
973 ms
load.sumome.com
404 ms
E-v1.js
38 ms
add-to-cart.min.js
1059 ms
jquery.blockUI.min.js
963 ms
woocommerce.min.js
961 ms
jquery.cookie.min.js
1069 ms
cart-fragments.min.js
1122 ms
main.min.js
1527 ms
wp-embed.min.js
1080 ms
Screen-Shot-2015-08-02-at-10.26.09-PM.png
241 ms
Screen-Shot-2015-08-02-at-11.14.30-AM.png
268 ms
edit-5.jpg
747 ms
Screen-Shot-2015-08-03-at-10.30.52-AM.png
623 ms
z4ko7isp52
83 ms
Reasons-to-Kill-Your-Plan-B-577x272.jpg
576 ms
vancity-infooverload-669x272.jpg
693 ms
Screen-Shot-2015-08-02-at-10.21.07-PM-669x272.png
844 ms
freeblog-banner.jpg
576 ms
roadt_copy-2-796x1024.png
836 ms
qpy-UiLNKP-VfOdbcs6r6-vvDin1pK8aKteLpeZ5c0A.woff
77 ms
qs_6LdoYjCitupC9judWT-vvDin1pK8aKteLpeZ5c0A.woff
77 ms
l1cOQ90roY9yC7voEhngDLO3LdcAZYWl9Si6vvxL-qU.woff
77 ms
bH7276GfdCjMjApa_dkG6bO3LdcAZYWl9Si6vvxL-qU.woff
76 ms
dI-qzxlKVQA6TUC5RKSb37O3LdcAZYWl9Si6vvxL-qU.woff
77 ms
icomoon.woff
570 ms
iframe_shim
96 ms
8c9q46CAcsp9TiRX9KLgZL3hpw3pgy2gAi-Ip7WPMi0.woff
99 ms
98a37163086eb3ee6bc3302b98f60b29df6b5c37.jpg
434 ms
loader.gif
141 ms
sebastiangomezblog.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sebastiangomezblog.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Sebastiangomezblog.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.
sebastiangomezblog.com
Open Graph description is not detected on the main page of Sebastiangomezblog. 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: