1.3 sec in total
96 ms
938 ms
261 ms
Click here to check amazing Belly Buzz Squarespace content for United States. Otherwise, check out these important facts you probably never knew about bellybuzz.squarespace.com
Visit bellybuzz.squarespace.comWe analyzed Bellybuzz.squarespace.com page load time and found that the first response time was 96 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
bellybuzz.squarespace.com performance score
96 ms
63 ms
40 ms
46 ms
42 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 41% of them (34 requests) were addressed to the original Bellybuzz.squarespace.com, 35% (29 requests) were made to Static1.1.sqspcdn.com and 7% (6 requests) were made to Farm8.staticflickr.com. The less responsive or slowest element that took the longest time to load (348 ms) relates to the external source Static1.1.sqspcdn.com.
Page size can be reduced by 475.5 kB (31%)
1.5 MB
1.1 MB
In fact, the total size of Bellybuzz.squarespace.com main page is 1.5 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 58.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. 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 58.1 kB or 82% of the original size.
Potential reduce by 120.5 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, Belly Buzz Squarespace needs image optimization as it can save up to 120.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 252.9 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 252.9 kB or 75% of the original size.
Potential reduce by 43.9 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. Bellybuzz.squarespace.com needs all CSS files to be minified and compressed as it can save up to 43.9 kB or 84% of the original size.
Number of requests can be reduced by 28 (36%)
78
50
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Belly Buzz Squarespace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
bellybuzz.squarespace.com
96 ms
common.css
63 ms
squarespace-gallery-slideshow.css
40 ms
yahoo-dom-event.js
46 ms
connection_core-min.js
42 ms
json-min.js
42 ms
animation-min.js
40 ms
selector.js
48 ms
element.js
49 ms
global.js
57 ms
lightbox.js
105 ms
api.js
56 ms
base64.js
58 ms
census.js
97 ms
yahoo-min.js
98 ms
event-min.js
97 ms
event-mouseenter-min.js
98 ms
element-min.js
99 ms
social.js
98 ms
datefmt.js
101 ms
yui2-yui3-bridge.js
99 ms
squarespace-gallery-slideshow.js
99 ms
cookie-min.js
100 ms
eu-cookie-policy.js
101 ms
counter.js
14 ms
counter.asp
6 ms
webfont.js
38 ms
all_t.png
56 ms
meter.asp
49 ms
analytics.js
163 ms
mpp.vindicosuite.com
90 ms
RecordHit
25 ms
rest
59 ms
rest
70 ms
rest
92 ms
tileBG.jpg
110 ms
headerBG.jpg
27 ms
flickr-link.png
46 ms
meter.asp
13 ms
0
161 ms
twitter_32.png
33 ms
flickr_32.png
31 ms
facebookprofilepic_normal.jpg
13 ms
6870786543_96916a0e6a_m.jpg
64 ms
6870786473_07c1327368_m.jpg
62 ms
6870785925_1d7e3985e0_m.jpg
65 ms
6870784133_b2d991c1c2_m.jpg
63 ms
6870782717_a4a7de22e7_m.jpg
59 ms
6870781845_813d40a5f9_m.jpg
70 ms
HcptL9fG_normal.jpg
11 ms
celeb+ad+block.jpg
23 ms
linkedin_32.png
9 ms
stumbleupon_32.png
24 ms
82 ms
celebritywriters.jpg
15 ms
celeb+mullets.jpg
16 ms
celebmustaches.jpg
17 ms
blogheader.png
28 ms
blogthumb.jpg
348 ms
cookheader.png
11 ms
celebveterans+block.jpg
21 ms
cookthumb.jpg
252 ms
craftthumb.jpg
252 ms
craftheader.png
50 ms
blank.gif
58 ms
explorethumb.jpg
122 ms
shopheader.png
123 ms
shopthumb.jpg
289 ms
linkthumb.jpg
163 ms
linksheader.png
127 ms
bloglink.png
132 ms
exploreheader.png
159 ms
cooklink.png
157 ms
explorlink.png
180 ms
craftlink.png
157 ms
shoplink.png
151 ms
linkslink.png
144 ms
homeheader2.jpg
281 ms
facebook_32.png
53 ms
loading.gif
28 ms
overlay-arrow-left.png
25 ms
overlay-arrow-right.png
25 ms
bellybuzz.squarespace.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bellybuzz.squarespace.com 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 Bellybuzz.squarespace.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.
bellybuzz.squarespace.com
Open Graph description is not detected on the main page of Belly Buzz Squarespace. 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: