22.3 sec in total
5.8 sec
16 sec
535 ms
Visit fonokart.com now to see the best up-to-date Fonokart content for India and also check out these interesting facts you probably never knew about fonokart.com
Buy stylish moblie phone covers, cases and accessories online in India at affordable prices for Apple, Samsung, Blackberry, HTC, Nokia, Sony and Nexus at Fonokart.com.
Visit fonokart.comWe analyzed Fonokart.com page load time and found that the first response time was 5.8 sec and then it took 16.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fonokart.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value8.4 s
2/100
25%
Value18.5 s
0/100
10%
Value320 ms
76/100
30%
Value0.239
52/100
15%
Value14.7 s
8/100
10%
5796 ms
1443 ms
978 ms
1230 ms
1414 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 11% of them (20 requests) were addressed to the original Fonokart.com, 22% (41 requests) were made to Skin.fonokart.com and 21% (39 requests) were made to Media.fonokart.s3-website-ap-southeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Fonokart.com.
Page size can be reduced by 1.5 MB (30%)
5.0 MB
3.5 MB
In fact, the total size of Fonokart.com main page is 5.0 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. 70% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 198.5 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 47.9 kB, which is 21% 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 198.5 kB or 88% of the original size.
Potential reduce by 273.8 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. Fonokart images are well optimized though.
Potential reduce by 656.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 656.6 kB or 73% of the original size.
Potential reduce by 382.4 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. Fonokart.com needs all CSS files to be minified and compressed as it can save up to 382.4 kB or 85% of the original size.
Number of requests can be reduced by 72 (43%)
166
94
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonokart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.fonokart.com
5796 ms
styles.css
1443 ms
general.css
978 ms
bootstrap.min.css
1230 ms
jquery.1.8.2.min.js
1414 ms
noConflict.js
734 ms
jquery.onebyone.js
738 ms
jqueryNoConfig.js
462 ms
jquery.bxslider.min.js
488 ms
default.css
982 ms
widgets.css
1210 ms
magento.css
1219 ms
social.css
1271 ms
productslist.css
1622 ms
productsscroller.css
1707 ms
ajaxglobalmessages.css
1696 ms
testimonialmanager.css
1883 ms
jquery.bxslider.css
1932 ms
easycatalogimg.css
1945 ms
ajaxlogin.css
2131 ms
onebyone.css
2194 ms
responsive.css
2197 ms
prototype.js
1742 ms
ccard.js
1024 ms
validation.js
1698 ms
builder.js
1482 ms
effects.js
1774 ms
dragdrop.js
1870 ms
controls.js
2176 ms
slider.js
1955 ms
js.js
2419 ms
form.js
2229 ms
translate.js
2251 ms
cookies.js
2353 ms
window.js
2935 ms
social.js
2655 ms
jquery-1.8.2.min.js
3463 ms
bootstrap.min.js
2953 ms
bootstrap-tooltip.js
2834 ms
jquery.mtlib.js
3639 ms
jquery.selectbox-0.2.js
3167 ms
jquery-1-7-1.js
4052 ms
css
25 ms
styles-no-responsive.css
2356 ms
css
36 ms
jquery.isotope.js
1212 ms
print.css
248 ms
analytics.js
29 ms
logo.png
297 ms
2_1.png
3346 ms
fb.png
716 ms
s-ip6g-0507c_result.jpg
715 ms
loading.gif
712 ms
1_1.png
3378 ms
3_1.png
2932 ms
4_1.png
2848 ms
Flipcases.png
2388 ms
metalbrushed.png
2526 ms
banner-white.png
3543 ms
diamond.png
4743 ms
stand.png
4651 ms
flip.png
4752 ms
amr.png
5651 ms
tribal.png
5218 ms
bumper.png
5153 ms
1.png
1188 ms
2.png
1192 ms
3.png
986 ms
5.png
1125 ms
4.png
1262 ms
6.png
1929 ms
7.png
2357 ms
8.png
2365 ms
commas1.png
1708 ms
commas2.png
1736 ms
li.png
701 ms
google.png
699 ms
s-ip6g-0507f_result.jpg
703 ms
s-ip6g-0507p_result.jpg
700 ms
s-ip6g-0507y_result.jpg
699 ms
s-ip6g-0495s_1_result_1.jpg
702 ms
s-ip6g-0495f_1_result.jpg
700 ms
s-ip6g-0495m_1_result.jpg
1217 ms
s-ip6g-0495j_1_result.jpg
1202 ms
s-ip6g-2425w_result.jpg
1254 ms
s-ip6g-2425p_result.jpg
1217 ms
s-ip6g-2425m_result_1_1.jpg
1216 ms
s-ip6g-2425g_result.jpg
1201 ms
s-ip6g-0130w_1_result.jpg
1449 ms
s-ip6g-0130s_1_result.jpg
1455 ms
s-ip6g-0130r_1_result.jpg
1449 ms
s-ip6g-0130e_1_result.jpg
1447 ms
s-ip6g-7997q_1_result.jpg
1459 ms
s-ip6g-7997p_1_result.jpg
1691 ms
s-ip6g-7997n_1_result.jpg
1906 ms
s-ip6g-7997m_1_result.jpg
1908 ms
s-ip6g-0337f_2_result.jpg
1691 ms
s-ip6g-0337h_2_result.jpg
1708 ms
s-ip6g-0337j_2_result.jpg
1692 ms
s-ip6g-0337d_2_result.jpg
1955 ms
s-ip6g-0214r_4_result.jpg
1942 ms
s-ip6g-0214f_4_result.jpg
1951 ms
s-ip6g-0214l_4_result.jpg
1955 ms
s-ip6g-0214g_4_result.jpg
2150 ms
s-ip6g-0507p_result.jpg
2158 ms
s-ip6g-0507y_result.jpg
2190 ms
s-ip6g-0495j_1_result_2.jpg
2195 ms
s-ip6g-0713_b1_result.jpg
2211 ms
s-ip6g-0554j_1_result.jpg
2195 ms
s-ip6g-0495j_1_result.jpg
2387 ms
s-ip6g-0483e_result.jpg
2398 ms
s-ip6g-0438w_result.jpg
2441 ms
ga.js
41 ms
all.js
40 ms
client:plusone.js
154 ms
collect
113 ms
icon-search.png
656 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
100 ms
OpenSans-Regular.woff
1154 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
102 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
101 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
102 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
101 ms
cart.png
694 ms
login.png
692 ms
wishlist.png
703 ms
collect
118 ms
__utm.gif
50 ms
points.jpg
2571 ms
loading.gif
809 ms
216 ms
cb=gapi.loaded_0
70 ms
xd_arbiter.php
75 ms
xd_arbiter.php
177 ms
loader.gif
1036 ms
loginbgg.png
1202 ms
loading.gif
1209 ms
postmessageRelay
59 ms
bg_direction_nav.png
1077 ms
loading.gif
1101 ms
bg-product.png
1767 ms
test_rating.png
1506 ms
3193398744-postmessagerelay.js
259 ms
rpc:shindig_random.js
256 ms
footerrepeat.jpg
2195 ms
Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf
15 ms
facebook.png
1709 ms
twitter.png
1721 ms
insta.png
1933 ms
printer.png
1954 ms
call.png
2131 ms
mail.png
2173 ms
payicons.png
2406 ms
shipicons.png
2189 ms
up-arrow.png
2629 ms
controls.png
2202 ms
s-ip6g-0297e_3_result.jpg
1750 ms
s-ip6g-0239r_1_result.jpg
1759 ms
s-ip6g-0207g_1_result.jpg
1782 ms
xd_arbiter.php
12 ms
cb=gapi.loaded_0
9 ms
page.php
145 ms
Ezryo55Cca5.css
39 ms
2NJaWBZ8ldv.css
44 ms
q68gy-v_YMF.js
41 ms
YvxwM8R7ol8.js
69 ms
ihptErjAmMX.js
66 ms
1BQnIVjTFoC.js
64 ms
6PDLJFN-l6_.js
66 ms
cUsKAwzqrQw.js
91 ms
12400541_2121701401302171_640444657513046003_n.png
938 ms
12376541_2119557551516556_7708430621642947683_n.png
23 ms
10953979_1378401519136295_3987422283617625728_n.jpg
26 ms
10314652_1682526405354863_6269632710712411576_n.jpg
24 ms
12742789_1050657154976444_4505649479914878112_n.jpg
25 ms
10330263_561920867291062_4391624061754991216_n.jpg
27 ms
12112403_903876316361905_8977038036198361668_n.jpg
50 ms
12801117_225958037751635_1422508460220155170_n.jpg
27 ms
12745878_564114193754770_387711874141095663_n.jpg
143 ms
12795390_825818550879478_94893665984847054_n.jpg
28 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
17 ms
6GqoI2ZyIrf.png
18 ms
R9a_DtVRZgv.js
7 ms
cUDgRFxaoIk.js
9 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
9 ms
fonokart.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fonokart.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
fonokart.com 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 Fonokart.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 Fonokart.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.
fonokart.com
Open Graph description is not detected on the main page of Fonokart. 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: