5.8 sec in total
1 sec
3.4 sec
1.3 sec
Welcome to prodigal.typepad.com homepage info - get ready to check Prodigal Typepad best content for United States right away, or after learning these important things about prodigal.typepad.com
With the drawing of this Love and the voice of this Calling we shall not cease from exploration... (T.S. Eliot)
Visit prodigal.typepad.comWe analyzed Prodigal.typepad.com page load time and found that the first response time was 1 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
prodigal.typepad.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value4.6 s
35/100
25%
Value8.4 s
18/100
10%
Value3,120 ms
2/100
30%
Value0.089
92/100
15%
Value17.6 s
4/100
10%
1038 ms
130 ms
11 ms
63 ms
82 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 30% of them (18 requests) were addressed to the original Prodigal.typepad.com, 17% (10 requests) were made to Radionz.co.nz and 17% (10 requests) were made to Static.typepad.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Prodigal.typepad.com.
Page size can be reduced by 236.6 kB (22%)
1.1 MB
861.1 kB
In fact, the total size of Prodigal.typepad.com main page is 1.1 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. 35% of websites need less resources to load. Images take 764.1 kB which makes up the majority of the site volume.
Potential reduce by 89.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. This page needs HTML code to be minified as it can gain 12.2 kB, which is 11% 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 89.1 kB or 79% of the original size.
Potential reduce by 2.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. Prodigal Typepad images are well optimized though.
Potential reduce by 59.4 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 59.4 kB or 52% of the original size.
Potential reduce by 86.2 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. Prodigal.typepad.com needs all CSS files to be minified and compressed as it can save up to 86.2 kB or 81% of the original size.
Number of requests can be reduced by 15 (27%)
56
41
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prodigal Typepad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
prodigal.typepad.com
1038 ms
styles.css
130 ms
flyouts-min.js
11 ms
recommend.js
63 ms
print.css
82 ms
quant.js
5 ms
base-weblog.css
163 ms
bxslider.css
156 ms
widgets.css
165 ms
recentpostsfancy.css
82 ms
tipjar.css
154 ms
screen.css
163 ms
analytics.js
73 ms
Logo_40wht.gif
70 ms
6a00d8345192a569e200e550004d5e8833-75hi
113 ms
6a00d8345192a569e200e54fd8202f8833-75hi
176 ms
6a00d8345192a569e201b7c72c0fab970b-75hi
120 ms
6a00d8345192a569e201b8d0b590dd970c-75hi
156 ms
6a00d8345192a569e201b7c72bf629970b-75hi
174 ms
6a00d8345192a569e201bb07d0060c970d-75hi
154 ms
6a00d8345192a569e201b8d1ae1e61970c-320wi
158 ms
6a00d8345192a569e201bb07d005e1970d-75hi
171 ms
6a00d8345192a569e201b8d0b58f3b970c-75hi
157 ms
6a00d8345192a569e200e5501487968834-75hi
160 ms
6a00d8345192a569e201b7c72bf446970b-75hi
154 ms
6a00d8345192a569e201bb08c74fc7970d-120wi
165 ms
6a00d8345192a569e201bb08c5a92d970d-320wi
235 ms
6a00d8345192a569e201bb08c4ef76970d-320wi
280 ms
6a00d8345192a569e201bb08c38903970d-320wi
311 ms
6a00d8345192a569e201bb08c2b82a970d-320wi
236 ms
6a00d8345192a569e201b7c81d6da9970b-320wi
235 ms
6a00d8345192a569e201b8d1a4fdd0970c-320wi
653 ms
6a00d8345192a569e201bb08bf146d970d-120wi
313 ms
6a00d8345192a569e201b7c819dab4970b-320wi
316 ms
6a00d8345192a569e201b7c8195dd2970b-320wi
315 ms
6a00d8345192a569e201bb08bdabc5970d-500wi
375 ms
6a00d8345192a569e201b8d1a258ba970c-320wi
388 ms
6a00d8345192a569e201bb08b24c8c970d-320wi
389 ms
6a00d8345192a569e201bb08b1d9a6970d-320wi
395 ms
6a00d8345192a569e20133f41e09b8970b-150wi
398 ms
header.jpg
41 ms
content-twt.gif
39 ms
6a00d8345192a569e2010534bf948f970c-75hi
157 ms
6a00d8345192a569e201b8d0b5a7d7970c-75hi
162 ms
6a00d8345192a569e201bb07d0053f970d-75hi
160 ms
remote-player
860 ms
collect
11 ms
stats
214 ms
pixel;r=709804978;a=p-fcYWUmj5YbYKM;tags=typepad.core;fpan=1;fpa=P0-1818240746-1458179696606;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458179696606;tzo=-180;ref=;url=http%3A%2F%2Fprodigal.typepad.com%2F;ogl=
10 ms
beacon.js
6 ms
remote-player-e60e358714ecbc1f8cd2a46adba3ca761832fe52d06e049d1ad0709e75027aa4.css
201 ms
modernizer-cf8902c13eef81189b98205dc8987788d794b3febb4e306468776e4a9d5cc792.js
409 ms
player-3f1b741a5612dd66f7579e5a4e7d10987736b1073998562ea563c4a812c8f1ba.js
804 ms
embedsprite-364e34b703811a3dae198258b348ff2b37831a6dd6c0c0bf577fb3dc3e8ca46c.png
201 ms
0-b1442e85b03bdcaf66dc58c7abb98745dd2687d86350be9a298a1d9382ac849b.gif
203 ms
GCR-fff95da587fad226ed9f45916b8b27d6a8d1e2026cb4d67f2bd234eeec90ffb7.woff
787 ms
GCM-00c302f430ae460c155804aba95b27d51bc28c1569f8c795f306b1553d492965.woff
793 ms
icomoon-4096db263b009700ed94c8569e6ef5c7219469f97d90fb72a359a4e9446f1183.woff
447 ms
24e5dce63c48412b9a4740f8b7916d373c47f9350c071c8b.json
266 ms
nr-885.min.js
22 ms
prodigal.typepad.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[accesskey] values are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
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
prodigal.typepad.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
prodigal.typepad.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prodigal.typepad.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 Prodigal.typepad.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.
prodigal.typepad.com
Open Graph description is not detected on the main page of Prodigal Typepad. 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: