3.5 sec in total
179 ms
2.6 sec
733 ms
Click here to check amazing Ubiq content for Colombia. Otherwise, check out these important facts you probably never knew about ubiq.mobi
See related links to what you are looking for.
Visit ubiq.mobiWe analyzed Ubiq.mobi page load time and found that the first response time was 179 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ubiq.mobi performance score
179 ms
765 ms
381 ms
311 ms
453 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ubiq.mobi, 84% (52 requests) were made to Ubiz.mobi and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ubiz.mobi.
Page size can be reduced by 426.8 kB (18%)
2.4 MB
1.9 MB
In fact, the total size of Ubiq.mobi 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 43.7 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 6.9 kB, which is 13% 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 43.7 kB or 81% of the original size.
Potential reduce by 52.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. Ubiq images are well optimized though.
Potential reduce by 137.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 137.9 kB or 80% of the original size.
Potential reduce by 192.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. Ubiq.mobi needs all CSS files to be minified and compressed as it can save up to 192.9 kB or 86% of the original size.
Number of requests can be reduced by 20 (38%)
53
33
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ubiq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ubiq.mobi
179 ms
ubiz.mobi
765 ms
bootstrap.min.css
381 ms
font-awesome.min.css
311 ms
animate.css
453 ms
nivo-lightbox.css
276 ms
owl.carousel.css
277 ms
main.css
279 ms
styles.css
458 ms
jquery.simplyscroll.css
367 ms
css
67 ms
loader.gif
605 ms
logo_ubiz.png
384 ms
left-hand.png
1023 ms
right-hand.png
731 ms
blured-item1.png
537 ms
blured-item2.png
622 ms
blured-item3.png
620 ms
pointer1.png
619 ms
pointer2.png
622 ms
google-play.png
803 ms
app-store.png
723 ms
screen4.png
924 ms
screen3.png
1103 ms
feat2.jpg
1264 ms
jquery.min.js
68 ms
bootstrap.min.js
770 ms
jquery.parallax.js
850 ms
jquery.prettyPhoto.js
857 ms
waypoints.min.js
944 ms
jquery.counterup.min.js
946 ms
nivo-lightbox.min.js
955 ms
owl.carousel.js
1027 ms
jquery.innerfade.js
1035 ms
plugins.js
1027 ms
main.js
1061 ms
jquery.simplyscroll.min.js
1114 ms
startup.jpg
1113 ms
offers.jpg
1221 ms
business.jpg
1153 ms
users.jpg
1012 ms
chatroom.jpg
1036 ms
profile.jpg
1047 ms
captcha.php
1079 ms
bg.jpg
1005 ms
arrow-left.png
890 ms
arrow-right.png
910 ms
google-play-white.png
939 ms
app-store-grey.png
838 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
18 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
94 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
145 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
146 ms
fontawesome-webfont.woff
963 ms
glyphicons-halflings-regular.woff
849 ms
bg-6.jpg
806 ms
business_bg2.jpg
1013 ms
bg-8.jpg
835 ms
bg-2.jpg
1017 ms
atrk.js
40 ms
atrk.gif
21 ms
ubiq.mobi SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ubiq.mobi 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ubiq.mobi 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.
ubiq.mobi
Open Graph description is not detected on the main page of Ubiq. 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: