5 sec in total
1.4 sec
3.4 sec
260 ms
Welcome to worldgettingsmaller.com homepage info - get ready to check Worldgettingsmaller best content right away, or after learning these important things about worldgettingsmaller.com
Airline and Airport facts and figures. The truth about flying and all you will need to know about how to get the best value when flying.
Visit worldgettingsmaller.comWe analyzed Worldgettingsmaller.com page load time and found that the first response time was 1.4 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
worldgettingsmaller.com performance score
1386 ms
1189 ms
118 ms
119 ms
121 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 90% of them (65 requests) were addressed to the original Worldgettingsmaller.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Worldgettingsmaller.com.
Page size can be reduced by 510.7 kB (29%)
1.8 MB
1.3 MB
In fact, the total size of Worldgettingsmaller.com main page is 1.8 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 39.3 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 7.5 kB, which is 15% 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 39.3 kB or 81% of the original size.
Potential reduce by 31.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. Worldgettingsmaller images are well optimized though.
Potential reduce by 246.6 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 246.6 kB or 67% of the original size.
Potential reduce by 193.3 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. Worldgettingsmaller.com needs all CSS files to be minified and compressed as it can save up to 193.3 kB or 87% of the original size.
Number of requests can be reduced by 34 (49%)
69
35
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Worldgettingsmaller. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
worldgettingsmaller.com
1386 ms
www.worldgettingsmaller.com
1189 ms
widgets.css
118 ms
style.css
119 ms
style.css
121 ms
style.css
336 ms
prettyPhoto.css
184 ms
mediaelementplayer.css
152 ms
responsive.css
223 ms
jquery.reject.css
179 ms
jquery.js
352 ms
jquery-migrate.min.js
210 ms
modernizr.custom.17475.js
244 ms
_utils.js
253 ms
skip-link-focus-fix.js
183 ms
html5.js
198 ms
superfish.js
221 ms
jquery.jclock.js
230 ms
jquery.flexslider-min.js
242 ms
jquery.prettyPhoto.js
319 ms
jquery.tools.min.js
271 ms
jquery.jcarousel.min.js
316 ms
mediaelement-and-player.min.js
358 ms
jquery.cookie.js
316 ms
jquery.elastislide.js
339 ms
jquery-ui.custom.min.js
374 ms
jquery.reject.js
384 ms
jquery.mobilemenu.min.js
360 ms
main.js
365 ms
css
24 ms
ga.js
22 ms
cropped-wgs_logo_small2.png
62 ms
boxed-pattern6.jpg
470 ms
twitter-icon.png
132 ms
search-button.png
131 ms
menu-icon.png
132 ms
home-icon.gif
149 ms
preloader.gif
149 ms
package-holidays-620x310.jpg
204 ms
Jetlag-620x310.jpeg
160 ms
firstclass-620x310.jpg
257 ms
ipad-620x310.jpg
328 ms
slider-date-icon.png
190 ms
Singapore-Changi-Aiport--194x123.jpg
211 ms
perfume-bottle-194x123.jpg
256 ms
Grey-black-suitcase-194x123.jpg
263 ms
cropped-plane-45x33.png
258 ms
cropped-plane-229x147.png
352 ms
trans2.gif
128 ms
img-link-icon.png
311 ms
img-overlay.png
296 ms
post-date-icon.png
303 ms
list-styles.png
345 ms
video_link_icon.png
351 ms
__utm.gif
26 ms
footer-tw-icon.png
339 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
22 ms
widgets.js
95 ms
footer-divider.png
336 ms
overlay.png
361 ms
to-top.gif
360 ms
site-options-tg.png
366 ms
options_select.gif
386 ms
switcher.png
381 ms
pattern_switches.png
403 ms
slider-caption1.png
339 ms
slider-caption2.png
339 ms
home-slider-controls.png
351 ms
video-controls.gif
360 ms
menu-select.gif
372 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
137 ms
syndication
77 ms
worldgettingsmaller.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 Worldgettingsmaller.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 Worldgettingsmaller.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.
worldgettingsmaller.com
Open Graph description is not detected on the main page of Worldgettingsmaller. 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: