7.5 sec in total
1.4 sec
5.5 sec
583 ms
Visit mobilephone.co.in now to see the best up-to-date Mobilephone content for India and also check out these interesting facts you probably never knew about mobilephone.co.in
Latest Mobile Phone reviews, specifications, photo's, features and prices. New Mobile Phones blog writing about latest mobile phone prices in India and
Visit mobilephone.co.inWe analyzed Mobilephone.co.in page load time and found that the first response time was 1.4 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mobilephone.co.in performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value6.8 s
7/100
25%
Value9.1 s
14/100
10%
Value14,250 ms
0/100
30%
Value0.013
100/100
15%
Value18.2 s
3/100
10%
1388 ms
215 ms
50 ms
87 ms
86 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 47% of them (69 requests) were addressed to the original Mobilephone.co.in, 7% (10 requests) were made to Static.xx.fbcdn.net and 5% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Mobilephone.co.in.
Page size can be reduced by 649.0 kB (51%)
1.3 MB
630.5 kB
In fact, the total size of Mobilephone.co.in main page is 1.3 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. 60% of websites need less resources to load. Javascripts take 643.5 kB which makes up the majority of the site volume.
Potential reduce by 76.9 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 76.9 kB or 86% of the original size.
Potential reduce by 17.2 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. Mobilephone images are well optimized though.
Potential reduce by 410.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 410.3 kB or 64% of the original size.
Potential reduce by 144.7 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. Mobilephone.co.in needs all CSS files to be minified and compressed as it can save up to 144.7 kB or 73% of the original size.
Number of requests can be reduced by 80 (59%)
135
55
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilephone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.mobilephone.co.in
1388 ms
style.css
215 ms
css
50 ms
styles.css
87 ms
default-style.css
86 ms
social_widget.css
88 ms
boxed-1120.css
106 ms
wdsb.css
111 ms
jquery.js
265 ms
jquery-migrate.min.js
171 ms
wdsb.js
188 ms
plugin.css
198 ms
trigger_buttons.min.css
194 ms
dashicons.min.css
405 ms
thickbox.css
404 ms
font-awesome.min.css
378 ms
nextgen_basic_thumbnails.min.css
375 ms
style.min.css
376 ms
nggallery.css
403 ms
brand
21 ms
show_ads.js
12 ms
jquery.form.min.js
470 ms
scripts.js
470 ms
jquery.jplayer.min.js
666 ms
jquery.flexslider.min.js
579 ms
jquery.fancybox.pack.js
579 ms
jquery.fancybox-media.js
628 ms
jquery.mousewheel-3.0.6.pack.js
627 ms
jquery.theme.js
673 ms
wp-embed.min.js
707 ms
ajax.min.js
710 ms
common.min.js
715 ms
nextgen_basic_thumbnails.min.js
798 ms
lightbox_context.min.js
800 ms
nextgen_thickbox_init.min.js
837 ms
thickbox.js
839 ms
infolinks_main.js
72 ms
js
32 ms
brand
34 ms
wp-emoji-release.min.js
736 ms
Mobile-logo.png
516 ms
bg.png
531 ms
sprite-h.png
532 ms
Spice-Stellar-520n-Mobile-550x415.jpg
731 ms
Karbonn-Sparkle-V-Mobile-503x415.jpg
698 ms
Alcatel-One-Touch-Flash-Mobile-448x415.jpg
700 ms
Spice-Stellar-517-Mobile.jpg
699 ms
iBall-Andi-3.5-F-Grabit-Mobile-400x415.jpg
785 ms
Samsung-Galaxy-Mega-2-Mobile-495x415.jpg
785 ms
Intex-Aqua-Style-X1-150x100.jpeg
764 ms
Huawei-Honor-Holly-smartphone-150x100.jpg
778 ms
HTC-Desire-Eye-Mobile-150x100.jpg
819 ms
Samsung-Galaxy-Grand-Prime-Mobile-150x100.jpg
828 ms
Gionee-GN715-150x100.jpg
834 ms
Lava-Iris-352-Flair-Mobile-150x100.jpg
897 ms
iPhone-6-Plus-phone-150x100.jpg
978 ms
Samsung-Galaxy-Note-Edge-Mobile-150x100.jpg
961 ms
facebook.png
1003 ms
googleplus.png
1003 ms
QQt14e8dY39u-eYBZmppwTqR_3kx9_hJXbbyU8S6IN0.woff
35 ms
twitter.png
998 ms
google_custom_search_watermark.gif
124 ms
pinterest.png
1061 ms
cj2hUnSRBhwmSPr9kS5899kZXW4sYc4BjuAIFc1SXII.woff
108 ms
c92rD_x0V1LslSFt3-QEpgRV2F9RPTaqyJ4QibDfkzM.woff
64 ms
League_Gothic-webfont.woff
1119 ms
ca-pub-5208211665304527.js
121 ms
zrt_lookup.html
136 ms
show_ads_impl.js
155 ms
sidebar-right.png
959 ms
hr.png
964 ms
glass.png
915 ms
sprite-v.png
1029 ms
icons-14.png
1015 ms
search.png
1012 ms
likebox.php
449 ms
arrow.png
989 ms
nav-alt.png
1056 ms
hr-light.png
1004 ms
ads
446 ms
osd.js
50 ms
footer-to-top.png
1867 ms
user_sync.html
65 ms
usersyncup-an.html
32 ms
ice.js
284 ms
loadingAnimation.gif
1804 ms
showad.js
220 ms
3nB4xc2_6jL.css
330 ms
DHQqLLtVOYz.css
408 ms
SRSW8M763HA.js
512 ms
ullQFyhrQFI.js
604 ms
y97Ig99UVTs.js
535 ms
KHAtULXOQuz.js
534 ms
PugMaster
71 ms
in.php
198 ms
14601205364781
83 ms
Pug
51 ms
usersync.aspx
48 ms
generic
67 ms
css
121 ms
m_js_controller.js
113 ms
abg.js
115 ms
Pug
47 ms
pixel
26 ms
Pug
72 ms
Pug
121 ms
generic
6 ms
Pug
139 ms
Pug
132 ms
doq.htm
478 ms
Pug
107 ms
favicon
108 ms
nessie_icon_tiamat_white.png
62 ms
s
45 ms
googlelogo_color_112x36dp.png
75 ms
x_button_blue2.png
43 ms
mapuid
43 ms
Pug
39 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
9 ms
PuwvqkdbcqU-fCZ9Ed-b7RsxEYwM7FgeyaSgU71cLG0.woff
83 ms
523983_358768937556125_1318402858_n.jpg
994 ms
399548_10149999285987789_1102888142_n.png
1039 ms
12733619_782214885218066_4266344854834709792_n.jpg
1082 ms
12359944_563706553781182_7818981172893868528_n.jpg
1277 ms
12043194_1496895993937713_6410880099968244056_n.jpg
1122 ms
11880510_847233645390633_5922644770159096098_n.jpg
1123 ms
1476484_584535798262315_1696891970_n.jpg
1121 ms
1907533_108441962827379_8946790517797966582_n.jpg
1122 ms
wL6VQj7Ab77.png
928 ms
1JLnMyDN79z.png
926 ms
quantcast.js
882 ms
getads.htm
261 ms
loader.gif
64 ms
loader-bg.png
63 ms
activeview
15 ms
quant.js
17 ms
pixel;r=126409674;a=p-aRAyv335QWAKb;fpan=1;fpa=P0-1414252567-1460120538002;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460120538001;tzo=-180;ref=;url=http%3A%2F%2Fwww.mobilephone.co.in%2F;ogl=
21 ms
67 ms
blank.html
0 ms
97 ms
echo.htm
191 ms
VXcANLwwL5J.js
47 ms
i8XO-4kv8i7.js
42 ms
newsflash.png
41 ms
newsflash-fade.png
73 ms
ui
17 ms
aa.js
29 ms
p.js
63 ms
mobilephone.co.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
mobilephone.co.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mobilephone.co.in SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilephone.co.in 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 Mobilephone.co.in 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.
mobilephone.co.in
Open Graph description is not detected on the main page of Mobilephone. 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: