2.3 sec in total
334 ms
1.3 sec
594 ms
Welcome to unclejayexplains.com homepage info - get ready to check Unclejayexplains best content for United States right away, or after learning these important things about unclejayexplains.com
Visit unclejayexplains.comWe analyzed Unclejayexplains.com page load time and found that the first response time was 334 ms and then it took 1.9 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.
unclejayexplains.com performance score
334 ms
86 ms
89 ms
129 ms
89 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 66% of them (78 requests) were addressed to the original Unclejayexplains.com, 8% (10 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (762 ms) belongs to the original domain Unclejayexplains.com.
Page size can be reduced by 854.7 kB (30%)
2.9 MB
2.0 MB
In fact, the total size of Unclejayexplains.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. 75% 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 132.0 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 132.0 kB or 87% of the original size.
Potential reduce by 628.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. Obviously, Unclejayexplains needs image optimization as it can save up to 628.0 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 77.5 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 77.5 kB or 53% of the original size.
Potential reduce by 17.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. Unclejayexplains.com needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 79% of the original size.
Number of requests can be reduced by 41 (36%)
115
74
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unclejayexplains. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
unclejayexplains.com
334 ms
style.css
86 ms
coda-slider.css
89 ms
jquery.js
129 ms
jquery.scrollto.js
89 ms
jquery.localscroll.js
93 ms
jquery.serialscroll.js
140 ms
coda.slider.js
141 ms
layers.js
141 ms
smooth.js
142 ms
motionpack.js
172 ms
validationEngine.jquery.css
178 ms
podpress.css
175 ms
1pixelout_audio-player.js
177 ms
podpress.js
221 ms
tw-sack.min.js
193 ms
postratings-js-packed.js
197 ms
postratings-css.css
211 ms
show_ads.js
6 ms
en_US
76 ms
urchin.js
21 ms
ga.js
10 ms
__utm.gif
84 ms
rating_over.gif
79 ms
header.gif
147 ms
search.gif
117 ms
rating_on.gif
66 ms
rating_half.gif
118 ms
loading.gif
119 ms
zoom.png
145 ms
rating_off.gif
146 ms
unclejaymart.jpg
234 ms
btn_donate_SM.gif
126 ms
menubarbg.jpg
128 ms
searchbg.jpg
127 ms
rss.jpg
216 ms
sliderbg.jpg
217 ms
04-28-14-feature.JPG
277 ms
insertbg.png
242 ms
watchnow.jpg
215 ms
04-21-14-feature.JPG
253 ms
03-03-14-feature.JPG
325 ms
02-17-14-feature.JPG
328 ms
02-10-14-feature.JPG
326 ms
02-03-14-feature.JPG
324 ms
itembg.jpg
296 ms
commentsbg.gif
319 ms
04-28-14-thumb.JPG
340 ms
04-21-14-thumb.JPG
365 ms
03-03-14-thumb.JPG
366 ms
02-17-14-thumb.JPG
366 ms
02-10-14-thumb.JPG
371 ms
02-03-14-thumb.JPG
372 ms
01-27-14-thumb.JPG
383 ms
01-20-14-thumb.JPG
408 ms
01-13-14-thumb.JPG
409 ms
12-22-13-thumb.JPG
412 ms
12-16-13-thumb.JPG
415 ms
12-09-13-thumb.JPG
420 ms
pixel.gif
180 ms
ca-pub-9405047026272038.js
181 ms
zrt_lookup.html
184 ms
show_ads_impl.js
107 ms
UJ-Its-Healthcare.gov-thumb.JPG
394 ms
11-25-13-thumb.JPG
413 ms
142 ms
141 ms
11-18-13-thumb.JPG
367 ms
11-11-13-thumb.JPG
365 ms
11-04-13-thumb.JPG
375 ms
xd_arbiter.php
98 ms
xd_arbiter.php
118 ms
116 ms
12-19-11-thumb.jpg
352 ms
12-04-11-thumb.jpg
354 ms
11-27-11-thumb.jpg
436 ms
11-20-11-thumb.jpg
437 ms
UJ-Explanation-thumb.jpg
762 ms
__utm.gif
85 ms
ping
95 ms
09-12-11-thumb.jpg
424 ms
ads
248 ms
osd.js
37 ms
ads
361 ms
08-29-11-thumb.jpg
354 ms
08-22-11-thumb.jpg
355 ms
08-15-11-thumb.jpg
359 ms
fan.php
248 ms
08-08-11-thumb.jpg
670 ms
07-04-11-thumb.jpg
333 ms
06-30-11-thumb.jpg
321 ms
05-23-11-thumb.jpg
297 ms
05-16-11-thumb.jpg
321 ms
05-09-11-thumb.jpg
298 ms
blockhead.jpg
291 ms
blockbg.jpg
290 ms
tips.png
357 ms
scroll_left.png
357 ms
scroll_right.png
345 ms
410ucuAGgaJ.css
18 ms
pERLJfhzcxv.css
23 ms
FAHeNGXgPup.js
29 ms
FJmpeSpHpjS.js
44 ms
0wM5s1Khldu.js
27 ms
1bNoFZUdlYZ.js
53 ms
1472848_10153594486345322_2133865151_n.png
54 ms
1471155_10153503898905322_1963639822_n.png
23 ms
10354686_10150004552801856_220367501106153455_n.jpg
21 ms
12809663_10206788314361079_3657862785601000691_n.jpg
23 ms
10171050_848852585131221_1838299071322923961_n.jpg
22 ms
19449_101329109901376_5813571_n.jpg
23 ms
12821471_1135195016511758_6503768073279262099_n.jpg
21 ms
12243173_10100683025463732_8848555695972290793_n.jpg
25 ms
7380_1183218075023399_7817042178467814155_n.jpg
24 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
14 ms
I6-MnjEovm5.js
2 ms
pQrUxxo5oQp.js
4 ms
unclejayexplains.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 Unclejayexplains.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 Unclejayexplains.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.
unclejayexplains.com
Open Graph description is not detected on the main page of Unclejayexplains. 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: