1.8 sec in total
29 ms
817 ms
923 ms
Click here to check amazing Robertgriffin content. Otherwise, check out these important facts you probably never knew about robertgriffin.net
Pragmatic Thoughts from a business advisor, self-proclaimed pragmatist, & disciple of the simple.
Visit robertgriffin.netWe analyzed Robertgriffin.net page load time and found that the first response time was 29 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
robertgriffin.net performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value6.5 s
9/100
25%
Value3.7 s
86/100
10%
Value690 ms
43/100
30%
Value0.001
100/100
15%
Value15.8 s
6/100
10%
29 ms
103 ms
120 ms
109 ms
113 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Robertgriffin.net, 14% (7 requests) were made to S0.wp.com and 12% (6 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Robertdgriffin.wordpress.com.
Page size can be reduced by 94.9 kB (18%)
541.0 kB
446.1 kB
In fact, the total size of Robertgriffin.net main page is 541.0 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. 50% of websites need less resources to load. Images take 284.0 kB which makes up the majority of the site volume.
Potential reduce by 94.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 94.3 kB or 76% of the original size.
Potential reduce by 0 B
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. Robertgriffin images are well optimized though.
Potential reduce by 421 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 238 B
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. Robertgriffin.net has all CSS files already compressed.
Number of requests can be reduced by 20 (47%)
43
23
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Robertgriffin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
robertdgriffin.wordpress.com
29 ms
103 ms
120 ms
109 ms
113 ms
118 ms
108 ms
css
148 ms
style.css
124 ms
123 ms
111 ms
navigation.min.js
106 ms
hovercards.min.js
126 ms
wpgroho.js
121 ms
118 ms
125 ms
w.js
126 ms
print.css
2 ms
conf
226 ms
ga.js
73 ms
dsc_5277_1.jpg
206 ms
2021-12-26-20.55.45-www.linkedin.com-cb832a4bcd43.png
198 ms
shield_badge.png
245 ms
56 ms
wpcom-mark.svg
19 ms
g.gif
153 ms
167 ms
pool-4306004_1280.jpg
154 ms
pexels-photo-5598284.jpeg
193 ms
pexels-photo-1152831.jpeg
239 ms
pexels-photo-3989140-e1640960448178.jpeg
163 ms
envelope-1829488_1920.jpg
165 ms
pexels-photo-6954174.jpeg
355 ms
dsc03882.jpg
248 ms
pexels-photo.jpg
376 ms
badge-686321_1920-300x300-1.jpg
246 ms
leadershipheader.png
457 ms
pexels-photo-5095945-e1640571989751.jpeg
403 ms
todoist-new-logo-red-700x300-1.png
354 ms
cropped-cropped-cropped-robertgriffinheadshotcircle2016_web.png
342 ms
g.gif
142 ms
g.gif
153 ms
__utm.gif
28 ms
font
35 ms
2021-12-26-20.55.45-www.linkedin.com-cb832a4bcd43.png
236 ms
ata.js
14 ms
shield_badge.png
126 ms
actionbar.css
1 ms
actionbar.js
18 ms
robertgriffin.net accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
robertgriffin.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
robertgriffin.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Robertgriffin.net 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 Robertgriffin.net 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.
robertgriffin.net
Open Graph data is detected on the main page of Robertgriffin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: