7.1 sec in total
1.5 sec
4.7 sec
832 ms
Welcome to robbertholf.com homepage info - get ready to check Rob Bertholf best content right away, or after learning these important things about robbertholf.com
Howzit, my name is Rob Bertholf. You have landed on my #braindump of anything web development & marketing related. This is my therapy to get closure on the consulting chapter of my life and a place...
Visit robbertholf.comWe analyzed Robbertholf.com page load time and found that the first response time was 1.5 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
robbertholf.com performance score
1484 ms
87 ms
105 ms
68 ms
100 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 52% of them (61 requests) were addressed to the original Robbertholf.com, 8% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Robbertholf.com.
Page size can be reduced by 493.4 kB (36%)
1.4 MB
868.7 kB
In fact, the total size of Robbertholf.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. 65% of websites need less resources to load. Images take 698.0 kB which makes up the majority of the site volume.
Potential reduce by 66.4 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 66.4 kB or 80% of the original size.
Potential reduce by 26.8 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. Rob Bertholf images are well optimized though.
Potential reduce by 168.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 168.6 kB or 59% of the original size.
Potential reduce by 231.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. Robbertholf.com needs all CSS files to be minified and compressed as it can save up to 231.6 kB or 79% of the original size.
Number of requests can be reduced by 63 (57%)
111
48
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rob Bertholf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
robbertholf.com
1484 ms
wp-emoji-release.min.js
87 ms
crayon.min.css
105 ms
styles.css
68 ms
font-awesome.min.css
100 ms
simple-line-icons.css
73 ms
style.css
132 ms
checkbox.min.css
131 ms
css
38 ms
css
55 ms
css
68 ms
style.css
177 ms
responsive.css
132 ms
style.css
135 ms
style.css
163 ms
style.css
164 ms
style.css
169 ms
style.css
179 ms
style.css
202 ms
form.min.css
199 ms
genericons.css
233 ms
jetpack.css
226 ms
jquery.js
333 ms
jquery-migrate.min.js
240 ms
crayon.min.js
311 ms
main.js
331 ms
ga.js
22 ms
__utm.gif
231 ms
devicepx-jetpack.js
167 ms
gprofiles.js
259 ms
wpgroho.js
167 ms
custom.js
189 ms
jquery.matchHeight.js
186 ms
jquery.sidr.js
185 ms
jquery.magnific-popup.min.js
183 ms
jquery.fitvids.js
182 ms
imagesloaded.pkgd.min.js
182 ms
affix.js
244 ms
e-201613.js
172 ms
analytics.js
154 ms
throne_logo.png
171 ms
RobBertholf-Blog-356x267.jpg
212 ms
DataDrivenDecisions-356x267.jpg
172 ms
WordPress4-356x267.png
302 ms
ContentMarketingTagcloud-267x267.jpg
170 ms
DataDrivenDecisions-267x267.jpg
213 ms
SocialAdvocacy-267x267.jpg
214 ms
PNM-Classes-267x267.jpg
215 ms
Klout-730x547.jpg
302 ms
SearchEngineOptimization-730x456.jpg
308 ms
bg-login-730x574.jpg
316 ms
Create-a-message-L8TR-271x300.jpg
299 ms
l8tr-ad.png
302 ms
l8tr-screenshot.png
303 ms
RobBertholf-Blog-350x185.jpg
303 ms
ContentMarketingTagcloud-350x185.jpg
305 ms
DataDrivenDecisions-350x185.jpg
312 ms
SearchEngineOptimization-350x185.jpg
398 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
129 ms
5M21SdFLkD52QavfmHs6cA.ttf
132 ms
Zd2E9abXLFGSr9G3YK2MsB43XjeME5heavxWqLE69Ro.ttf
216 ms
fontawesome-webfont.woff
320 ms
Simple-Line-Icons.woff
405 ms
UyYrYy3ltEffJV9QueSi4ZSGyElUubCb34ysAjXfb7E.ttf
217 ms
googleplus_ico.png
316 ms
facebook_ico.png
317 ms
linkedin_ico.png
318 ms
instagram_ico.png
402 ms
twitter_ico.png
403 ms
github_ico.png
402 ms
flickr_ico.png
400 ms
youtube_ico.png
400 ms
reddit_ico.png
473 ms
pinterest_ico.png
467 ms
sdk.js
446 ms
linkid.js
59 ms
collect
210 ms
collect
282 ms
count.js
72 ms
widgets.js
247 ms
hovercard.css
58 ms
services.css
159 ms
g.gif
78 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
160 ms
134 ms
xd_arbiter.php
263 ms
xd_arbiter.php
529 ms
syndication
140 ms
532717230409003008
260 ms
proxy.jpg
74 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
65 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
46 ms
urWn1A5L_normal.png
113 ms
R-ykb7UL_normal.png
130 ms
Cdv2YkKWAAAcxHl.jpg:small
199 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
132 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
135 ms
page.php
156 ms
proxy.jpg
10 ms
bmANhCXvh4r.css
304 ms
XCdv7aD40Gm.js
511 ms
tknZmeHjRao.js
676 ms
nw0sMxy_KfY.js
592 ms
jot.html
31 ms
11693939_1577865309100916_7702203645849073541_n.png
438 ms
564999_1377152655838850_1026313874_n.jpg
508 ms
12509212_10156491208200381_2691547796850737271_n.jpg
652 ms
11218212_1631757490399552_913265625133867195_n.jpg
648 ms
3403_657689304371707_3160017093021819718_n.jpg
650 ms
11846698_134242280250153_4712948644755668686_n.jpg
647 ms
11407223_10100678742307246_1421053769617901464_n.jpg
673 ms
1911624_10100913394876336_1016963800_n.jpg
649 ms
wL6VQj7Ab77.png
87 ms
WTZ_Jhk-ooC.png
86 ms
R9GKCzjAnbk.js
78 ms
AWWjhOengNF.js
82 ms
YnSasnyq68i.js
80 ms
kQf_jlUv-kX.js
148 ms
robbertholf.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Robbertholf.com 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 Robbertholf.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.
robbertholf.com
Open Graph data is detected on the main page of Rob Bertholf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: