4.8 sec in total
1.1 sec
3.4 sec
316 ms
Click here to check amazing Funat GIGGLES content. Otherwise, check out these important facts you probably never knew about funatgiggles.com.sg
Visit funatgiggles.com.sgWe analyzed Funatgiggles.com.sg page load time and found that the first response time was 1.1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
funatgiggles.com.sg performance score
1119 ms
118 ms
176 ms
159 ms
149 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 59% of them (45 requests) were addressed to the original Funatgiggles.com.sg, 28% (21 requests) were made to Static.xx.fbcdn.net and 12% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Funatgiggles.com.sg.
Page size can be reduced by 354.4 kB (18%)
2.0 MB
1.7 MB
In fact, the total size of Funatgiggles.com.sg main page is 2.0 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 30.8 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 30.8 kB or 84% of the original size.
Potential reduce by 120.4 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. Funat GIGGLES images are well optimized though.
Potential reduce by 149.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 149.9 kB or 67% of the original size.
Potential reduce by 53.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. Funatgiggles.com.sg needs all CSS files to be minified and compressed as it can save up to 53.2 kB or 85% of the original size.
Number of requests can be reduced by 32 (43%)
75
43
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funat GIGGLES. 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 from 10 to 1 for CSS and as a result speed up the page load time.
www.funatgiggles.com.sg
1119 ms
nivo-slider.css
118 ms
prettyPhoto.css
176 ms
style.css
159 ms
frontend_style.css
149 ms
jquery.fancybox-1.3.4.css
190 ms
jquery.js
273 ms
jquery-migrate.min.js
194 ms
cufon-yui.js
218 ms
GROBOLD_500.font.js
236 ms
jquery.nivo.slider.pack.js
250 ms
jquery.prettyPhoto.js
251 ms
main.js
294 ms
jquery.mousewheel-3.0.4.pack.js
295 ms
jquery.fancybox-1.3.4.pack.js
305 ms
frontend_script.js
335 ms
gtm4wp-form-move-tracker.js
341 ms
wp-embed.min.js
367 ms
wp-emoji-release.min.js
255 ms
page-bg.png
151 ms
header-bg.png
153 ms
logo.png
205 ms
menu-bg.png
153 ms
menu-item.png
150 ms
thumb.php
660 ms
thumb.php
579 ms
thumb.php
841 ms
thumb.php
654 ms
thumb.php
840 ms
thumb.php
846 ms
thumb.php
920 ms
sidebar-bg.png
841 ms
featured-bg.png
841 ms
1Events.png
846 ms
2Attractions.png
858 ms
3Admission.png
859 ms
4Parties.png
859 ms
footer-bg.png
880 ms
star.png
880 ms
glyphicons-halflings-white.png
938 ms
letter.png
936 ms
input-bg.png
931 ms
read-on.png
955 ms
rss.png
938 ms
slider-arrows.png
928 ms
likebox.php
287 ms
hDvwL1_H7g-.css
90 ms
56WNbrUYLbL.css
112 ms
yZ--Yu0PDbV.css
133 ms
QD6_ejUFoCN.css
165 ms
xxJgcoj8mOR.css
173 ms
q68gy-v_YMF.js
189 ms
FJmpeSpHpjS.js
188 ms
0wM5s1Khldu.js
149 ms
1bNoFZUdlYZ.js
151 ms
njO1TPvGzoR.js
184 ms
1QuX41zDRrx.js
185 ms
Oagsvfb4VWi.js
233 ms
LTv6ZK-5zxz.js
240 ms
1FCa-btixu2.js
239 ms
12798948_779318915531781_4456615465730873584_n.jpg
168 ms
11329821_660973444032996_8739494061296314669_n.jpg
173 ms
1485089_780392668757739_2772613208114748139_n.jpg
195 ms
12105782_781599075303765_6803834679771326367_n.jpg
206 ms
983660_781599068637099_4038133714222892428_n.jpg
215 ms
2554_781599071970432_5796890408933317419_n.jpg
214 ms
937_779323838864622_7059261679361476567_n.jpg
227 ms
12798948_779318915531781_4456615465730873584_n.jpg
213 ms
12802743_776084975855175_6553158978947560562_n.jpg
274 ms
wL6VQj7Ab77.png
118 ms
s7jcwEQH7Sx.png
116 ms
pimRBh7B6ER.png
118 ms
QDwYpIaRyfG.png
118 ms
K00K-UgnsKu.png
118 ms
I6-MnjEovm5.js
22 ms
pQrUxxo5oQp.js
37 ms
funatgiggles.com.sg SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funatgiggles.com.sg 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 Funatgiggles.com.sg 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.
funatgiggles.com.sg
Open Graph description is not detected on the main page of Funat GIGGLES. 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: