10.6 sec in total
1.3 sec
8.1 sec
1.1 sec
Click here to check amazing Not So Chubby Hubby content. Otherwise, check out these important facts you probably never knew about not-so-chubby-hubby.com
Bluehost - Top rated web hosting provider - Free 1 click installs For blogs, shopping carts, and more. Get a free domain name, real NON-outsourced 24/7 support, and superior speed. web hosting provide...
Visit not-so-chubby-hubby.comWe analyzed Not-so-chubby-hubby.com page load time and found that the first response time was 1.3 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
not-so-chubby-hubby.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.3 s
100/100
25%
Value1.3 s
100/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
1346 ms
192 ms
188 ms
189 ms
180 ms
Our browser made a total of 197 requests to load all elements on the main page. We found that 23% of them (45 requests) were addressed to the original Not-so-chubby-hubby.com, 10% (20 requests) were made to Maps.googleapis.com and 6% (12 requests) were made to 4236808.fls.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Not-so-chubby-hubby.com.
Page size can be reduced by 1.6 MB (64%)
2.4 MB
882.3 kB
In fact, the total size of Not-so-chubby-hubby.com main page is 2.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. 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 89.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 89.0 kB or 77% of the original size.
Potential reduce by 16.2 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. Not So Chubby Hubby images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 67% of the original size.
Potential reduce by 444.5 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. Not-so-chubby-hubby.com needs all CSS files to be minified and compressed as it can save up to 444.5 kB or 86% of the original size.
Number of requests can be reduced by 109 (60%)
183
74
The browser has sent 183 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Not So Chubby Hubby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.not-so-chubby-hubby.com
1346 ms
style.css
192 ms
styleRightSide300.css
188 ms
prettyPhoto.css
189 ms
shortcodes.css
180 ms
buttons-shortcode.css
179 ms
marklet.css
182 ms
ajax-contact.css
290 ms
theme_before.css
333 ms
modals.css
336 ms
playonvideo-skins.php
528 ms
superbox.css
333 ms
jquery.js
395 ms
jquery-migrate.min.js
390 ms
sociable.js
422 ms
sociable.css
422 ms
ajax-contact.js
446 ms
jquery.min.1.8.3.js
685 ms
playonvideo.php
646 ms
superbox.min.js
583 ms
show_ads.js
8 ms
scripts-active.js
503 ms
myStuff.js
504 ms
supersleight.plugin.js
1676 ms
jquery.nivo.slider.pack.js
1706 ms
jquery.prettyPhoto.js
1675 ms
marklet.js
1712 ms
comment-reply.min.js
1643 ms
wp-embed.min.js
1691 ms
jsapi
17 ms
cgmp.framework.min.js
1820 ms
wp-emoji-release.min.js
1727 ms
all.js
166 ms
ga.js
10 ms
image-2808917-10739449
71 ms
yellowTexture.gif
1699 ms
bg-top.png
1698 ms
bg-center.png
1698 ms
socHome_Exercise_Equipment.jpg
1752 ms
completeNavBg.png
1751 ms
search.png
1749 ms
Twitter.png
1751 ms
Youtube.png
1754 ms
Facebook.png
1753 ms
transparent.png
2032 ms
directions.png
2033 ms
ca-pub-9761419303307773.js
149 ms
zrt_lookup.html
83 ms
show_ads_impl.js
84 ms
__utm.gif
33 ms
10739449-1417806523625
98 ms
141 ms
xd_arbiter.php
153 ms
xd_arbiter.php
287 ms
ads
210 ms
plusone.js
90 ms
osd.js
39 ms
loading.gif
1863 ms
kzWH2SUMDbE
132 ms
ads
202 ms
bg-bottom.png
1708 ms
style_1_medium.png
1682 ms
ads
203 ms
UHBZcPOA9NY
95 ms
cb=gapi.loaded_0
9 ms
cb=gapi.loaded_1
40 ms
badge
305 ms
www-embed-player-vflfNyN_r.css
52 ms
www-embed-player.js
70 ms
base.js
134 ms
postmessageRelay
264 ms
343 ms
adj
315 ms
beacon
267 ms
322 ms
adj
259 ms
beacon
257 ms
423 ms
adj
332 ms
beacon
287 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
294 ms
ad_status.js
424 ms
rs=AGLTcCPxxcsaEHPLIxgGb9au86GYFsrXHA
41 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
66 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
159 ms
3193398744-postmessagerelay.js
378 ms
rpc:shindig_random.js
149 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
251 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
456 ms
photo.jpg
1120 ms
badges-eaefc7099b8352c2d91a1a3d728dcac7.png
384 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
365 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
372 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
367 ms
284 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1522480694
1050 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1522480694
1050 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1522480694
1042 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1522480694
1163 ms
0
1021 ms
277 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-3232342
1046 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-3232342
1171 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-3232342
1159 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-3232342
1168 ms
surly.js
1039 ms
surly.js
1047 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
204 ms
238 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1150870966
1030 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1150870966
1054 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1150870966
1211 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1150870966
1213 ms
index.html
1098 ms
verify_selector.js
905 ms
blank.gif
922 ms
bapi
1005 ms
index.html
1281 ms
verify_selector.js
897 ms
cb=gapi.loaded_0
157 ms
blank.gif
1046 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
669 ms
index.html
1205 ms
verify_selector.js
985 ms
bapi
923 ms
blank.gif
984 ms
style.css
709 ms
js
609 ms
ba.html
80 ms
pixel
108 ms
pixel
96 ms
4.gif
124 ms
pixel
194 ms
lidar.js
116 ms
sbhK2lTE.js
263 ms
common.js
60 ms
map.js
62 ms
util.js
135 ms
geocoder.js
59 ms
geometry.js
132 ms
directions.js
132 ms
marker.js
129 ms
StaticMapService.GetMapImage
187 ms
4311.js
175 ms
pixel
404 ms
pixel
404 ms
verifyr.js
338 ms
verifyr.js
202 ms
onion.js
92 ms
openhand_8_8.cur
82 ms
infowindow.js
67 ms
ViewportInfoService.GetViewportInfo
280 ms
stats.js
65 ms
controls.js
59 ms
css
353 ms
verifyr.js
308 ms
beacon.js
281 ms
0
171 ms
bg.png
278 ms
adchoices.en.png
279 ms
cTrvNaRi.html
150 ms
transparent.png
123 ms
dbapi
147 ms
google4.png
138 ms
mapcnt6.png
138 ms
sv5.png
138 ms
spotlight-poi.png
134 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
85 ms
tmapctrl.png
219 ms
cb_scout5.png
219 ms
tmapctrl4.png
218 ms
imgs8.png
218 ms
dbapi
167 ms
0
162 ms
dt
182 ms
vt
109 ms
vt
114 ms
vt
67 ms
vt
69 ms
vt
68 ms
dt
144 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
84 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
90 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
99 ms
FaceBody_300x250_logo.gif
99 ms
FaceBody_300x250_bg.jpg
122 ms
dt
140 ms
sd
61 ms
dt
99 ms
Rejuvenation_728x90_logo.gif
93 ms
Rejuvenation_728x90_bg.jpg
86 ms
Rejuvenation_300x250_logo.gif
93 ms
Rejuvenation_300x250_bg.jpg
102 ms
AuthenticationService.Authenticate
108 ms
box_19_top-right.png
56 ms
ci.png
47 ms
not-so-chubby-hubby.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
<frame> or <iframe> elements do not have a title
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
not-so-chubby-hubby.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
not-so-chubby-hubby.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Not-so-chubby-hubby.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 Not-so-chubby-hubby.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.
not-so-chubby-hubby.com
Open Graph description is not detected on the main page of Not So Chubby Hubby. 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: