9.3 sec in total
2.4 sec
6.9 sec
83 ms
Click here to check amazing Robby Kim content for United States. Otherwise, check out these important facts you probably never knew about robbykim.com
Visit robbykim.comWe analyzed Robbykim.com page load time and found that the first response time was 2.4 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
robbykim.com performance score
2352 ms
23 ms
36 ms
170 ms
218 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 74% of them (34 requests) were addressed to the original Robbykim.com, 9% (4 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Robbykim.com.
Page size can be reduced by 1.4 MB (47%)
2.9 MB
1.5 MB
In fact, the total size of Robbykim.com main page is 2.9 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. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 13.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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.2 kB or 78% of the original size.
Potential reduce by 926.7 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, Robby Kim needs image optimization as it can save up to 926.7 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 265.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 265.0 kB or 73% of the original size.
Potential reduce by 172.9 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. Robbykim.com needs all CSS files to be minified and compressed as it can save up to 172.9 kB or 84% of the original size.
Number of requests can be reduced by 30 (73%)
41
11
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Robby Kim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.robbykim.com
2352 ms
css
23 ms
css
36 ms
global.css
170 ms
grid.css
218 ms
fontello.css
197 ms
style.css
267 ms
responsive.css
218 ms
user.css
316 ms
jetpack.css
518 ms
jquery.js
838 ms
jquery-migrate.min.js
693 ms
devicepx-jetpack.js
7 ms
gprofiles.js
56 ms
wpgroho.js
489 ms
underscore.min.js
737 ms
jquery.tinyscrollbar.js
597 ms
jquery.sharrre-1.3.4.js
598 ms
jquery.transit.js
668 ms
utils.js
670 ms
jquery.fluxus-grid.js
669 ms
jquery.reveal.js
784 ms
jquery.fluxus-lightbox.js
783 ms
iscroll.js
784 ms
jquery.fluxus-slider.js
786 ms
main.js
938 ms
user.js
937 ms
comment-reply.min.js
1001 ms
wp-embed.min.js
1076 ms
e-201611.js
4 ms
wp-emoji-release.min.js
1100 ms
logo1.png
747 ms
menu-arrows.png
403 ms
slider-arrows.png
404 ms
Untitled.png
2225 ms
DSC_7486-1920x1271.jpg
1408 ms
DSC_2956-3-1920x1272.jpg
1292 ms
slash.png
564 ms
RFda8w1V0eDZheqfcyQ4EJS3E-kSBmtLoNJPDtbj2Pk.ttf
17 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
17 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
17 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
17 ms
hovercard.css
27 ms
services.css
54 ms
g.gif
7 ms
fontello.woff
455 ms
robbykim.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 Robbykim.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 Robbykim.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.
robbykim.com
Open Graph description is not detected on the main page of Robby Kim. 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: