35.6 sec in total
390 ms
22.4 sec
12.9 sec
Welcome to johndarerblog.com homepage info - get ready to check Johndarer Blog best content right away, or after learning these important things about johndarerblog.com
John Darer's blog delves into everything you need to know about structured settlements and settlement planning news, the good the bad and the ugly. What's real? What's not?. Learn about structured set...
Visit johndarerblog.comWe analyzed Johndarerblog.com page load time and found that the first response time was 390 ms and then it took 35.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
johndarerblog.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.1 s
46/100
25%
Value5.0 s
63/100
10%
Value2,100 ms
7/100
30%
Value0
100/100
15%
Value15.5 s
7/100
10%
390 ms
643 ms
312 ms
98 ms
41 ms
Our browser made a total of 259 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Johndarerblog.com, 13% (33 requests) were made to Images6.linkwithin.com and 11% (29 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Static.technorati.com.
Page size can be reduced by 661.8 kB (23%)
2.9 MB
2.2 MB
In fact, the total size of Johndarerblog.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 463 B
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 463 B or 52% of the original size.
Potential reduce by 376.6 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, Johndarer Blog needs image optimization as it can save up to 376.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 282.7 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 282.7 kB or 67% of the original size.
Potential reduce by 2.1 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. Johndarerblog.com needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 73% of the original size.
Number of requests can be reduced by 110 (46%)
240
130
The browser has sent 240 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johndarer Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
johndarerblog.com
390 ms
structuredsettlements.typepad.com
643 ms
styles.css
312 ms
flyouts-min.js
98 ms
t.js
41 ms
insertCPI.js
804 ms
jsserv.php
35 ms
typepad-widget.js
529 ms
sttypepad.js
90 ms
postHotList.js
213 ms
a
111 ms
widget.js
218 ms
widget.js
218 ms
recommend.js
216 ms
print.css
235 ms
custom
216 ms
custom
217 ms
quant.js
160 ms
plusone.js
647 ms
base-weblog.css
308 ms
bxslider.css
311 ms
widgets.css
342 ms
recentpostsfancy.css
313 ms
tipjar.css
303 ms
screen.css
313 ms
typepad.js
421 ms
JDDarer.json
389 ms
typepad-widget.js
272 ms
analytics.js
215 ms
6a00d8341c520753ef017d42a9219c970c-150wi
1372 ms
findlawbutton_anim.gif
386 ms
insurance-journal-magazine-industry-favorite-88x31.gif
328 ms
cs-wh-120x60.gif
359 ms
laws.jpg
294 ms
324 ms
osPB.3.gif
320 ms
add.gif
277 ms
btn-fave2.png
20482 ms
addtomyyahoo4.gif
275 ms
vn_johndd_7645.gif
20481 ms
blog.gif
20482 ms
80x15.png
423 ms
80x15.gif
315 ms
loadedweb.png
315 ms
myAOLButtonSmall.gif
275 ms
uslawblognetwork121x29.gif
713 ms
pixel.png
112 ms
Logo_40wht.gif
271 ms
facebook.png
115 ms
linkedin.png
112 ms
pinterest.png
107 ms
skype.png
107 ms
twitter.png
108 ms
youtube.png
104 ms
pinit-1.png
138 ms
6a00d8341c520753ef01b8d1b9e4c3970c-800wi
763 ms
6a00d8341c520753ef01bb08d37c29970d-800wi
1060 ms
6a00d8341c520753ef01b7c82ede65970b-800wi
370 ms
6a00d8341c520753ef01b7c82e1740970b-320wi
449 ms
6a00d8341c520753ef01b8d1b87fef970c-800wi
941 ms
6a00d8341c520753ef01b7c82d0431970b-800wi
592 ms
6a00d8341c520753ef01bb08d12489970d-320wi
947 ms
6a00d8341c520753ef01bb08d08ef5970d-320wi
1114 ms
6a00d8341c520753ef01b7c82b376b970b-320wi
1053 ms
6a00d8341c520753ef01b8d1b39ab3970c-800wi
1115 ms
6a00d8341c520753ef01bb08cdaf2b970d-800wi
1113 ms
6a00d8341c520753ef01b8d1b39c52970c-800wi
1116 ms
6a00d8341c520753ef01b7c8291488970b-800wi
1114 ms
6a00d8341c520753ef01bb08cc9791970d-800wi
1393 ms
6a00d8341c520753ef01bb08cc0f24970d-500wi
4651 ms
6a00d8341c520753ef01b7c82776e6970b-500wi
4127 ms
6a00d8341c520753ef01bb08cbb6bf970d-320wi
1340 ms
6a00d8341c520753ef01bb08cb0a39970d-800wi
1329 ms
6a00d8341c520753ef01b8d1b0da9d970c-800wi
1919 ms
6a00d8341c520753ef01b7c8265fa4970b-800wi
4116 ms
6a00d8341c520753ef01b7c825f4ee970b-320wi
1853 ms
6a00d8341c520753ef01b8d1af90e6970c-800wi
5473 ms
sdk.js
4107 ms
header.jpg
239 ms
btn_viewmy_160x25.gif
248 ms
collect
329 ms
622 ms
182 ms
s.gif
112 ms
get_custom_js
154 ms
share-link-bg-reblog.gif
108 ms
tweet_button.html
496 ms
yca2BCwAnBQ
588 ms
tweet_button.html
461 ms
share-link-bg-digg.gif
85 ms
tweet_button.html
412 ms
tweet_button.html
532 ms
tweet_button.html
493 ms
show_widget
384 ms
show_widget
406 ms
show_widget
400 ms
show_widget
401 ms
show_widget
400 ms
tc.js
357 ms
vglnk.js
385 ms
jot
533 ms
jot
539 ms
jot
531 ms
sharethis.1ac33bc7d4476110a610f925104446ff.css
114 ms
www-embed-player-vfl5foy2V.css
2419 ms
www-embed-player.js
2919 ms
jot
398 ms
jot
801 ms
rotating-icon.gif
217 ms
385131547.jpg
377 ms
p
447 ms
default.jpg
227 ms
pixel.gif
648 ms
pixel.gif
220 ms
417760259.jpg
595 ms
410364683.jpg
223 ms
419235227.jpg
224 ms
370734985.jpg
582 ms
424417851.jpg
269 ms
389587695.jpg
409 ms
424476553.jpg
406 ms
394033919.jpg
404 ms
422409607.jpg
669 ms
422110217.jpg
430 ms
409281601.jpg
430 ms
tweet_button.html
155 ms
tweet_button.html
153 ms
tweet_button.html
172 ms
tweet_button.html
235 ms
tweet_button.html
259 ms
jot
2360 ms
jot
214 ms
tweet_button.html
2619 ms
jot
181 ms
tweet_button.html
2426 ms
v2
295 ms
jot
211 ms
jot
227 ms
tweet_button.html
196 ms
tweet_button.html
495 ms
tweet_button.html
1971 ms
dpx
2115 ms
jot
1934 ms
tweet_button.html
1956 ms
tweet_button.html
1966 ms
tweet_button.html
2131 ms
tweet_button.html
2006 ms
tweet_button.html
2101 ms
stats
342 ms
collect
157 ms
cb=gapi.loaded_0
199 ms
cb=gapi.loaded_1
303 ms
fastbutton
1738 ms
fastbutton
1693 ms
fastbutton
1697 ms
fastbutton
1689 ms
fastbutton
1697 ms
fastbutton
1712 ms
fastbutton
1716 ms
fastbutton
1728 ms
fastbutton
1707 ms
fastbutton
1775 ms
fastbutton
1754 ms
fastbutton
1774 ms
fastbutton
1770 ms
fastbutton
1774 ms
fastbutton
1771 ms
fastbutton
1915 ms
fastbutton
1809 ms
fastbutton
1771 ms
fastbutton
1800 ms
fastbutton
1884 ms
beacon.js
176 ms
pixel;r=1892516543;a=p-fcYWUmj5YbYKM;tags=typepad.core;fpan=1;fpa=P0-1984105941-1460133065101;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460133065100;tzo=-180;ref=http%3A%2F%2Fjohndarerblog.com%2F;url=http%3A%2F%2Fstructuredsettlements.typepad.com%2F;ogl=title.Structured%20Settlements%204Real%3A%20What's%20Real%20News%20in%20the%20Structured%20Settlements%252C%20Se%2Csite_name.Structured%20Settlements%204Real%C2%AE%20Blog%3A%20Structured%20Settlements%20%7C%20Settlement%20Planning%2Ctype.blog%2Curl.http%3A%2F%2Fstructuredsettlements%252Etypepad%252Ecom%2Fstructured_settlements_4r%2F%2Cdescription.Structured%20settlement%20news%252C%20information%20and%20expert%20opinion%20from%20structured%20settl%2Cimage.http%3A%2F%2Fup7%252Etypepad%252Ecom%2F6a00d8341c520753ef017d42a9219c970c-220si
1214 ms
jot
111 ms
show_widget
1416 ms
show_widget
1461 ms
show_widget
1460 ms
show_widget
1445 ms
show_widget
1442 ms
show_widget
1456 ms
show_widget
1460 ms
show_widget
1462 ms
show_widget
1462 ms
show_widget
1462 ms
2076 ms
getSegment.php
705 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
705 ms
postmessageRelay
954 ms
xrefid.xgi
741 ms
rs=AGLTcCP3oxc7cWS41pXoMx-UY1nqx3xkGg
725 ms
pixel
806 ms
jot
728 ms
jot
636 ms
jot
607 ms
jot
520 ms
jot
520 ms
jot
523 ms
t.dhj
519 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
271 ms
ping
1647 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
883 ms
ad_status.js
920 ms
ca.png
917 ms
1077434459-postmessagerelay.js
985 ms
rpc:shindig_random.js
746 ms
mapuid
703 ms
jot
613 ms
381491579.jpg
568 ms
237351107.jpg
445 ms
412417063.jpg
232 ms
383221765.jpg
346 ms
385131479.jpg
352 ms
424354865.jpg
353 ms
421852533.jpg
355 ms
419235161.jpg
338 ms
412417061.jpg
335 ms
423406353.jpg
370 ms
416013935.jpg
380 ms
422665331.jpg
378 ms
423062311.jpg
370 ms
345031671.jpg
382 ms
410999491.jpg
373 ms
358305499.jpg
520 ms
402943743.jpg
516 ms
416945403.jpg
521 ms
424103733.jpg
518 ms
370734961.jpg
519 ms
377887011.jpg
517 ms
365125057.jpg
529 ms
jot
194 ms
1394 ms
demconf.jpg
107 ms
t.dhj
231 ms
715 ms
52154.gif
467 ms
s-3271.xgi
536 ms
cm
529 ms
x35248
1014 ms
741 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
742 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
812 ms
cb=gapi.loaded_0
619 ms
cb=gapi.loaded_1
484 ms
hbpix
474 ms
223 ms
cb=gapi.loaded_1
441 ms
cm
267 ms
pixel
246 ms
pixel
166 ms
sync
189 ms
xd_arbiter.php
856 ms
xd_arbiter.php
1431 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
816 ms
cb=gapi.loaded_0
793 ms
2981
772 ms
47154.gif
757 ms
47154.gif
755 ms
batch
164 ms
johndarerblog.com 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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
johndarerblog.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
johndarerblog.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johndarerblog.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 Johndarerblog.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.
johndarerblog.com
Open Graph description is not detected on the main page of Johndarer Blog. 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: