Tools & Wizards About Us
fonezone.in screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fonezone.in

Online Shopping for Electronics, Mobile Phones ETC – Fonezone.in

Page Load Speed

3 sec in total

First Response

267 ms

Resources Loaded

2.5 sec

Page Rendered

271 ms

fonezone.in screenshot

About Website

Welcome to fonezone.in homepage info - get ready to check Fonezone best content for India right away, or after learning these important things about fonezone.in

Best Prices. Free Shipping on All Orders. Pay on Delivery. Easy Returns. Huge Selection. Free Shipping* 100% Purchase Protection. Types: Computer & Accessories, Mobile Phones, Mobile Accessories & Man...

Visit fonezone.in

Key Findings

We analyzed Fonezone.in page load time and found that the first response time was 267 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

fonezone.in performance score

0

Network Requests Diagram

www.fonezone.in

267 ms

ajaxify.scss.css

38 ms

timber.scss.css

44 ms

theme.scss.css

41 ms

css

25 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fonezone.in, 58% (46 requests) were made to Cdn.shopify.com and 6% (5 requests) were made to Shopiapps.in. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Shopiapps.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.1 kB (23%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fonezone.in main page is 1.7 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. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 59.7 kB

  • Original 71.1 kB
  • After minification 58.2 kB
  • After compression 11.4 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 12.9 kB, which is 18% 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 59.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 11.6 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. Fonezone images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 244.8 kB

  • Original 383.5 kB
  • After minification 352.2 kB
  • After compression 138.7 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 244.8 kB or 64% of the original size.

CSS Optimization

-74%

Potential reduce by 75.0 kB

  • Original 101.1 kB
  • After minification 100.6 kB
  • After compression 26.2 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. Fonezone.in needs all CSS files to be minified and compressed as it can save up to 75.0 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (51%)

Requests Now

74

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonezone. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.fonezone.in

www.fonezone.in

267 ms

ajaxify.scss.css

ajaxify.scss.css

38 ms

timber.scss.css

timber.scss.css

44 ms

theme.scss.css

theme.scss.css

41 ms

css

css

25 ms

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js

28 ms

jquery.min.js

jquery.min.js

30 ms

modernizr.min.js

modernizr.min.js

63 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

61 ms

slider.js

slider.js

84 ms

fastclick.min.js

fastclick.min.js

84 ms

timber.js

timber.js

86 ms

theme.js

theme.js

86 ms

handlebars.min.js

handlebars.min.js

88 ms

ajaxify.js

ajaxify.js

86 ms

whatsapp_inc.php

whatsapp_inc.php

444 ms

currencies.js

currencies.js

82 ms

shopify_stats.js

shopify_stats.js

42 ms

trekkie.storefront.min.js

trekkie.storefront.min.js

73 ms

shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js

shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js

52 ms

logo.png

logo.png

22 ms

slide_1.jpg

slide_1.jpg

42 ms

slide_2.jpg

slide_2.jpg

35 ms

slide_3.jpg

slide_3.jpg

35 ms

slide_4.jpg

slide_4.jpg

35 ms

slide_5.jpg

slide_5.jpg

26 ms

slide_6.jpg

slide_6.jpg

33 ms

iphone3gs_medium.jpg

iphone3gs_medium.jpg

35 ms

9310_medium.jpg

9310_medium.jpg

40 ms

ax_medium.png

ax_medium.png

68 ms

ps3_medium.jpg

ps3_medium.jpg

66 ms

8460p_medium.jpg

8460p_medium.jpg

66 ms

Blackberry_Playbook_16GB_Tablet_0ae96e86-4cb1-499a-9dbf-e7f25a139b00_large.jpeg

Blackberry_Playbook_16GB_Tablet_0ae96e86-4cb1-499a-9dbf-e7f25a139b00_large.jpeg

68 ms

Blackberry_Playbook_16GB_Tablet_large.jpeg

Blackberry_Playbook_16GB_Tablet_large.jpeg

67 ms

vs810_large.jpg

vs810_large.jpg

67 ms

ds109_large.jpg

ds109_large.jpg

69 ms

9860_large.jpg

9860_large.jpg

69 ms

9380_large.jpg

9380_large.jpg

69 ms

iphone5s_d84611be-024c-43ff-a84f-188095e24013_large.jpg

iphone5s_d84611be-024c-43ff-a84f-188095e24013_large.jpg

69 ms

iphone4_d49c63b7-ac1a-4c0f-831a-d7aff9a99b63_large.jpg

iphone4_d49c63b7-ac1a-4c0f-831a-d7aff9a99b63_large.jpg

70 ms

iphone4_42c199ad-1d4c-4345-a6d2-cefd7890ca26_large.jpg

iphone4_42c199ad-1d4c-4345-a6d2-cefd7890ca26_large.jpg

71 ms

iphone4_8735cc68-5ce3-4602-8c1a-5d570443fc6b_large.jpg

iphone4_8735cc68-5ce3-4602-8c1a-5d570443fc6b_large.jpg

71 ms

iphone3gs_695cce11-29da-4672-86f5-91c1f930875a_large.jpg

iphone3gs_695cce11-29da-4672-86f5-91c1f930875a_large.jpg

71 ms

1100_large.jpg

1100_large.jpg

71 ms

m7_large.jpeg

m7_large.jpeg

73 ms

t328d_large.jpeg

t328d_large.jpeg

73 ms

5sgold_8bdc4d85-e7ca-4957-8f58-d63a88998012_large.jpeg

5sgold_8bdc4d85-e7ca-4957-8f58-d63a88998012_large.jpeg

120 ms

iphone4_cb8363a8-821b-4f2b-9bd9-ffcc552cb8a8_large.jpg

iphone4_cb8363a8-821b-4f2b-9bd9-ffcc552cb8a8_large.jpg

71 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

11 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

16 ms

identify

identify

142 ms

analytics.js

analytics.js

14 ms

record.gif

record.gif

76 ms

collect

collect

3 ms

collect

collect

67 ms

page

page

110 ms

icons.woff

icons.woff

25 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

31 ms

common.js

common.js

187 ms

whatsapp-button.js

whatsapp-button.js

213 ms

load_div.php

load_div.php

1045 ms

analytics.js

analytics.js

32 ms

wp_icon.png

wp_icon.png

63 ms

conversion-production-min.js

conversion-production-min.js

55 ms

spr.js

spr.js

65 ms

freeshippingbar.js

freeshippingbar.js

95 ms

9174-05f83a77c11adaab1e3c5884fceb75ec.js

9174-05f83a77c11adaab1e3c5884fceb75ec.js

110 ms

137 ms

jquery.currencies.min.js

jquery.currencies.min.js

473 ms

spr.css

spr.css

45 ms

jquery.min.js

jquery.min.js

13 ms

vantage-1.6.js

vantage-1.6.js

24 ms

fbevents.js

fbevents.js

84 ms

fsb_get_bar

fsb_get_bar

15 ms

32 ms

css

css

65 ms

cart.json

cart.json

129 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

22 ms

ico-select.svg

ico-select.svg

21 ms

SEO Factors

fonezone.in SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonezone.in 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 Fonezone.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.

Social Sharing Optimization

fonezone.in

Open Graph data is detected on the main page of Fonezone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: