3.1 sec in total
416 ms
2.2 sec
517 ms
Visit mobilelikez2.net now to see the best up-to-date Mobilelikez 2 content for United States and also check out these interesting facts you probably never knew about mobilelikez2.net
Visit mobilelikez2.netWe analyzed Mobilelikez2.net page load time and found that the first response time was 416 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
mobilelikez2.net performance score
416 ms
126 ms
23 ms
47 ms
8 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mobilelikez2.net, 6% (6 requests) were made to I.simpli.fi and 4% (4 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (416 ms) relates to the external source Mobilelikez.com.
Page size can be reduced by 862.5 kB (40%)
2.1 MB
1.3 MB
In fact, the total size of Mobilelikez2.net 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 17.7 kB, which is 22% 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 63.8 kB or 81% of the original size.
Potential reduce by 17.6 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. Mobilelikez 2 images are well optimized though.
Potential reduce by 737.1 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 737.1 kB or 65% of the original size.
Potential reduce by 44.0 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. Mobilelikez2.net needs all CSS files to be minified and compressed as it can save up to 44.0 kB or 84% of the original size.
Number of requests can be reduced by 57 (63%)
90
33
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilelikez 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.mobilelikez.com
416 ms
sfp.js
126 ms
pixel-103699-077b9bc72c45287b7bab50a3808e2e44637a721d.js
23 ms
jquery.min.js
47 ms
styles.css
8 ms
meteor-slides.css
8 ms
pagenavi-css.css
8 ms
css
27 ms
style.css
15 ms
jquery.js
19 ms
jquery-migrate.min.js
12 ms
ajax.js
11 ms
jquery.cycle.all.js
15 ms
jquery.metadata.v2.js
12 ms
jquery.touchwipe.1.1.1.js
13 ms
slideshow.js
14 ms
jquery-latest.js
7 ms
jquery.shorten.js
14 ms
analytics.js
14 ms
load.js
130 ms
fbevents.js
86 ms
track
68 ms
quant.js
41 ms
dpx.js
61 ms
cc.js
117 ms
headerlogo2.png
34 ms
95 ms
97 ms
103 ms
gallery.png
24 ms
timthumb.php
27 ms
timthumb.php
76 ms
timthumb.php
64 ms
timthumb.php
66 ms
timthumb.php
67 ms
timthumb.php
69 ms
timthumb.php
68 ms
401246.html
60 ms
365728.html
57 ms
timthumb.php
71 ms
timthumb.php
72 ms
timthumb.php
71 ms
timthumb.php
77 ms
timthumb.php
73 ms
t
74 ms
timthumb.php
64 ms
timthumb.php
65 ms
timthumb.php
66 ms
timthumb.php
65 ms
timthumb.php
66 ms
p
50 ms
pixel;r=948774235;a=p-zyKdW7Td_sfXE;fpan=1;fpa=P0-2125102802-1458442675886;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458442675885;tzo=-180;ref=http%3A%2F%2Fwww.mobilelikez.com%2F;url=http%3A%2F%2Fwww.mobilelikez.com%2F;ogl=
54 ms
jquery.form.min.js
36 ms
scripts.js
33 ms
comment-reply.min.js
34 ms
navigation.js
34 ms
cFjxecmvOa.js
57 ms
timthumb.php
43 ms
timthumb.php
40 ms
timthumb.php
40 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
46 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
xrefid.xgi
34 ms
px
33 ms
v1-likez-1.js
35 ms
xrefid.xgi
21 ms
px
21 ms
378348.gif
21 ms
dpx
18 ms
52154.gif
36 ms
47154.gif
37 ms
pixel;r=1774315182;a=p-KhYH1eCCx9-1N;fpan=0;fpa=P0-2125102802-1458442675886;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458442676010;tzo=-180;ref=;url=http%3A%2F%2Fwww.mobilelikez.com%2F;ogl=description.%2Cimage.%2Csite_name.www%252Emobilelikez%252Ecom%2Curl.http%3A%2F%2Fwww%252Emobilelikez%252Ecom%2F%2Ctitle.
35 ms
s9.g
52 ms
aol
34 ms
86 ms
52 ms
i.js
43 ms
analytics.js
25 ms
dpx.js
21 ms
20087
41 ms
20160127082606-5355.js
20 ms
collect
28 ms
p
19 ms
mapuser
16 ms
20214
27 ms
net.php
15 ms
pixel
21 ms
generic
10 ms
pixel
20 ms
dpx
6 ms
generic
8 ms
net.php
8 ms
pixel
16 ms
pixel
19 ms
pixel.gif
5 ms
y_match
4 ms
362358.gif
9 ms
match_redirect
8 ms
pixel.gif
2 ms
29931
13 ms
xrefid.xgi
4 ms
mobilelikez2.net SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilelikez2.net 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 Mobilelikez2.net 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.
mobilelikez2.net
Open Graph description is not detected on the main page of Mobilelikez 2. 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: