12.6 sec in total
5.4 sec
6.5 sec
696 ms
Visit imobile.sg now to see the best up-to-date Imobile content and also check out these interesting facts you probably never knew about imobile.sg
Incoming search terms:ProjectBuyerLeadGenerationSystem-iMobilei mobile singaporeimobile singapore
Visit imobile.sgWe analyzed Imobile.sg page load time and found that the first response time was 5.4 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
imobile.sg performance score
5437 ms
47 ms
65 ms
57 ms
64 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 43% of them (35 requests) were addressed to the original Imobile.sg, 15% (12 requests) were made to Projects.imobile.sg and 15% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Imobile.sg.
Page size can be reduced by 1.2 MB (57%)
2.1 MB
911.5 kB
In fact, the total size of Imobile.sg main page is 2.1 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. CSS take 680.4 kB which makes up the majority of the site volume.
Potential reduce by 92.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 92.1 kB or 78% of the original size.
Potential reduce by 51.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. Imobile images are well optimized though.
Potential reduce by 453.3 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 453.3 kB or 71% of the original size.
Potential reduce by 588.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. Imobile.sg needs all CSS files to be minified and compressed as it can save up to 588.3 kB or 86% of the original size.
Number of requests can be reduced by 37 (54%)
68
31
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
imobile.sg
5437 ms
wp-emoji-release.min.js
47 ms
MobileSimulatorPRO.css
65 ms
MobileSliderPRO.css
57 ms
tfg_style.css
64 ms
styles.css
64 ms
css
22 ms
style.css
66 ms
shortcodes.css
77 ms
shortcodes_responsive.css
87 ms
jquery.js
138 ms
jquery-migrate.min.js
105 ms
MobileSimulatorPRO.js
87 ms
MobileSliderPRO.js
88 ms
jquery.easing.js
107 ms
pinit.js
7 ms
widgets.js
84 ms
in.js
7 ms
frontend-builder-global-functions.js
114 ms
jquery.form.min.js
114 ms
scripts.js
113 ms
comment-reply.min.js
132 ms
custom.js
137 ms
jquery.fitvids.js
143 ms
waypoints.min.js
144 ms
jquery.magnific-popup.js
168 ms
frontend-builder-scripts.js
171 ms
main-styles.css
138 ms
frontend-builder-style.css
148 ms
comparison.jpg
263 ms
pinit_fg_en_rect_gray_20.png
27 ms
iMobile_logo1.png
105 ms
Slide1.jpg
179 ms
iphone5black.png
86 ms
arrows2.png
86 ms
slide3.jpg
139 ms
slide21.jpg
102 ms
slide11.jpg
138 ms
slide4.jpg
134 ms
slide5.jpg
138 ms
mobilestats.jpg
259 ms
comparebutton.png
228 ms
bookmark.jpg
222 ms
Screenshot.jpg
221 ms
ecover480.png
226 ms
fullbrochure.png
274 ms
hotline.png
256 ms
marketme1.jpg
339 ms
CarMagnetic.jpg
273 ms
samplesites.png
337 ms
newprojects.png
337 ms
3j_2srh7o3M
151 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
59 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
75 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
68 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
70 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
94 ms
ETmodules_v2_4.ttf
146 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
44 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
41 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
46 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
47 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
49 ms
like.php
214 ms
counter.js
27 ms
www-embed-player-vflfNyN_r.css
63 ms
www-embed-player.js
101 ms
pinit_main.js
97 ms
t.php
207 ms
secureAnonymousFramework
113 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
113 ms
count.json
208 ms
qeKvIRsJabD.js
399 ms
LVx-xkvaJ0b.png
425 ms
share
196 ms
sprite_connect_v14.png
133 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
169 ms
3j_2srh7o3M
69 ms
ad_status.js
48 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
5 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
45 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
54 ms
imobile.sg SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imobile.sg 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 Imobile.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.
imobile.sg
Open Graph data is detected on the main page of Imobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: